Forum support is awful!!!

[Trevor Hannant]

@Reeve: For some reason I didn't know that. But if that's the case then I guess they should step up with a more solid support presence in the forums.

Forum Classic customers can submit tickets for the first 30 days after the first download of the software for the members area. Publishing Suite customers have ticket support for the life of the 4.x product.

The "lack" of forum support is a direct result of the number of queries coming in via the ticket and phone support routes - these are being hammered and have been since launch of vB4. Levels have dropped a bit and once the team get them down further, they'll be able to spend more time in the forums like they have done in the past.

Note that when it comes to the forums, problems such as database errors and similar are getting priority over styling and customisation issues.

[cbiweb]

Cool, thanks for the explanation.

And if I could afford to hang out here and answer styling/customization questions most of the day, I would. I've had to ask questions myself, but I'm very quickly getting to know vB4, and making extensive notes along the way. Unfortunately I have to earn a living, which cuts down on my ability to post detailed mini-tutorials for people.

[birdie]

I have had no assistance on 2 separate threads from the vBulletin support team for days now.

Why did you not do it the proper way and fill out a support ticket? The forums are NOT for official support.

[cbiweb]

@birdie: Read the whole thread. I made the same mistake of telling him the same thing. ;-)

[jwbond]

Why did you not do it the proper way and fill out a support ticket? The forums are NOT for official support.

Simple. I don't visit these forums often and did not know of the new format. Perhaps they need to make it more clear!

[jwbond]

As for the fixed width, both myself and another staff member have tried the fixes suggested in that thread within the last few mintues and successfully gotten a fixed width, centered forum. If this isn't working for you then something else is breaking that within your templates.

To troubleshoot that, temporarily disable the plugin system, edit config.php and add this line right under <?php

define('DISABLE_HOOKS', true);

Then if you still have this problem, create a new style and choose no parent style. This will force it to use the default templates. Finally empty your browser cache, close all browser windows then try again. Make sure you change to the new style and view your forums with it.

Good idea. I like the simple method for disabling plugins.

However, it didn't work. Something tells me this is once again a css issue. What is the name of the css class vBulletin uses for the forum width container? Perhaps I used the same in my css file.

[bhd]

I have had no assistance on 2 separate threads from the vBulletin support team for days now.

Sadly I must concur. I asked for support on the support ticket system a week ago and was told to post it as a bug instead which I promptly did. All I've received is a deathly silence.

I understand that staff are under the whip with the new release and all but as a paying customer, quite frankly, that's not my problem as my [paying] customers often reminding me. Not what one expects.

[s0lidgr0und]

Weird. So it was the custom code.

I thought I saw that early in the thread...

[Trevor Hannant]

Just the body class in vbulletin.css:

body {
 width:{vb:stylevar doc_width};
 min-width:{vb:stylevar doc_minWidth};
 max-width:{vb:stylevar doc_maxWidth};
 margin: {vb:stylevar doc_margin};
 font-size:{vb:stylevar font.fontSize}px;
 color:{vb:stylevar body_color};
 line-height:{vb:stylevar line_height};
}