Discuss Joomla! 2.5.10 Released

[yaanimai]

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.

Regarding the sort bug, is it OK to upgrade to 2.5.10 with that bug? Is it just a bug in reporting the version number or does it affect the functionality of the site?

The problem of no intro text showing is a bug fix (solved by adjusting article and or menu settings) & not a bug so that should not affect the upgrade decision, is that correct?

Thanks!

[thierry_s]

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

What a genius you are. This has fixed my problem - many, many thanks

[DavidBoggitt]

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.

I'm also a little concerned about this. As usual, I've given myself 48 hours to wait after an update and now I'm not sure whether to update and 'fix' the natsort/asort issue, or wait for another update, or...

[epatjas]

Same issue. My home page is now title only. Using MaxiMenuCK

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

[Kubik-Rubik]

What a genius you are. This has fixed my problem - many, many thanks

Thanks!

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.

I have tested it and have not encountered any negative effects with this change. Yes, a parameter for the natural algorithm should be the best solution. The function natsort works as sort (with the regular flag) except it sorts numbers in natural order, so it should not have any negative effects on other calls of the function.

Is it just a bug in reporting the version number or does it affect the functionality of the site?

This bug does not affect the functionality of the site.

[cesargabriel]

Hi...

After upgdating J!2.5.9 to J!2.5.10, Extension Manager - Database shows these problems:

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).

Other information:

Database schema version (in #__schemas): 2.5.9.
Update version (in #__extensions): 2.5.10.
Database driver: mysqli.
66 database changes were checked successfully.
31 database changes did not alter table structure and were skipped.

The original J!2.5.9 was a new brand installation with no content...

This bug does not affect front-end performance...

Regards from Lima, Peru...

[DavidBoggitt]

Having read all this, I've just updated one site (after backing up of course!) from 2.5.9 to 2.5.10 using Admin Tools Pro and in the Extension Manager there are no errors reported:

Code: Select all

Database schema version (in #__schemas): 2.5.10.
Update version (in #__extensions): 2.5.10.
Database driver: mysqli.
66 database changes were checked successfully.
31 database changes did not alter table structure and were skipped.

[daszeichen]

Hi Board
There seems to be a problem with 2.5.10 and certain extensions using the jFolder:files() utility function. After updating a couple of sites from 2.5.9 to 2.5.10 they all show a fatal PHP-error:

Code: Select all

Fatal error: Uncaught exception 'UnexpectedValueException' with message 'JPath::clean: $path is not a string.' in /home/xxxxxxx/public_html/libraries/joomla/filesystem/path.php:204

So it seems as soemthing must have changed within path.php in this update. Is there a way to fix this issue?

Thanks a lot for any help
Bernhard (das.zeichen)

[DavidBoggitt]

I've now updated several sites from 2.5.9 to 2.5.10, using Admin Tools Pro each time and every time I get the same thing in Extension Manager, with no problems shown:

Database schema version (in #__schemas): 2.5.10.
Update version (in #__extensions): 2.5.10.
Database driver: mysqli.
66 database changes were checked successfully.
31 database changes did not alter table structure and were skipped.

Is there a difference between updating by ftp-ing files to the server and using Admin Tools Pro? Surely not.... but...?!?!

[Breizhtic]

I've now updated several sites from 2.5.9 to 2.5.10, using Admin Tools Pro each time and every time I get the same thing in Extension Manager, with no problems shown:

Database schema version (in #__schemas): 2.5.10.
Update version (in #__extensions): 2.5.10.
Database driver: mysqli.
66 database changes were checked successfully.
31 database changes did not alter table structure and were skipped.

Is there a difference between updating by ftp-ing files to the server and using Admin Tools Pro? Surely not.... but...?!?!

"Problem" appears only when you press "Fix" on the database tab.

[DavidBoggitt]

But surely people were only pressing Fix because the database showed errors after the update....?

[Kubik-Rubik]

But surely people were only pressing Fix because the database showed errors after the update....?

If you update through the installer, then no error is displayed. The error is only visible after the "Fix" button is activated. Just try it on your site!

PS: I always click on this button to be sure to have the latest database schema.

[GJSchaller]

Thank you for your help, Kubik-Rubik!

Has a bug been submitted to the tracker for this? (I just want to be sure it's fixed for 2.5.11 and beyond!)

[Kubik-Rubik]

You are welcome, Geoffrey!

Yes, the bug will be fixed in the next release: http://joomlacode.org/gf/project/joomla ... m_id=30681

[tloehr]

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 http://www.gebedsklub.net This happened immediately I did the update!

I have exactly the same problem. After the update only the titles of the articles were shown but not the text. The rest is working fine. After I reverted to the previous version everything is back to normal.

Any ideas ?

Bye, Torsten...

[leolam]

Issue you describe cannot be replicated by us

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

[summitawards]

I have a big problem
I have exactly the same problem. After the update only the titles of the articles were shown but not the text. The rest is working fine. After I reverted to the previous version everything is back to normal.

Any ideas ?

Tloehr. Fellow from another thread solved this for me: For the featured articles, it's likely not a bug, but rather a bug fix. Try checking your settings for the menu item (mine is Home) and check the "Show Intro Text" setting. Worked for me.

[armjoomla]

My featured article is not showing up on my home page. Anybody can assist?

Thank you!

EDIT-
Thank you, summitawards, your solution worked!

[Webdongle]

Methinks it's been fixed ... check for updates

[cesargabriel]

Hi...

The problem with database after updating from J!2.5.9 to J!2.5.10 was fixed with new brand update to J!2.5.11

Thanks to Joomla! team...

Regards from Lima, Peru...

[summitawards]

My pleasure armjoomla. I'm a newbie and was passing on what a seasoned user provided. Love this forum and its participants.

[tloehr]

Tloehr. Fellow from another thread solved this for me: For the featured articles, it's likely not a bug, but rather a bug fix. Try checking your settings for the menu item (mine is Home) and check the "Show Intro Text" setting. Worked for me.

Hey 1000 thanks m8,

before I could try this solution I upgraded to the (freshly available) 2.5.11. This version works without any further changes.

But I greatly appreciate Your efforts to help me.

Bye, Torsten...

[semco]

thanks for your quick fixed " just follow instruction"