|
67.
|
|
|
Upload <strong>all new b2evolution files from the /blogs folder</strong> to your site. We cannot stress this enough: <strong>ALL FILES</strong>! And that means you cannot reuse your default /conf files, default skin templates or default plugins if you have modified them without renaming them.<br /> <br /> Since your custom configurations, custom skins and custom plugins should be using different names, they should typically not be overwritten. Same for your media files.<br /> <br /> The single one file you must absolutely pay attention to is <code>/blogs/conf/_basic_config.php</code>. You will need to either keep, recreate or restore that file from backup (see step 1) before you can proceed with the upgrade.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2evo.src.html:39
|
|
68.
|
|
|
Run the installation/upgrade script on your server. It is located in <code>http://yoursite.com/yourblogsfolder/install</code>/ . Then, simply follow the on screen instructions.<br /> <br /> The installer/upgrader will allow you to run a database upgrade from <strong>any</strong> b2evolution version to the new one.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2evo.src.html:44
|
|
69.
|
|
|
Check the online manual for <a %s>specific upgrade instructions</a> to your new version of b2evolution.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2evo.src.html:48
|
|
70.
|
|
|
If you had hacks or other customizations to the core files, your can bring those back now. We recommend you get yourself a diff/merge tool like <a %s>WinMerge</a>. This will allow you to easily compare your old (backuped) files with the new files (even whole directories at once) and report changes accordingly.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2evo.src.html:50
|