In my experiance back up the site first ( files and Database ) then download the latest version.
Upload all files overwriting the ones on the server and goto www.yoursite.com/install and choose the upgrade option..
If you have altered the code for any of the snippets etc remove the tick from them when asked what to install.
Should just work ok from there....
Dont install the test site as it will overwrite all your database
Cool thanks...I’m going to try to give it go...
Thanks for the speedy reply. As always, this utility’s community is truly awesome, as is the software!
Ahh... that could explain part of my problem...
i tried upgrading MODx last week. Downloaded files, upgraded successfully, and was very happy to see how quick it was. When i next logged on, i received a Parse error and a blank screen when trying to open the manager. On reading this note, i see that my problem may have been that i ticked "install test database" or some such thing and maybe it has overwritten my files?
So here is the question...
Would it be best to reinstall the files and run the upgrade again? Or should i intall the files as a completely new installation?
i am only partially literate in these things, and do not quite know just what the impact of the overwriting of the database files may be. The site wasn’t particularly developed and there was not a great deal to lose, so i am really just trying to reduce the need to install and delete files a few times.
Paulp is correct iambemused .
However, something went horribly wrong after my upgrade with regards to the QM+ Front End Editor. After running an edit front end style, the page would refresh in this iframe as tall as what the new QM runs in? What’s that all about?
Anyway, I went back to 1.0.0 as it was working just fine without the major changes I thought I saw with user experience (front end - my client REQUIRES no nonsense confusion with this) in this new version! Maybe I didn’t give it a chance, but the data migration screwed so much up with what I had already set in place with the development stage I am at. I am not flamming at all...I love this work environment. If I could afford a donation I would give a handful of $$ right now. Alas, that’s why I’m working with this solution-->Easy to set up---> manageable to customize (though I am so still learning) and just down right loaded with a 12 guage community voice to back it up--> And its FREE!
If any one would take some time to upgrade and take screen shots, I think n()()bs like me would benefit the most!
i have just successfully upgraded, and then moved on to change the directory security settings - but in doing so i now receive an error message when trying to view the site (i can still log into the site manager though):
« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »
PHP error debug
Error: Invalid argument supplied for foreach()
Error type/ Nr.: Warning - 2
File: mysite.../assets/snippets/ditto/classes/ditto.class.inc.php
Line: 860
Line 860 source: foreach ($modx->documentMap as $null => $document) {
Parser timing
MySQL: 0.0515 s (8 Requests)
PHP: 0.0345 s
Total: 0.0860 s
i am guessing that this relates to the directory settings (i changed the 4 main /assets/ directories altered for the install from 777 to 644 and had changed the /cache directory to 666).
Is anyone aware of the likley source of my issue here?
-
☆ A M B ☆
- 2,475 Posts
I just went through this tonight... the upgrade is trickier than some of the others I’ve done. I really should take screenshots and write a how-to, but here’s the gist of it:
1. Backup your site. This includes a full backup of all files in your document root AND a full dump of your existing database. Not much bad can happen to you if you have a good backup.
2. Download the MODx 1.0.1 update to your desktop, unzip it.
3. Make a note of your database password and connection details -- I usually just copy the /manager/includes/config.inc.php for reference
4. Upload the following folders to your document root: manager/ and install/ (depending on your FTP program, you may overwrite the manager directory -- so make sure you got that config file on hand so you can reconnect to your database)
5. From the downloaded package, upload the assets/templates/help and the assets/templates/manager directories to the corresponding folder on your webserver.
6. From the downloaded package, upload the assets/plugins directories to the corresponding directories on your webserver... there are several new plugins that are required to make version 1.0.1 work, including "qm" -- just copy over any directory in the plugins directory to your web server.
7. Navigate to www.yourdomain.com/install and go through the install process -- make SURE you select UPGRADE (not clean install), and make sure you UNCHECK the option to install a sample website. You can install the new chunks, but DO NOT install the sample web site, otherwise, your existing data will be overwritten.
The install process may need your database info, so refer back to your manager/includes/config.inc.php file that you copied in step 3.
If all goes well, the new stuff gets installed, and you should be able to visit your site’s front page normally. If you still get errors, see if you are missing any particular files (e.g. the plugins/qm/something.php) -- that’s a tip that maybe forgot to upload those files or maybe you put them in the wrong place. Just compare the files and directory structure of the MODx 1.0.1 package you downloaded to what’s on your web server.
Hope this helps!
-
MODX Staff
- 730 Posts
Everett,
What problems did you encounter just uploading all of the 1.0.1 files for an upgrade? I tested the upgrade path from 1.0.0 to 1.0.1 several times using all of the files, and did not have any problems. (Admittedly, I was "testing" and not doing upgrades of actual production sites.) It would be great to work through any such problems so that upgrading is as easy as possible in future versions.
-
☆ A M B ☆
- 2,475 Posts
netProphET -- I normally would have done as you did, but I was dealing with clients’ sites that had a large number of custom assets (templates, images, scripts, modules etc.) so I had to resort to the hunt and peck method outlined above.
Personally not had any problems with the upgrade I described and woudl always say upload all of the files as then there will be no problems with code changes especially now as we are getting nearer to revolution and allot of coding is changing
