Search found 4 matches

by champion6
Sat Dec 10, 2005 3:05 pm
Forum: Announcements Discussions
Topic: Discuss about : Upgrade to Joomla! 1.0.4 Security Release now!
Replies: 132
Views: 58049

Re: Discuss about : Upgrade to Joomla! 1.0.4 Security Release now!

In the Tech Zone, there is a thread describing the same navigation problem that I have, m By turning off Caching in Joomla, my navigation links work correctly. The indexing errors in the database still exist. I'll deal with those in time. In the mean time, my site is operational. Thanks to all who p...
by champion6
Fri Dec 09, 2005 10:50 pm
Forum: Announcements Discussions
Topic: Discuss about : Upgrade to Joomla! 1.0.4 Security Release now!
Replies: 132
Views: 58049

Re: Discuss about : Upgrade to Joomla! 1.0.4 Security Release now!

Well, my problem appears to be in my database. I have DirectAdmin, so I used phpMyAdmin. When I ran a check on all tables, these errors were reported: Problems with indexes of table `jos_categories`   More than one INDEX key was created for column `section` Problems with indexes of table `jos_c...
by champion6
Fri Dec 09, 2005 8:00 pm
Forum: Announcements Discussions
Topic: Discuss about : Upgrade to Joomla! 1.0.4 Security Release now!
Replies: 132
Views: 58049

Re: Discuss about : Upgrade to Joomla! 1.0.4 Security Release now!

I'm having problems that I think might be related to this issue. Please help! Problem: I have Latest News on my Front Page. The navigation links at the bottom do not function properly. End >> 1. Clicking on 2 or 3 or 4 (etc.) or Next or End does not always change the display of news items. 2. If th...
by champion6
Tue Nov 29, 2005 2:19 am
Forum: Announcements Discussions
Topic: Discuss about : Upgrade to Joomla! 1.0.4 Security Release now!
Replies: 132
Views: 58049

Re: Discuss about : Upgrade to Joomla! 1.0.4 Security Release now!

Beat, We indeed messed up with the UTF-8 work. We tried a move to UTF-8 in 1.0.3 and then decided to only do it in 1.1. Changes were reverted but the language iso setting was forgotten. We fixed this in 1.0.4 and forgot about the possible consequences. U are right that we should have informed our u...