1 barberj May 16, 2010 13:41
3 yabba May 16, 2010 18:23
Sounds like you got a bad copy of the zip or your ftp hasn't overwritten all files, which is why it's better to delete them first before upgrading.
What I do is create a "public_html_new" -> upload files to it -> copy across /media/ ++ any custom plugins/skins and conf/_basic_config.php ... although mine's called _config_TEST.php ;) ....
Anyway, I do that and then I hit phpmyadmin and create a shiny new db and then ask it to copy all my evo db tables and data to it.
Once it's done that I rename public_html to public_html_evo_version and rename public_html_new to public_html, hit the installer and hope like hell ;)
If it all goes tits up then I just undo the folder renaming and change the table name in my original /conf/_basic_config.php and then start again with a new zip, a new folder, a new backup
Sometimes it works first time :D
¥
4 bushleaguecritic May 16, 2010 20:13
That upgrade procedure needs "stickied" somewhere, ¥åßßå.
Succinct, clean and most of all... reversible. ;)
5 yabba May 17, 2010 18:01
I'm good at simple ;)
I'll make a sticky post with my method later
¥
6 tilqicom May 17, 2010 21:23
BushLeagueCritic wrote:
Succinct, clean and most of all... reversible. ;)
It's reversible.. at your expsense..with a simple ftp/sql backup right before you get to it (;
7 barberj Jun 08, 2010 22:26
So is it possible to upgrade directly to 3.3.3 using this method?
8 yabba Jun 09, 2010 00:11
tilqicom wrote:
BushLeagueCritic wrote:
Succinct, clean and most of all... reversible. ;)
It's reversible.. at your expsense..with a simple ftp/sql backup right before you get to it (;
None of my workflow involves ftp or backup, it's just a matter of copying shit on the server ;)
barberj wrote:
So is it possible to upgrade directly to 3.3.3 using this method?
No, but it'll allow you to restore your blog if it all goes tits up ;)
¥
9 huafeihua116 Jun 09, 2010 03:03
barberj wrote:
So is it possible to upgrade directly to 3.3.3 using this method?
I just want to know!
10 barberj Jun 18, 2010 14:32
The first error I get is Fatal error: require_once() '../conf/_config.php'
Second error: Fatal error: require_once() .../conf/_locales.php
Third error: Fatal error: require_once() /inc/locales/_locale.funcs.php
I'm copying over the inc/Locales folder
and while I'm here there is an inc/plugins folder
4th error: Fatal error: require_once() /conf/_formatting.php
5th error: Fatal error: require_once() /conf/_admin.php'
6th error: Fatal error: require_once() /conf/_stats.php'
7th error: Fatal error: require_once() /inc/_core/__core.init.php
8th: /inc/sessions/_sessions.init.php
9th: /inc/_core/_misc.funcs.php
10th: /inc/antispam/model/_antispam.funcs.php (Presume that is a plugin)
11th: /inc/files/model/_file.funcs.php (all folder contents missing apart from 1 file)
12th: /inc/_core/model/_log.class.php
13th: /conf/_upgrade.php
14th: /inc/_vars.inc.php
15th: /inc/_core/_misc.funcs.php
16th: /inc/collections/model/_blog.funcs.php
17th: /inc/collections/model/_category.funcs.php
18th: /inc/items/model/_item.funcs.php lots of files missing here
19th: /inc/users/model/_user.funcs.php
20th: /inc/_core/ui/forms/_form.funcs.php
21st: /install/_functions_install.php
This files doesn't exist in the upgrade package or the previous version so stuck!
11 yabba Jun 18, 2010 16:14
The upgrade package only contains changed files and folders. I don't use ftp so I just grab the full package, which is what my instructions are based on ;)
¥
12 barberj Jun 19, 2010 12:40
13 barberj Jun 19, 2010 14:12
What about the blog php files?
14 yabba Jun 19, 2010 15:36
I normally hit ssh and use wget to pull the zip server to server, unzip it to a temp folder, then move the files from the blogs folder to my public_html_new folder.
¥
Why should you need to delete *any* files in an upgrade. Surely the upgrade should remove any unwanted files?