The Joomla! Forum ™

I think i'd like to downgrade to the last stable release until the developers get an opportunity to fix the issues in 2.5.5. Right now I see a whole lot of files for 2.5.5, upgrade package, patching packages, it looks like a giant headache to me!

Quite. I love Joomla! and appreciate the immense amount of work that goes into it. But roll on 2.5.6 ....

_________________
My website: http://www.davidboggitt.com/
Love and hate both devastate you, but at least love takes you to dinner first.

The only way to downgrade is to restore from a backup that you made before you started the upgrade.

We expect to be out with 2.5.6 later today, so you could try that as a manual update to your partially updated site.

_________________
Andrea Tarr
http://www.tarrconsulting.com - Tarr Consulting
http://www.twitter.com/Tarrconsulting - Follow me on Twitter @Tarrconsulting

Yaay!!

_________________
My website: http://www.davidboggitt.com/
Love and hate both devastate you, but at least love takes you to dinner first.

@atarr

I attempted to re-try the update extension, but while it seems to have gone through OK back-end, I'm still getting a blank screen front-end.

What's this I'm hearing about a .PHP error? Might it be relevant to my case, and if so what should I do about it?

Thanks again for all your help!

Well, I'll try upgrading to 2.5.6 later today ...

This is a two-part message for Nick and atarr;


Nick,

I have answered your questions below:

1) What are your SEF settings?

Search Engine Friendly URLs > Yes
Use URL rewriting > Yes
Adds Suffix to URL > Yes
Unicode Aliases > No

2) What is the menu type of the menu item that the alias is pointing to?
Alias was for a link to an article. The menu (with the aliases) was actually a hidden menu and not assigned to a visable position. This menu and its links were not being used on the site at the moment. The links were in a menu and the menu was in the menu list but I was not currently using it on the site to access any pages. Don't know if that matters. Sometimes I want to create a link to a page/s that are not visable my main menu - hence the "hidden menu". Examples would be a sitemap, legal and terms links in my footer.

3) Is there more than one alias pointing to that menu item?
No

4) Could you try your same settings on a clean install?
Not at the moment. However, I applied the 2.5.5 update to another site yesterday and had no problems. One thing to note though, my "hidden menu" on this other site did not contain any aliases. Maybe it does have something to do with the fact the site with the problems has a hidden menu and also contains aliases.

5) Do you by chance have an SEF extension installed?
No. Just using Joomla SEF. The .htaccess files has been changed as well as the configuration file with regard to $live_site line to use Joomla SEF.

6) Is there anything peculiar about your menu item aliases?
Nothing special - see numbers 2 and 4 above...


atarr,

1. Go into all your menu items that have the type of alias and Save them. See if that fixes the problem
Oddly enough that worked for one menu item - this menu item was a link to an uncatagorized page. The other link that didn't fix when saved was to a catagory/blog. This second link (the original one in my main menu, not the alias) was actually unpublished at the time.

2. If that doesn't fix it, see if you can go in and reselect the menu item the alias is pointing to.
No change.

3. If that doesn't fix it, see if you can change the menu type to something other than alias and then change it back to alias.
No change.

I am guessing that the issue has something to do with the fact that the menu item alias with the problems are linked (aliased) to menu items that are unpublished. In my case, both the parent and the alias were unpublished. The reason for this is that I replicated a site for quicker developement and had many menu items unpublished. I had not gone back to delete the unused menus and links yet. The site where I didn't have problems contained no menu item aliases where the parent item was also unpublished. Aliases were used however with no apperant problem. I hope that made some sense...

Thanks for all you do guys! Hope this helps.

_________________
I searched first, I swear I did...

J2.5.7 Stable / PHP Version 1.5.17 / Apache 2.2.20 (Unix)
/G\

So do I apply 2.5.5, then if that works, the 2.5.5 patch afterwards?

I'm not a programmer, very much a newbie to Joomla, and all this has me in a tail spin.

Nope you wait.

