1 joanmvf May 21, 2009 19:24
3 edb May 21, 2009 21:06
Or [url=http://forums.b2evolution.net/viewtopic.php?t=18548]this ancient post that is very like that ancient post only isn't set up for printing[/url] ;)
4 yabba May 21, 2009 22:26
EdB wrote:
Or [url=http://forums.b2evolution.net/viewtopic.php?t=18548]this ancient post that is very like that ancient post only isn't set up for printing[/url] ;)
I knew we kept you around for a reason :D
¥
joanmvf wrote:
You may want to reference [url=http://forums.b2evolution.net/viewtopic.php?printertopic=1&t=18548&start=0&postdays=0&postorder=asc&vote=viewresult&sid=1483126f5b6e92ef2c03cfe9575a6753]this ancient post[/url].
You should have an backup of your database ...quite likely you will need to use the upgrade process of an b2evolution instance (version 3.x maybe?) to fix your issues.
By the way, I visited your blog --you are better off stopping your server instance just to make sure you are not exposing yourself to an cracker attack. I can see the error that you describe.
Good luck!