|
|
61.
|
|
|
Do <strong>not</strong> install the current version of b2evolution right now. Instead, download b2evolution version 1.x. You can download <a %s>almost any version of b2evolution here</a>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2.src.html:38
|
|
|
62.
|
|
|
Follow the instructions incuded in b2evolution 1.x to upgrade from b2/Cafelog.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2.src.html:40
|
|
|
63.
|
|
|
Come back to the current version of b2evolution and <a %s>upgrade from b2evolution 1.x to the current version</a>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2.src.html:42
|
|
|
64.
|
|
|
Backup all your b2evolution files. Take special care of the files you may have modified, including <strong>/conf</strong>, <strong>/skins</strong>, <strong>/plugins</strong>, your <strong>/media</strong> directory and possibly stubfiles, hacks or custom templates...
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2evo.src.html:36
|
|
|
65.
|
|
|
You should also backup your database if you can. This functionality should be provided by your host.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2evo.src.html:37
|
|
|
66.
|
|
|
If you are upgrading from a version prior to 2.0, we highly recommend you clean up outdated files. To achieve this, delete your b2evolution folders <strong>except /media</strong>. Folders to delete include /admin, /conf, /cron, /htsrv, /inc, /install, /plugins, /skins, /skins_adm, /xmlsrv. Depending on your version, you may not have all of these folders on your server. Also, again, make sure you have a backup before deleting.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_b2evo.src.html:38
|
|
|
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
|
