WordPress/Mandigo/Upgrading
From onehertz
Contents |
[edit] Upgrading Mandigo
Upgrading Mandigo is generally only a matter of uploading the new files, overwriting the existing ones.
- If you haven't made any modification to the PHP files, and if you haven't overwritten any of the standard images, all you have to do is upload the new files. The settings made on the Theme Options page will remain untouched.
- If you only have uploaded your own header images to the images/headers/ folder, there is nothing to worry about: since these files do not exist in the theme zip file, they will not be overwritten when you upload the update.
- If you have modified a scheme file, be it the CSS file or some images, you can simply upload the new theme files, except those you have edited. On a side note, the best way to customize a scheme is to create your own.
- If you did modify some PHP files, you will have to reapply the same modifications to new theme files. Please note that most modifications, such as including some javascript or some style rules can be done using the HTML Inserts feature (see the tab next to "Theme Options" in your WP dashboard).
Remember it's always a good thing to backup your files prior to updating. Even if you don't remember changing a file, just download the full theme folder from your hosting account to your computer. It only takes a few seconds and you can't be too cautious!
[edit] Upgrading from a pre-1.34 version
The file structure has changed in Mandigo 1.34. A set of functions will take care of moving the files for you provided the theme directory is writable by the web server. The minimal permissions depend on several factors and differ from host to host so the easiest way to let the web server move and delete the files for you is to give it full permissions, that is to recursively chmod 777 the whole directory. The actual method to so also differs from an ftp client to another, but try right-clicking the mandigo/ directory and look for a "chmod" or "set permissions" menu, then set the permissions to 777, and have them applied to all sub files and folders. Also note that this must be done PRIOR to uploading the files from the Mandigo 1.34 archive.
Once the new files are up and the permissions are set, just head to the Theme Options page to trigger the upgrade functions and check if Mandigo detected something wrong during the update process. If for a reason or another some files can't be moved, the theme will display an error message at the top of the Theme Options page.
Below is the list of files that have moved or changed names in 1.34.
| old | new |
| ./options.css | ./backend/css/options.css |
| ./farbtastic.css | ./backend/css/farbtastic.css |
| ./js/farbtastic.js | ./backend/js/farbtastic.js |
| ./images/farbtastic_marker.png | ./backend/images/farbtastic_marker.png |
| ./images/farbtastic_mask.png | ./backend/images/farbtastic_mask.png |
| ./images/farbtastic_wheel.png | ./backend/images/farbtastic_wheel.png |
| ./option-headoverlay-on.jpg | ./backend/images/options-navigation-stripe-on.jpg |
| ./option-headoverlay-off.jpg | ./backend/images/options-navigation-stripe-off.jpg |
| ./option-stroke-on.jpg | ./backend/images/options-blogname-stroke-on.jpg |
| ./option-stroke-off.jpg | ./backend/images/options-blogname-stroke-off.jpg |
| ./images/attention_catcher.png | ./backend/images/attention_catcher.png |
| ./js/jquery.dimensions.js | deleted in this version |
If you can't get the theme to move the files, you may want to try moving them by hand. If this doesn't work either, you can dismiss the error message and live with the duplicate files.
[edit] Upgrading from a pre-1.33 version
Some classes and tags have changed in 1.33 so if you have created or customized your own scheme, you will need to change some CSS selectors:
| old | new |
| .calborder | .datestamp |
| .cal | .datestamp div |
[edit] Upgrading from a pre-1.26 version
If you are upgrading from a previous version and you had made modifications to either a scheme stylesheet (eg. blue.css) or you had overwritten some of the default images, make sure you move these files to new appropriate directories. My advice would be to create a new scheme, even if yours is only slightly different from the default one, as this will make future upgrades even easier.
Once your blog/site looks the same as it used to, we can safely delete these files/dirs:
- stylesheets: blue.css, green.css, orange.css, pink.css, purple.css, read.css, teal.css
- thumbnails: scheme-*.jpg
- images sub-directories: images/blue/, images/green/, images/orange/, images/pink/, images/purple/, images/red/, images/teal/