Lol. I like your thinking.

I do have an Akeeba backup I did just prior to clicking the fatal upgrade button, but I'm not entirely sure how to access it and roll it backwards.

@grafixpro

Thanks! I was able to replicate the problem by unpublishing the menu item that was being pointed to. I think there is a second issue that is being fixed by the saving as well, but this is a good step forward.

We are planning to remove the original bug fix that is causing this problem (that https isn't working for aliased menu items) for the release 2.5.6 that we plan to release later today. That will fix the problem that people are currently having with the get() error. We'll need to take some time to fix that patch so it fixes the error without introducing more bugs.

Thanks for the help.

_________________
Andrea Tarr
http://www.tarrconsulting.com - Tarr Consulting
http://www.twitter.com/Tarrconsulting - Follow me on Twitter @Tarrconsulting

Thank you grafixpro!

FYI, here's the new tracker item for the menu item alias issue:
http://joomlacode.org/gf/project/joomla ... m_id=28704

Kind regards,
Nick

_________________
To God through Jesus Christ be the glory forever and ever!
---------------
Online Joomla Training at http://www.ostraining.com/online/
Sell your templates at https://www.templatecapitol.com/

@piersh

To see what the PHP error is, go to Site/Global Configuration in your backend. Go to the Server tab. Change Error Reporting to Maximum (it's probably either System Default or None right now). Apply the change.

Now if you go to the frontend you will probably see an error message. Copy it and post it here.

Thanks,

_________________
Andrea Tarr
http://www.tarrconsulting.com - Tarr Consulting
http://www.twitter.com/Tarrconsulting - Follow me on Twitter @Tarrconsulting

Thanks you have just saved my life, I had visions of reinstalling the whole site thanks to the forum, you would have thought it would have been tested bofore it was published doesn't inspire confidence thanks to the forum

@hfsh

Good that you have a backup, just in case. If you want to be more secure, FTP to your site and download it. You'll find it under administrator/components/com_akeeba/backups

When 2.5.6 comes out, follow Method C to update your site (see the document I posted above or use the link to update instructions on the announcement on joomla.org). That's the only way to do it since you don't have a functioning backend at the moment.

If that doesn't fix it, then you can restore the site from your backup.

_________________
Andrea Tarr
http://www.tarrconsulting.com - Tarr Consulting
http://www.twitter.com/Tarrconsulting - Follow me on Twitter @Tarrconsulting

I was simply pointing out that the developer's recommendation at this time (albeit in a shortened version) was that if you have not updated yet, then don't do it until, hopefully later today, the 2.5.6 release is made.
This would also apply to new installers and that is to await the next release.

hope that helps clarify the point.

I get the error: "Fatal error: Using $this when not in object context in: /ROOT/.../libraries/joomla/application/base.php". I patched yesterday, then decided to reinstall 2.5.4->2.5.5 release and the error returned.

Just wondering why... if the bug was identified and a patch is being discussed http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=28684, why has this not made it into the official 2.5.5 release?

The 2.5.5 release won't be changed, ever. Once a version is tagged and released, that is it for that version. That being said, a 2.5.6 update is being prepared right now to fix the issues that were introduced in 2.5.5, and as such, that will be the version recommended for use. In the meantime, if you have a site impacted by one of the numerous errors discussed here, your best bet is to restore a backup to 2.5.4 and wait for 2.5.6 to be released with all of these fixes.

_________________
http://www.babdev.com
Unsolicited PMs will be ignored
Follow me @mbabker

I'm getting this error on certain pages:

Fatal error: Call to a member function get() on a non-object in /home/global/public_html/modules/mod_menu/helper.php on line 100

and after having ALSO gotten an error with the Docman modules, on a hunch I disabled a side bar menu module for the page that was kicking up that line 100 error.

Sure enough, it works.

First I thought, "they're looking in the wrong place, it's a module issue" and then it dawned on me, the top menu or side menu, they're BOTH modules. Duh. Then I realized the side bar menu does indeed have aliases in it.

So, at this point, is there a fix for the alias in the menu bug, or do we just wait for 2.5.6?

thanks!

_________________
Brian Peat,
Owner, The Peat Group
http://www.thepeatgroup.com

There is a fix for the menu issue is in 2.5.6.

It has to do with menu aliases. For a fix, try going into each menu item that has a type of alias and saving it. If that doesn't fix it, check that the menu item being pointed to is actually published.

_________________
Andrea Tarr
http://www.tarrconsulting.com - Tarr Consulting
http://www.twitter.com/Tarrconsulting - Follow me on Twitter @Tarrconsulting

I just replaced my helper file with the one you posted here:

https://github.com/joomla/joomla-cms/bl ... helper.php

it fixed the issue. At least that'll get my by until the 2.5.6 release

Thanks!

_________________
Brian Peat,
Owner, The Peat Group
http://www.thepeatgroup.com

Hi everyone,

We've released a 2.5.6 test package which fixes the bugs reported within this discussion. Please see the following announcement for how to test:
viewtopic.php?f=625&t=725578

If no major issues are reported, we will release the 2.5.6 version sometime today (sooner rather than later).

Kind regards,
Nick

_________________
To God through Jesus Christ be the glory forever and ever!
---------------
Online Joomla Training at http://www.ostraining.com/online/
Sell your templates at https://www.templatecapitol.com/

work for me,
thanks

We are reverting 2.5.5 to 2.5.4. In JCE anytime we (or our clients, unfortunately) edited a page, all the formatting was removed and the entire page was placed in a single paragraph.

Looking forward to a fix. Thanks.

Use ftp
it will probably be in be in /administrator/components/akeeba/backup
Download it to your PC to keep it safe
Upload it to the Joomla root
Download kickstart.zip from the Akeeba site unzip on your PC
Upload kickstart.php to your Joomla root
Point your Browser to www.yoursite.com/kickstart.php

_________________
http://weblinksonline.co.uk/joomla-faq.html

@All
OK, 2.5.6 is live. Thank you to everyone who helped and congrats!

Kind regards,
Nick

_________________
To God through Jesus Christ be the glory forever and ever!
---------------
Online Joomla Training at http://www.ostraining.com/online/
Sell your templates at https://www.templatecapitol.com/

New 2.5.5 install with Virtuemart installation package works okay (as it should I guess) - Upgraded to 2.5.6 via extension manager - admin side fine but user side failed with helper.php message.
As this is a new site, I just did a complete 2.5.5 install again and working on that - will wait till 2.5.6 is okay.
Am relatively new to Joomla so don't want to mess around too much if I did't know what to fix!

I am confused. Which upgrade package should I use if I have a Joomla 2.5.4 site? I didn't upgrade to 2.5.5.

I don't see an upgrade package from 2.5.4 to 2.5.6 I see an upgrade package from 2.5.5 to 2.5.6 or 2.5.0 to 2.5.6

What is the Joomla_2.5.6-Stable-Update_Package.zip package & when should that be used?

When updating from 2.5.4 to 2.5.6 you do use 2.5.0 to 2.5.6. This is the package that shows when you go to Components/Joomla Update or click the update Joomla icon on the Control Panel. Using the Joomla Update, you don't need to download anything manually.

(The 2.5.6 update file is used if you are updating from 1.7 or if you need to refresh everything.)

_________________
Andrea Tarr
http://www.tarrconsulting.com - Tarr Consulting
http://www.twitter.com/Tarrconsulting - Follow me on Twitter @Tarrconsulting

@kaybee57

If you used the original test package to update to 2.5.6, that was missing the helper.php file fix. The actual update package contains that file, so an upgrade to 2.5.6 should fix your problem.

_________________
Andrea Tarr
http://www.tarrconsulting.com - Tarr Consulting
http://www.twitter.com/Tarrconsulting - Follow me on Twitter @Tarrconsulting