Discuss Joomla! 2.5.10 Released

[pe7er]

Discuss Joomla! 2.5.10 Released here

Please see announcement for details: http://forum.joomla.org/viewtopic.php?f=8&t=800212

Note: To report bugs, please use the official Bug Tracker.

[saosangmo]

hi,
After updating this version, I can not access the System Information, Global Configuration, Extension Manager, My Profile,...
I'm using:
1) nginx servert as frontend apache as backend.
2) PHP 5.3.23 with APC enabled.
I have tried to remove cookie on my browser. The Administrator login screen displays this message:

Use a valid username and password to gain access to the administrator backend.

I have tested on my local, everything works well.
Does anyone get the same problem?
thanks

[saosangmo]

Don't mind, I have solved this issue.
I re-update with Joomla_2.5.x_to_2.5.10-Stable-Patch_Package, my site comes back.

[Roybinhood]

I have a big problem

After I used the automated administrator Joomla version updater to do a basic update to Joomla 2.5.10 my drop down sub menus when clicked on suddenly do not open to category blog but to nothing ( white blank page with template around) and the front page article does not appear although some of the modules on the font page still do ... do see www.gebedsklub.net This happened immediately I did the update!

[thierry_s]

I was running 2.5.6 and went to update to 2.5.10. This failed to upload via standard update method. Kept coming with Error Null. Tried package via Extension Manager, Error loading file to server. So downloaded file, unzipped, removed installation folder and copied up to server via FTP. Site ok, Backend appears ok. Went to Extension Manager > Database and it had warning two entries both the same =

Warning: Database is not up to date!
1 Database Problem Found

Database schema version (2.5.9) does not match CMS version (2.5.10).

I clicked on Fix and one of the entries disappeared but still have one Warning. I tried to re-install using the first two options mentioned above but still had the same installation error.

Any ideas how I can resolve.

[summitawards]

Newbie, here. Where do I find the Official Bug Tracker to report an issue after updating 2.5.9 to 2.5.10?

[Kubik-Rubik]

Warning: Database is not up to date!
1 Database Problem Found

Database schema version (2.5.9) does not match CMS version (2.5.10).

I clicked on Fix and one of the entries disappeared but still have one Warning. I tried to re-install using the first two options mentioned above but still had the same installation error.

Have the same problem after an update from 2.5.9 to 2.5.10. Updated via the installer in the backend.

Regards

[summitawards]

K. Just to make sure...Joomla_2.5.9_to_2.5.10-Stable-Patch_Package.zip. Can never be too cautious to check first.

[Kubik-Rubik]

K. Just to make sure...Joomla_2.5.9_to_2.5.10-Stable-Patch_Package.zip. Can never be too cautious to check first.

Do you mean me?

And yes, of course I have used the correct package. :-)

[saosangmo]

I have got the same issue.

Warning: Database is not up to date!
1 Database Problem Found
Database schema version (2.5.9) does not match CMS version (2.5.10).

I have run to fix in the panel but the system can not fix it.

[Kubik-Rubik]

Okay, found the problem. It is related to the version number 2.5.10 and the used sorting algorithm for arrays.

The schema is generated from the highest number of all .sql update files in the folder administrator/components/com_admin/sql/updates/mysql or sqlazure. The used folder handling class JFolder (libraries/joomla/filesystem/folder.php) does sort all files in the function files with the following PHP function:

Code: Select all

asort($arr); // line 502

The main problem is that this is not a "natural order" algorithm. So the version 2.5.10 is sorted directly after 2.5.1 and not after 2.5.9.

How to fix it? Change this line into:

Code: Select all

natsort($arr);

and everything is correct and you can lean back!

Note: The database is already up-to-date if you get the mentioned error! The problem is only an inaccurate evaluation of the current version due to the wrong sorting algorithm!

PS: The files are loaded for the schema determination in the class JSchemaChangeset (function: getSchema) in the line

Code: Select all

$updateFiles = $this->getUpdateFiles(); // line 173

[emcg50b]

I'd some issues after 2.5.9 - I couldn't change a menu item from text Separator to Category List.

Exported the database and created a sub-somain on the host, and thought I'd cracked it.
2.5.10 came along and I thought I'd install that, maybe that was the original problem.

Now everything is pear-shaped. My home page featured articles only show the titles, not the content.
In desperation I've sent an email to the host provider to restore last weekend's backup - no I didn't do a backup prior to the update (stupid of me to trust that it would work, I know).

Anyone else with similar issues. 2.5.9 with MaxiMenuCK.

regards

emcg

[summitawards]

Kubik-Rubik - Could you do a gentle step-by-step on the above fix.

I've located two 2.5.10.sql files (two different folders as you said). Where and what code should I add?

[Nick Savov]

Newbie, here. Where do I find the Official Bug Tracker to report an issue after updating 2.5.9 to 2.5.10?

Hi and welcome, summitawards!

Check out the following process for reporting a bug:
http://docs.joomla.org/Filing_bugs_and_issues

