CSS issue after upgrade to vB 4.0.1

sinucello · February 18th, 2010, 04:26 AM

Hi,
I upgraded from vB 3.8.4 to 4.0.1 and PP 6.2.3 to 7.0.1. Now the layout of the gallery is wrong, I think the CSS-files are missing. You can see the page here:
A community photo gallery - Wunderkessel Fotogalerie

Could you please help me to fix this? I also noticed that in the admin section the integration options are all labeled with vb3 and not vB4. Does this indicate that something went wrong during the upgrade or are the labels just vB3 and do work for vB4 also?

thank you - all the best,
Sacha

Chuck S · February 18th, 2010, 06:39 AM

Interesting looks to me like you have some plugin installed that is conflicting.

If you turn off VBSEO or whatever plugin you have active does photopost appear correctly?

Your style is clearly loading

sinucello · February 18th, 2010, 06:45 AM

Hello Chuck,

you got it. After upgrading to vB4.0.2 all plugins were disabled automatically but then I installed the new vBSEO 3.5.0 RC2. I turned vBSEO off now and the gallery looks all right:

A community photo gallery - Wunderkessel Fotogalerie

Hm, could you please look after this? I think a lot of vB owners are going to use vBSEO with vB4.

Ciao,
Sacha

Chuck S · February 18th, 2010, 06:53 AM

Sasha

I beleive vbSEO is looking into the issue. However the correct course of action is to go into your vbSEO admin panel and where you can specify directories that vbseo does not touch enter your photopost directory.

Placing Photopost directory in the do not touch settings in your vbseo panel should work fine.

sinucello · February 18th, 2010, 10:26 AM

Hi,

thanks but that didn`t help. I found out that there are already threads in the vBSEO support forum about this (exclude gallery won`t work) and added my problem to an existing german thread:
Photopost Lösung gesucht - vBulletin SEO Forums

I hope they`ll find a solution. I still don`t understand the problem as my PP dir is a sibling of the forum dir and not a child. So why does vbSEO affect the gallery at all? We`ll see.

all the best,
Sacha

Chuck S · February 18th, 2010, 10:45 AM

Well I can only tell you what users have posted here about vbSEO and there solution to there issue.

Our code to support vb4 is really simply as all we do is check the vbulletin simply_version to grab the vb version and then load the appropriate vb stuff based on whether your using vb3 or vb4.

If you turn off vbseo you can see things work fine

Now the one thing I see on your site is your bburl setting in vbulletin appears to be empty or vbseo is blocking that variable

see where we define this in header-inc.php

Code:

Content visible to verified customers only.

and then the css code

Code:

Content visible to verified customers only.

So either your bburl is empty of vbseo is affecting the setting of variables which is what we have already shared with them.

sinucello · February 18th, 2010, 12:43 PM

Hi,

Quote:

Originally Posted by Chuck S

So either your bburl is empty of vbseo is affecting the setting of variables which is what we have already shared with them.

you`re right again.

In vBulletins headinclude template the base href is filled with the variable bburl. After I replaced the variable with a text-string, everything works fine now.

So if someone has the same problem, just replace:

Code:

Content visible to verified customers only.

with

Code:

Content visible to verified customers only.

or whatever your forum URL is.

all the best,
Sacha

Chuck S · February 18th, 2010, 12:58 PM

Sasha

Just a quick point you set your base forum url in your vb admin settings for the url etc in there admin then that variable would not be empty I would think.

sinucello · February 18th, 2010, 01:02 PM

Hello Chuck,

Quote:

Originally Posted by Chuck S

Just a quick point you set your base forum url in your vb admin settings for the url etc in there admin then that variable would not be empty I would think.

yes, the value is set there correctly but somehow vBSEO causes the var to loose it`s value when the headinclude template is parsed in PP. I don`t know what happens under the hood but if you replace the var with a hard-coded string it works. Not a nice/clean solution but I don`t have the time to investigate any further.

Ciao,
Sacha

Chuck S · February 18th, 2010, 01:05 PM

Yeah make sure you convey that issue to vbseo so they can investigate there code and see what they nullify.

What is nullified with vbseo appears to not be consistent. one person with vbseo has one issue and another has another issue.

sinucello · February 20th, 2010, 09:00 AM

Hi,

vbSEO RC2 Final has been released and solved the problems. PP and vBSEO work together now without any code changes on my site.

Ciao,
Sacha

Chuck S · February 20th, 2010, 09:52 AM

So no more vbSEO doing whacky stuff.

Thats a good thing