-
AuthorPosts
-
limeweb Friend
limeweb
- Join date:
- October 2006
- Posts:
- 86
- Downloads:
- 0
- Uploads:
- 0
- Thanks:
- 5
- Thanked:
- 3 times in 1 posts
April 14, 2009 at 10:11 am #140234There is a liddle bug in the quickstart package…
Duplicate entry ’25–10′ for key ‘group_id_aro_id_groups_aro_map’ SQL=INSERT INTO jos_core_acl_groups_aro_map VALUES (25,”,10)
vpitetti Friendvpitetti
- Join date:
- March 2008
- Posts:
- 29
- Downloads:
- 0
- Uploads:
- 0
- Thanks:
- 6
- Thanked:
- 1 times in 1 posts
April 14, 2009 at 4:44 pm #301273Yes I got that too, Installed twice on localhost and once on a real server to check it out and happened all 3 times. See below screenshot for the error during install.
scotty Friendscotty
- Join date:
- March 2008
- Posts:
- 2339
- Downloads:
- 0
- Uploads:
- 13
- Thanks:
- 76
- Thanked:
- 827 times in 595 posts
August 22, 2009 at 4:36 pm #315066It’s not actually an error. This duplicate entry is the setup of your administrator account and is necessary for Joomla to work right. It’s setting the admin ‘user’ up in the ‘user’ table and in the ‘admin group’. This is why it’s regarded as a duplicate.
The reason you are seeing this is because you have ‘display errors’ set to yes in your php config. This is fine in a development environment but ‘display error’ should be set to NO in a live site as it is considered a security risk.
limeweb Friendlimeweb
- Join date:
- October 2006
- Posts:
- 86
- Downloads:
- 0
- Uploads:
- 0
- Thanks:
- 5
- Thanked:
- 3 times in 1 posts
August 22, 2009 at 8:16 pm #315078<em>@scotty 141694 wrote:</em><blockquote>It’s not actually an error. The reason you are seeing this is because you have ‘display errors’ set to yes in your php config. </blockquote>
Hi Scotty
In common with most other template clubs ‘quickstart’ releases JA has display errors inherently set to ‘ON’ whereas, as you rightly say, the recommended setting is ‘OFF’.
Notwithstanding this, all templates (JA and others) load properly on a local server and do not show the duplicate sql ‘error’ even with display switched to ON.
JA Ruby is different. The sql error shows at the head of the page after the sample data file is loaded. This is odd wouldn’t you say?
None of this appears to matter since (as would be expected from your post above) the Ruby Admin works anyway. Just a little strange, thats all.
-
AuthorPosts
This topic contains 5 replies, has 3 voices, and was last updated by scotty 15 years, 3 months ago.
We moved to new unified forum. Please post all new support queries in our New Forum