Trying to update to vBlog 2.0 PL1 and having issues?

[RedGTiVR6]

EDIT: Sorry! The title should read vBLOG, not vBulletin!

I'll upload the files and when I try and go to the page, nothing comes up.

It's like nothing is there....I get a page that basically says it can't find that page. I check and blog.php is loaded in the right location, but http://forum.xxx.xxx/blog.php doesn't show up...

Now we do have vBSEO installed, so i'm wondering if it might be related to this?

Our current blog install is linked as follows: http://forums.xxx.xxx/blogs

Once I drop the new files onto the server, then try and access the blog, using the same link (/blogs or even blog.php) nothing happens....

I'm upgrading from 1.0 and according to the directions, it says to just upload the files and that's it...

Anyone know if anything I've missed?

Thanks in advance.

I'm running vBulletin 3.8.1 and vBSEO 3.2.0 btw.

[snakes1100]

Have you tried checking the error log for the webserver apache/iss?

If disabling vbseo via the product manager dont yield results, the next best thing is tailing the error log on the server when you visit that link.

Might want to make sure you uploaded the files in ascii and not binary, check the file permissions as well.

[RedGTiVR6]

I'll check these things tomorrow night for sure. Thanks!

[Dismounted]

If you are having trouble with an official product, please open a support ticket or post over at the vBulletin.com forum.

[RedGTiVR6]

That's nice and all, but I know that as soon as I would do that, they would point the finger at an unsupported product that I have installed. That's why I'm trying to figure out the ACTUAL problem first. If I find out that it's something to do with vBlog its self, then I'll head on over there. I just want to be sure first.

I was trying to avoid being told to go somewhere else for help, but it looks like I didn't avoid that afterall. I love how that works.

Thanks.

[Marco van Herwaarden]

To troubleshoot this, please remove any hacks and disable your plugins, then see if you still have this problem.
Note: To temporarily disable the plugin system, edit config.php and add this line right under <?php

define('DISABLE_HOOKS', true);

If so, reupload all the original vB non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server.

If your problem still exists, please create a new Style with no Parent set. Now browse the forum using this new style, do you still have the same problems? If you are troubleshooting login or guest issues, you will need to set this style as board default in the vBulletin Options.

If your problem stil exists after this, then post on vB.com as your problem is not related to a modification.

[RedGTiVR6]

This appears to be an issue beyond a compatibility issue with a plug-in I'm afraid.

I've disabled all plug-ins except for the Blog plug-in, I still get the error. I've added the code to config.php, I still get the error. I've created a new style and checked it using that style, I still get the error. I have not tried uploading the files again, but I'm not sure that would fix the problem considering the type of error I'm actually getting.

When I try to go to the Blog page, I get a page telling me that there's been a DB error, but nothing telling me exactly what the DB error is.

When I then go to my profile page, I get the following DB error:

Database error in vBulletin 3.8.1:

Invalid SQL:

					SELECT
						blog_text.username AS postusername, blog_text.ipaddress AS blogipaddress, blog_text.state, blog_text.blogtextid, blog_text.title, blog_text.dateline, blog_text.pagetext, blog_text.allowsmilie,
						blog.userid AS blog_userid, blog.blogid, blog.title AS entrytitle, blog.state AS blog_state, blog.firstblogtextid, blog.options AS blogoptions, blog_user.memberids, blog_user.memberblogids, blog.postedby_userid, blog.postedby_username,
						user2.usergroupid AS blog_usergroupid, user2.infractiongroupids AS blog_inractiongroupids, user2.membergroupids AS blog_membergroupids,
						user.*,
						blog_user.title AS blogtitle,
						IF(user.displaygroupid = 0, user.usergroupid, user.displaygroupid) AS displaygroupid, user.infractiongroupid, options_ignore, options_buddy, options_member, options_guest, blog.userid AS blog_userid,
						blog.state AS blog_state, blog.firstblogtextid
					,avatar.avatarpath, NOT ISNULL(customavatar.userid) AS hascustomavatar, customavatar.dateline AS avatardateline,customavatar.width AS avwidth,customavatar.height AS avheight
					, blog_read.readtime AS blogread, blog_userread.readtime AS bloguserread
					
					FROM blog_text AS blog_text
					LEFT JOIN blog AS blog ON (blog.blogid = blog_text.blogid)
					LEFT JOIN user AS user ON (user.userid = blog_text.userid)
					LEFT JOIN user AS user2 ON (user2.userid = blog.userid)
					LEFT JOIN blog_user AS blog_user ON (blog_user.bloguserid = blog.userid)
					
					LEFT JOIN blog_read AS blog_read ON (blog_read.blogid = blog.blogid AND blog_read.userid = 1641)
					LEFT JOIN blog_userread AS blog_userread ON (blog_userread.bloguserid = blog.userid AND blog_userread.userid = 1641)
					
					
					LEFT JOIN avatar AS avatar ON(avatar.avatarid = user.avatarid) LEFT JOIN customavatar AS customavatar ON(customavatar.userid = user.userid)
					
					WHERE blog.state IN('visible')
	AND blog.dateline <= 1235692882
	AND blog.pending = 0
	AND blog_text.state IN('visible')
	AND blog.firstblogtextid <> blog_text.blogtextid
	AND blog_text.bloguserid = 1641
					ORDER BY blog_text.dateline DESC
					LIMIT 5;

MySQL Error   : Unknown column 'blog_user.memberids' in 'field list'
Error Number  : 1054
Request Date  : Thursday, February 26th 2009 @ 07:01:22 PM
Error Date    : Thursday, February 26th 2009 @ 07:01:22 PM
Script        : http://xxxxxxx/member.php?action=getinfo&u=1641
Referrer      : http://xxxxxxx/profile.php?do=editoptions
IP Address    : xxxx
Username      : xxxx
Classname     : vB_Database
MySQL Version : 5.0.51b-community-nt

[Dismounted]

It looks like some kind of (corrupted, maybe?) DB table. If you have disabled all products except for the blog, and this error still occurs, you should definitely open a ticket.

[RedGTiVR6]

Thanks - I've posted over there, but I think I'll just go ahead and initiate opening a ticket too.