PDA

View Full Version : vbulletin_important.css location


VodkaFish
04-03-2009, 05:05 PM
I made a few style edits and after I saved them the funkiest thing happened to my vbulletin_important location reference - the domain disappeared.

Instead of:
http://www.domain.ext/forums/clientscript/vbulletin_important.css?v=xxx
It's now:
/clientscript/vbulletin_important.css?v=xxx

Because of the / it's not being called correctly.

Where can I find this reference to fix it?

KevinL
04-03-2009, 05:13 PM
It's supposed to be there isn't it? :confused:

VodkaFish
04-03-2009, 05:30 PM
Not absolutely referenced.
If you have your forum in /forums/ and it's looking for /clientscript/ instead of just clientscript/ you're going to have problems.

KevinL
04-03-2009, 05:44 PM
ahhhhh I see what you're saying! Sorry about that! haha

Well, what did you change right before that happened?

Lynne
04-03-2009, 05:45 PM
You said you did some style edits and then this happened. Exactly what did you do?

VodkaFish
04-03-2009, 06:01 PM
Styles & Templates -> Style Manager -> Main CSS (in my template group)
Changed a couple of font colors/weights/sizes.
Hit "Save" on the very bottom so it did them all at once.

Lynne
04-03-2009, 06:32 PM
Doing anything in the Main CSS page doesn't affect vbulletin_important.css in any way. I'm thinking you must have done something else that is effecting the path for that file. Try disabling your modifications and see if the problem goes away. Don't forget that disabling modifications also means removing any htaccess code you may have added for a mod.

VodkaFish
04-03-2009, 06:49 PM
All I'm saying is the path to the file was affected, not the file itself. I can't find where the path to that file is written. If I could, I'd replace it with my path or backtrack properly.

Lynne
04-03-2009, 06:52 PM
Did you try what I suggested - disabling your plugins? Also, try this:

Create a new style with no parent:

Styles & Templates > Style Manager > Add New Style
Parent Style: No Parent Style
Title: Default vBulletin
Allow User Selection: Yes
Save

Then browse the site using that totally default vbulletin style - do you still have the same problem?

VodkaFish
04-03-2009, 07:25 PM
I tried disabling plugins, nothing changed (outside of a few seconds of "wtf is going on" IMs).

If I use another style, I do get the full url back, like such:

<link rel="stylesheet" type="text/css" href="http://www.domain.ext/forums/clientscript/vbulletin_important.css?v=xxx" />



As my original edits were in "Additional CSS Definitions" I reverted it just for the sake of it, but nothing (so I put my edits back).

Lynne
04-03-2009, 07:31 PM
Check the template that the link is being output from. See if it is the same in the non-working template as in the working (default style) template.

To find the template - vboptions > General Settings > Add Template Name in HTML Comments > set to Yes . Then go back to your page and view the source code and you will see the name of the template called around your part of the code. Sometimes the template is the one mentioned at the very top of the page source.

VodkaFish
04-03-2009, 08:18 PM
Did that, confirmed it's in headinclude. Things looked similar between the two, so I just went and copied the code over from the working site. While the code took, it did not change the url for vbulletin_important.css. So it appears it's not a template error.

Thanks for the suggestions so far.

Is this possibly cached somewhere? Could a full cache dump help? I'm not entirely familiar with the way vB caches parts of the forum.

Lynne
04-03-2009, 08:39 PM
I don't suppose you have vBoptimize installed?

VodkaFish
04-03-2009, 09:19 PM
No, I don't.

Lynne
04-03-2009, 09:34 PM
That's very odd. I can't think of anything else at the moment. Maybe someone else will come up with an idea.

VodkaFish
04-08-2009, 05:33 AM
I wound up going into the db and editing the field to add my domain to the css url.

I then replicated the issue by saving the "main css". Maybe it is a plugin I have that does something upon save, but I haven't tracked it down yet.