1 dondonakal Apr 29, 2009 17:04
3 edb Apr 30, 2009 00:01
I'm thinking that should have been "2.4.6 has been out for ages" yah?
Sorry dondonakal, but with such little info available (specifically a link to the actual error) the best that can be said is that the 1.* generation is almost entirely obsolete. I've no idea if upgrading will cure this problem, but at the very least you should upgrade to 1.10.3 ... and in a perfect world to 2.4.6 - even though there is no promise this will resolve the problem.
4 dondonakal Apr 30, 2009 14:56
thanks..yeah my boss told me to look into upgrading the app into 2.4.6, but as i am very new to b2evolution, i am a bit scared of breaking something..
5 edb Apr 30, 2009 15:13
Back up your files, back up your database, upgrade. Something goes wrong, restore the original files and database. Not so bad eh?
Your /media/ folder needs backing up especially because b2evolution doesn't know anything about it. Your /conf/ folder has the bits to connect to the database, though I've no idea which file it was way back then.
DELETE all the files from your server before you upload your new ones. That way you won't have a ton of folders and files left behind that aren't used anymore.
Oh and you will lose your skin. Biggest pain in upgrading is losing your skin.
6 yabba Apr 30, 2009 17:28
EdB wrote:
I'm thinking that should have been "2.4.6 has been out for ages" yah?
It took me ages to change my clocks, when DST kicked in, as well :roll:
¥
It may interest you to know that 2.4.5 has been out for ages ;)
¥