Jul 27
Update Manager 1.5.1 Final Released!
Hi all, I’m happy to announce that I’ve released the final version of the update manager. I would kindly ask all those who downloaded and installed the beta versions to update to the final release going forwards. There is a small introduction with links to the latest release on my open source consulting site as well as a walkthrough of the process. This is the first stand alone release of the tool from the Advanced Tools package and I’m going to update the Advanced Tools package to incorporate this update sometime tomorrow. I’ve also applied to have this extension listed in its own right on the JED as well to make it even easier to find. Check it out and as always if you have any issues, let me know through the comments.
For those who had earlier versions of the extension installed, you will probably be getting the following message (or have issues updating to 1.5.12): Parsing XML Document Failed: Not a JUpgrader definition file!
Updating to this version of the update manager will resolve those issues, so what are you waiting for? Update!
49 comments49 Comments so far
Leave a comment
Updated to this latest version and gave it a test ride.
Everything went as expected and I manually patched the issues with 1.5.13 with the related patches found here:
http://forum.joomla.org/viewtopic.php?f=430&t=423159&start=0
Thanks for the good work pasamio. ;o)
Kris…
Thank you in advance for your work Pasamio!
I’m going to try.
Regards,
Young
Thanks mate. This makes updating Joomla 1.5 a snap. Especially handy when you manage over 20 Joomla sites. I still don’t understand why this is not included in the core code, like wordpress.
This product exactly won’t be in 1.6, but something very similar will hit 1.6 with the ability to update other extensions. WordPress’ updater annoys me because it seems to want to force me into FTP mode on servers that I have FTP disabled on because they don’t need it and I control those servers completely. But yes, 1.6 will have similar functionality.
Hi,
I just installed Advanced tools on a 1.5.11 site yesterday, and the updater did not work, so I was thrilled to see this update today. However, when I tried it on the same site it didn’t work either – here’s the error message:
Update file does not exist: /tmp/jupgrader.xml
Parsing XML Document Failed!
I did get a warning on the main page:
Warning: Potentially invalid temporary path.
Configured path: /tmp
Suggested path: /home/***EDITED***/public_html/tmp
but didn’t see a way to change that. Am I missing something very obvious? And I don’t really know about the whole proxy server deal…
Thanks for all the great work you do!
Copy the path that is provided and paste it into the temporary path box in your global configuration, save it and then try the updater again. Need to write that down somewhere…
Brilliant Sam
Have had a couple of sites throwing the error at the bottom.
Every thing “appears” to function as it should from the front end and admin … just wondering if I’ve created a time bomb and something will go wrong.
One was from 1.5.11 the other from 1.5.9
Error Loading Modules
MySQL server has gone away SQL=SELECT id, title, module, position, content, showtitle, control, params FROM jos_modules AS m LEFT JOIN jos_modules_menu AS mm ON mm.moduleid = m.id WHERE m.published = 1 AND m.access <= 2 AND m.client_id = 1 ORDER BY position, ordering
Hi yerg, thats interesting – would indicate that that something has taken too long. The component is rendered in line which appears to be causing issues for the rest of the load. Perhaps it is a slow server. The newer releases should cause any problems, the page load might have caused that error but unless you received a time out message or similar from PHP then it should be fine.
Worked like a charm! Thanks!
Have installed latest update manager, but I get the same “Update file does not exist” error mentioned above. My temp directory in the global config file is just as it appears in the error message. The jupgrader.xml file is actually not in that folder. Did something go wrong in the install of the component? What else could be the problem?
Is your temporary directory properly writeable by what ever method you are using? e.g. FTP or direct file writing?
All other components load to it with no problems. Using the file manager from my hosting control panel, I see the folder has read, write, & execute checked. My exact message reads: “Update file does not exist: …/trinitywestmemphis.com/jo/tmp/jupgrader.xml
Parsing XML Document Failed!”
How does the jupdate.xml get into the temp directory in the first place?
Update… I saw a similar message on another site. The file referenced on that site was “http://jsitepoint.com/update/packages/joomla/update.xml” On a whim I copied that file as jupgrader.xml into my tmp directory. Now I got to step 2 and selected the 1.5.14 patch, but got another message: “Download Failed: cURL transfer failed(23): Failed writing body(46)”
Could use some help.
So there is no warning from the extension that the temporary path is set incorrectly?
The extension itself downloads it and the installation package to it. Normally if this can’t happen it is because you’ve either misconfigured your global Joomla! temp path to somewhere that you didn’t mean or it just can’t write to that directory using what ever method. I have seen one strange issue with pathing and FTP mode that I’m still trying to work out but it should be obvious that the path that the extension is trying to write to is distinct to where you think it should be writing to (in the error message that is).
If you set it to cached mode (under params on the first two screens) you can download the XML file manually and put it into place as jupgrader.xml and then download the package file (it’ll give you thelink in step two) and upload that to your Joomla! site it should extract and go from there.
Give me link to the jupgrader.xml file and I will try the manual route.
http://jsitepoint.com/update/packages/joomla/update.xml
Need to write that down somewhere formally. Just need to grab it and call it jupgrader.xml in the site and you’re set. jupgrader.xml is actually a legacy file name from the 1.0 times when it was actually called that file. So you should have the file already, you just need to grab the link to the other file and put it in the same place, flick it to cached mode and you should be done.
I changed cache to yes and I get the same error as before on the second step. After I select either full or patch package – “Download Failed: cURL transfer failed(23): Failed writing body(46)”
Would you be able to mail me details of the site so I can have a look over and see if I’ve missed something? pasamio AT gmail DOT com is my address if you’re happy for me to see if I can see what I’ve missed.
Cheers!
Happy to. What details do you need specifically?
Are you looking for configuration.php or access to my site?
Just an admin username/pw and admin location so that I can have a quick look around and see how its all put together. I have to be missing something simple, it shouldn’t be complicated
OK, I’ve sent the info.
Any new development on this issue?
Not yet, I’m catching up on everything after a bit of travel.
Hope you enjoyed yourself while you were away. Any news on trying to use the updater. Surely I’m not the only person experiencing this problem.
Hi –
I have been reading the forums in search of an answer to my difficulties with getting the updater to work on the site I’m busy with. Joomla 1.5.14
I have tried to follow the advice given. I am not succeeding. Does anyone have another way – simple as possible – to help walk me through this? please?
I keep getting the following error message after clicking on the link:”download the update file >>>”
Warning: ftp_chmod() [function.ftp-chmod]: Could not change perms on /public_html//tmp/jupgrader.xml: No such file or directory in /home/helpingh/public_html/administrator/components/com_jupdateman/libraries/joomla/filesystem/helper.php on line 100
Update file does not exist: /home/helpingh/public_html/tmp/jupgrader.xml
Parsing XML Document Failed!
Forgive me if I am repeating the same question/problem.
I’m running into the same issue – I verified the Temp directory is set correctly, and permissions on it were event set to 777, but it still could not seem to place the file into that directory. I’ll keep an eye on this thread, and if there’s anything I can do to help troubleshoot things, I will be glad to help.
I am having the same issue, which Im guessing has something to do with file permissions. I am using the cached version of the updater. I have downloaded the XML file and the patch and put them both in the tmp directory. This is the error I get once the patching process starts….
* JFTP::write: Bad response
* Unable to write entry
Failed to extract archive!
tmp directory set correctly. File permissions on that directory are 777. FTP settings in Joomla are correct. Gonna do the upgrade manually now (cause I need to get it done) but I have a duplicate test environment available.
Hi, I am having this issue too and am really struggling to find the cause of it. I’ll keep an eye here too in case anyone comes up with a fix. Thanks in advance.
I’m having the same issue. I downloaded and manually installed the jupgrader.xml file from the link above which resolved the Update file does not exist: but am getting MD5 checksum errors now.
Same problem with these errors. I’ve been trying for hours…
in case this is helpful for anyone, I posted this on another thread too: I finally got this to work by doing the following:
1) This problem was on a LAMP with a PLESK control panel. In Joomla the path to the Temp-folder in the Global Config I defined as such:
/var/www/vhosts/domain.com/httpdocs/tmp
2) In /var/www/vhosts/domain.com/conf/vhost.conf I defined the following
php_admin_flag engine on
php_admin_value open_basedir none
Now if you go into your Joomla admin under PHP Settings you should see: Open basedir: None
I successfully used 1.5 extractor; fopen; Cached Update: No. If you have curl I see no reason this won’t work also.
This is a really great script! I didn’t think there was a script like this. Such a smart and simple extension, I’ll install it with every joomla site I develop in the future. 🙂 cheers /E
Came to this blog looking for a solution to the “Update file does not exist: /tmp/jupgrader.xml
Parsing XML Document Failed!”
My temp path was correct [as was a few others here]. So I tried turning off the “FTP Settings” in Global Config and the install worked.
Everytime I install the updater…it creates the folder, and lists it under components, but when I try to use it I get a white screen. Using my FTP the folder created during installation is empty. I have tried it about 20 times.
A white screen sounds like you’re on PHP4, check that you’re on PHP5 and also if that doesn’t work bump up your error reporting (Global Config, Server tab IIRC) and see what message you get from there
Im having a lot of troubles with this.
After installing the updater I got a message sying that jupgrader was missing in the tmp-folder. Looking through the component-folder com_jupdateman I realized it was totally empty. I do not know how I could have a menu-item saying updatemanager.
I then extracted the files in the tar-file and uploaded them through ftp to the folder and uploaded the upgrade.xml-file that I found mentioned somewhere in this blog to my tmp-folder.
Now I get this message:
Fatal error: Call to a member function name() on a non-object in /hsphere/local/…EDITED…/cms/administrator/components/com_jupdateman/step1.php on line 54
Why am I having so many trouble with this….
I simply cannot get this to work with FTP enabled in the global configuration!
The tmp directory is correctly configured.
Simply nothing is written to the tmp directory – not jupgrader.xml, or the patch file – though the script does not return any errors and must assume they are downloading successfully.
Surely if FTP is enabled the script shouldn’t be writing directly to the tmp directory? The point of the FTP mode is to write files as the user and not the Apache process.
I just don’t see how this script can ever work with FTP enabled. Even if the jupgrader.xml was actually written to the tmp directory (I’ve emulated this) then it fails on ftpChmod’ing it because the file is owned by “nobody” (the Apache process” and not the FTP user and obviously doesn’t have permissions to the file!
I was having the same issue as EJSTark. After reading a few of the other comments related to FTP, I turned FTP off in Global Config, and the updater worked like a charm in cURL mode (didn’t try fopen). After the update, I just turned FTP back on.
I was getting the same errors as “flasp” mentioned above. I uninstalled the update manager and reinstalled. I got as far as Step 3 – then I get an Error 500 – Internal server error message: An internal server error has occured!
Please try again later.
Any help would be appreciated.
I use update manager on about 20 sites. I never had a problem on any except with those hosted by a particular company. I get the chmod error and /tmp/jupdater.xml error and cannot even get passed step 1. I have checked for differences between the php.ini’s and there is no difference they are using identical setups but somehow one gives errors and the other doesn’t.
Hi –
I’ve been slowly resolving errors encountered with this, but finally hit a roadblock I don’t understand and can’t get past.
When running the updater, on the final screen, I get the error:
* Unable to write entry
Warning: file_put_contents(/home1/___site____/index2.php) [function.file-put-contents]: failed to open stream: Permission denied in /home1/___site____/libraries/joomla/filesystem/file.php on line 298
Failed to extract archive!
I’ve changed my configuration to all the various suggestions listed above, but each time I get a ‘failed to extract’ error. What’s the next step? Thanks!
Jen
So that problem is file permissions and I’m not entirely sure how you can fix that because it varies from server to server. If you don’t have FTP mode enabled then this will likely fix the problem for you however if you have installed extensions in this mixed mode you’re probably going to find that you’ll want FTP mode to update the site and then disable it to return it to normal operation. Check with your hosting provider for more details or perhaps even switch providers to one where this won’t be an issue (my personal recommendation is Rochen).
Thank you. You made upgrading kinda fun
Hey,
I have had a lot of trouble with using this plugin on a clients website, but have finally figured out what the issue was. Maybe this will help someone else…..I was getting an error with both the fopen method and the curl method. All permissions etc seemed to be fine, but I could not get past the error.
I discovered that the hosting account for the website does not allow outgoing connections from the website unless they are approved. It does however generate a list of outgoing connection attempts, and from that list I was able to enable the IP of joomlacode.org (206.123.111.164). After adding that IP, I tried again, and it still did not work 100%, but it got one step further than before. It now allowed me to choose the update patch or the full package, but then would produce an error again when I chose the update package.
I then added a similar IP from my list (206.123.111.167) which I think also goes to joomlacode.org, and also one which goes to awaken.pasamio.com (69.60.121.193).
After doing this, I was able to complete all steps and upgrade the site successfully.
Hope this info helps anyone in a similar situation.
Just another vote for turning off FTP in the Global Config panel…that did the trick for me!
Thanks for this Updater !!!
couldnt get it to work until i read thru this thread-
then i went back in,, and where the Installer said “suggested path” when i began,, i copied and pasted that path into Global Config where /tmp had been,, this DID the trick, and Install-Upgrade was Successful !!! However,,, i still cannot EDIT any of my Articles,, its been a year since i made this site,,(had injuries from an accident),, and now that I’m able to try to make some changes,, I Can’t Edit,, help ?? hahaha,, thanks,, Ima Rookie,, JB
I am getting the same problem as Paul in the previous post
Paul January 4th, 2010 3:35 am
I get a Failed to extract archive! error. I don’t understand Paul’s solution. Curl is not enabled and I am just using a local wamp installation to test the extension. The error gives me no information on where the archive is written so I don’t understand where to look for permissions. This just a windows box. The tmp directory and all subfolders have full permissions. Is it because I am on a windows box and it doesn’t know how to extract a .tar file maybe?
Thank you.
Wow! Thanks for this program. I’ve been having issues updating and this saved me so much time. I really can’t thank you enough. I’ve tried jupgrade and it just wouldn’t load no matter what I tried, then I found you.
THANKS