1 davidnewcomb Apr 29, 2010 10:49
3 davidnewcomb Apr 29, 2010 17:40
Thanks, it is still a bug though!
4 sam2kb Apr 29, 2010 17:45
I don't know if it was fixed in b2evo 4 or not. Although you can enable a setting in config file to deal with this bug.
5 yabba Apr 29, 2010 19:26
davidnewcomb wrote:
Thanks, it is still a bug though!
It's a bug that's already been fixed in the version you're reporting it against, search the config files.
/me moves to "not a bug"
¥
6 davidnewcomb Jun 02, 2010 15:07
Having looked through it properly, I agree that it is not a bug. However it probably does point to a bug in the upgrade scripts which should have corrected the database during the database upgrade process.
I have created an article for others who may suffer from the same problem.
Missing B2evolution posts
http://www.bigsoft.co.uk/blog/index.php/2010/06/02/missing-b2evolution-posts
7 yabba Jun 02, 2010 15:15
It points to a lack of forethought in the upgrade script, not a bug ;)
Thanks for posting the article though, lets hope it helps any others that find themselves in the same position :D
¥
Please search the forum, there's a workaround for this.