2.5.6 can't update: ERROR:Invalid login

[designaholic]

Trying to update a 2.5.4 install on a server and I get this ERROR:Invalid login

I am logged in fine. Last time I updated from 2.5.3 to 2.5.4 everything worked perfectly.

Here's a video showing the error: https://dl.dropbox.com/u/5837624/joomla_update_fail.mov

Also, if I check the Extension Manger for updates, nothing shows, i.e, I have to click the update box on the dashboard.

Any ideas on this?

[Per Yngve Berg]

Please use the Forum Post Assistant.

Unable to play the video.

Are the ftp layer enabled in Joomla?
Perhaps a wrong password.

Try to turn the ftp layer off. The ftp layer is not needed on most installs.

[designaholic]

Please use the Forum Post Assistant.

Unable to play the video.

Are the ftp layer enabled in Joomla?
Perhaps a wrong password.

Try to turn the ftp layer off. The ftp layer is not needed on most installs.

Hi, I can't find a link to 'Forum Post Assistant' – what / where is that?

ftp layer is off. Seems to be an issue with Plesk but I have everything set up correctly in terms of permissions, i.e. nothing has changed since the last time I used the auto-updater.

I will do a manual update this time, perhaps it's just a twitchy update as it seemed fine from 2.5.3 > 2.5.4.

ps. the video works for me, perhaps a Dropbox server glitch?

Cheers.

[Per Yngve Berg]

The link to the FPA is at the top of this topic in the orange frame with the forum rules.

[humvee]

[Mod note: Moved from Installation Forum to Upgrade Forum; Please post in the correct forum.]

1. BACKUP your site and database
   • If you have not already done so, do it now!
   • You must also backup your site :
     • before any update procedure,
     • before adding Extensions.
     • before adding or editing the core files.
     • regularly, to safeguard the content that is added.
       • The time span will vary depending on the type of site you have and the number of visitors and changes that are occurring to your site. Busy retail or forum sites need to be updated at least hourly, if not even more frequently.
2. Manually overwrite the joomla_root/ directory
   1. Download a copy of the Joomla Full Stable Package for 2.5.x
      1. Open this archive locally on your PC.
         • If on Windows do not use M$ own archive manager - download and install 7-Zip.
      2. Delete the installation/ directory from the opened archive.
   2. Using your FTP client
      1. Upload the files to the host joomla_root/ directory (where Joomla files and directories are already located).
         • Again if you are on Windows do not use M$ own software - download and install either WinSCP or FileZilla.
         • Ensure the Default Transfer File Type is set either to Auto or Binary.
      2. Overwrite the files that are already there YOU MUST KEEP THE SAME FILE HIERARCHY
3. Automated Overwrite of the joomla_root/ directory
   1. Go to Joomla Downloads Page
      1. Identify the latest Joomla Full Stable Package 2.5.x file link from the listed files in your preferred archive format - zip being the most common used.
      2. RIGHT-CLICK that link.
      3. CLICK Copy Link Location (Firefox) or Copy Shortcut (Internet Explorer)
   2. Go to the Extensions=>Extension Manager->Install tab
      1. RIGHT-CLICK the text field for Install from URL (making sure any existing text is selected too).
      2. CLICK Paste (to paste the link from the Clipboard).
      3. CLICK Install.
   3. If you get a timeout error whilst doing this...
      • CLICK Go back one page button on your browser
      • CLICK Install again next to the Install from URL field
        NOTE: This may happen more than once depending on your connection speed, etc.
4. Final Steps...
   1. Go to Extensions=>Extension Manager->Discover tab
      1. CLICK Discover (to identify any Extensions not already identified by the system)
   2. Now, make sure the database has been updated to reflect any changes from the process(es)
      1. Go to the Extensions=>Extension Manager->Database tab
      2. CLICK the Fix button (top right Toolbar).
   3. Make sure that you clear the Joomla cache files.
      1. Open the Extensions=>Extension Manager->Updates tab
      2. CLICK Purge Cache
   If all has gone as intended then you should now have full access to your Joomla site and its functions both front and back end.
   Please let us know.

[nibor0622]

Hi All,

Don't know if this is still applicable, but I experienced the same error while updating to 2.5.16. Method: 'Write file directly' (No FTP)

The problem was due to incorrect permissions on some directories inside Joomla. Note that correct (all directories marked green) permission in system information is insufficient for updating. The user that the webserver is running under need write permissions on all files that need updating.

[ginageick]

Hm.. first time I've encountered this.
While trying to update to 2.5.27 from 2.5.26 (update from 2.5.24 and 2.5.25 works fine!?) AND 3.3.6 on different sites/different servers. FTP layer disabled on all - folder permissions 755, files 644.

Could this just be a glitch in this update? We've had a ton of updates recently; if it was a permissions issue, I would think it would have presented itself before now?

Any input is greatly appreciated!

[Per Yngve Berg]

It must be a problem with the update server. It does not respond.

[sd12013]

TL;DR: You have to manually update from 2.5.26 to 2.5.27.

From the Joomla team...

Please delay updating your Joomla! installation to 3.3.5. Unfortunately, due to a small technical issue we need to release another version very soon. It is not recommended to install or update to 3.3.5. and 2.5.26

We are terribly sorry for this situation and we are working hard to resolve this as quick as possible.

UPDATE [Tue, Sep 30, 2014 22:03:02] Just a notice: if you already updated, don't worry, everything is ok. The only problem is that you will have to update to the upcoming version manually. But there is no any danger.

[MikeS]

Would it not be better to correct the problem in the update file?
This situation does not leave a very good taste in the mouths of those experiencing this silly error!

[Per Yngve Berg]

It's fixed in 2.5.27. Those you already have installed 2.5.26 must do a manual update.