Hope this helps!

Kind regards,
Nick

[summitawards]

Thanks Nick. I look to see if I can maybe report a bug. With the autoupdate from 2.5.8 to 2.5.10, my Featured Articles have Titles but don't have Intro text despite their settings to show.

**Anyone giving advice on exactly where I put Joomla_2.5.x_to_2.5.10-Stable-Patch_Package.zip to re-update from cpanel? I think it is suppose to go in public_html and then unpack but...I don't want to break anything.

[chrisjclay]

**Anyone giving advice on exactly where I put Joomla_2.5.x_to_2.5.10-Stable-Patch_Package.zip to re-update from cpanel? I think it is suppose to go in public_html and then unpack but...I don't want to break anything.

Yep, just put it in the Joomla root directory (usually "www" or "public_html") and then extract it through cPanel. If you don't have a recent backup, it wouldn't hurt to make one first. I always back up my sites before updating Joomla, "just in case"...

Chris

[Nick Savov]

Thanks Nick. I look to see if I can maybe report a bug. With the autoupdate from 2.5.8 to 2.5.10, my Featured Articles have Titles but don't have Intro text despite their settings to show.

You're welcome, SummitAwards!

For the featured articles, it's likely not a bug, but rather a bug fix and now your correct setting is showing (I know; it sounds a bit strange). Try checking your settings for the menu item and check the "Show Intro Text" setting.

Hope this helps!

[summitawards]

Whaoo! That was it to show the Inro Text! Thank you so very much.

***Now my needed bug fix is that I have two Featured Articles but only one shows. Two where showing before the 2.5.10 udate Menu is set to have three Any ideas?

[summitawards]

My bad. Darn sticky cache drives me crazy. Both are up and looking pretty. Be well and thank you again Nick!

[Nick Savov]

You're welcome, SummitAwards! Glad I could be of help!

Cheers,
Nick

[Punitsoft]

I have got the same issue.

Warning: Database is not up to date!
1 Database Problem Found
Database schema version (2.5.9) does not match CMS version (2.5.10).

I have run to fix in the panel but the system can not fix it.

Hi,

I am from Softaculous team. Even we are facing same issue after upgrading joomla 2.5.9 to 2.5.10.

Is there an ETA for bug fix ?

[marioguisti]

After updating to 2.5.10, my featured articles do not display. Please help...

[leolam]

I am from Softaculous team. Even we are facing same issue after upgrading joomla 2.5.9 to 2.5.10. Is there an ETA for bug fix ?

Edit: 04/26 2013: We confirm issue on multiple (not all) sites

Leo

[Punitsoft]

I am from Softaculous team. Even we are facing same issue after upgrading joomla 2.5.9 to 2.5.10. Is there an ETA for bug fix ?

Who says this is a bug? we have upgraded today so far 74 websites and are going to do a couple of hundred more..... Issue you describe cannot be replicated by us

Leo

After Upgrade if you go to Extension Manager -> Database - click on the Fix Button

We get Warning: Database is not up to date!
1 Database Problem Found
Database schema version (2.5.9) does not match CMS version (2.5.10).

Did you try this ?

[Kubik-Rubik]

After Upgrade if you go to Extension Manager -> Database - click on the Fix Button

We get Warning: Database is not up to date!
1 Database Problem Found
Database schema version (2.5.9) does not match CMS version (2.5.10).

Did you try this ?

See here for a description and fix: http://forum.joomla.org/viewtopic.php?f ... 3#p3023743

All Joomla! 2.5.10 installations are concerned with this problem.

[ghazal]

Hi,

All Joomla! 2.5.10 installations are concerned with this problem.

Confirmed here.

@Kubik-Rubik
Respects

[Breizhtic]

After Upgrade if you go to Extension Manager -> Database - click on the Fix Button

We get Warning: Database is not up to date!
1 Database Problem Found
Database schema version (2.5.9) does not match CMS version (2.5.10).

Did you try this ?

See here for a description and fix: http://forum.joomla.org/viewtopic.php?f ... 3#p3023743

All Joomla! 2.5.10 installations are concerned with this problem.

Thanks for the fix.

But I have some installations that aren't concerned by this bug... Unless you click on Fix !

[Kubik-Rubik]

But I have some installations that aren't concerned by this bug... Unless you click on Fix !

Yes, the mentioned check function is only called after a click on the "Fix" button. If you update through the installer and don't click on the button, then you won't see the bug.

[mcsmom]

For the issue in which your article text is not displaying, go to the article manager page and click options.
On the tab for articles change show intro text to show.

Unfortunately this will mean that if you were hiding introtext inyour full articles this will now display.

You can fix this with an override right now or we will be doing a fix and release it shortly.

[mcsmom]

On the natsort versus asort we need to not break the API so it's not as simple as changing just that line but that is fantastic that you ran down the problems so well. I think perhaps we need to add an option and defaul to asort since that is what is expected currently.