Log in

View Full Version : Why are my forums like this?


iBardia
01-18-2009, 03:45 PM
I think there is something wrong with my forums, because when I click on a category, I get this:
https://vborg.vbsupport.ru/external/2009/01/54.jpg

But when I clicked on it on another forum I go on, it looked like this:
https://vborg.vbsupport.ru/external/2009/01/55.jpg

Why is that, and is there a way to fix it?

Lynne
01-18-2009, 03:52 PM
Try disabling your plugins and see if it shows them correctly.

SEOvB
01-18-2009, 03:52 PM
Looks like you have something messed up in one of the forumdisplay templates.

iBardia
01-18-2009, 03:55 PM
Try disabling your plugins and see if it shows them correctly.
How do I do that?
Looks like you have something messed up in one of the forumdisplay templates.

Maybe..

Lynne
01-18-2009, 03:57 PM
To temporarily disable the plugin system, edit config.php and add this line right under <?php

define('DISABLE_HOOKS', true);

iBardia
01-18-2009, 04:00 PM
To temporarily disable the plugin system, edit config.php and add this line right under <?php

define('DISABLE_HOOKS', true);

Thanks.
I'm trying it now.

--------------- Added 1232301726 at 1232301726 ---------------

No.. I guess it's not the plugins

Lynne
01-18-2009, 04:04 PM
Create a new style with no parent - Styles & Templates > Style Manager > Add New Style > no parent - then browse the site using that totally default vbulletin style - do you still have the same problem?

iBardia
01-18-2009, 04:06 PM
Create a new style with no parent - Styles & Templates > Style Manager > Add New Style > no parent - then browse the site using that totally default vbulletin style - do you still have the same problem?

Still doesn't work.

Lynne
01-18-2009, 04:42 PM
Then check your settings for the forum. And also vboptions > forum display listings

iBardia
01-18-2009, 05:10 PM
Then check your settings for the forum. And also vboptions > forum display listings

What am I looking for specifically?

SEOvB
01-18-2009, 05:15 PM
Try running your forumdisplay pages thru the w3c validator it will tell you all the coding errors.

iBardia
01-18-2009, 05:23 PM
Try running your forumdisplay pages thru the w3c validator it will tell you all the coding errors.

Got me this:

Line 338, Column 6: required attribute "type" not specified.
<style>td.minitabbarttclass

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Line 391, Column 46: end tag for element "a" which is not open.
<td class="vbmenu_control"><a href="" /></a></td>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 394, Column 46: end tag for element "a" which is not open.
<td class="vbmenu_control"><a href="" /></a></td>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 397, Column 46: end tag for element "a" which is not open.
<td class="vbmenu_control"><a href="" /></a></td>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 400, Column 46: end tag for element "a" which is not open.
<td class="vbmenu_control"><a href="" /></a></td>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 403, Column 46: end tag for element "a" which is not open.
<td class="vbmenu_control"><a href="" /></a></td>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 685, Column 4: end tag for element "td" which is not open.
</td>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 687, Column 4: end tag for element "tr" which is not open.
</tr>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 688, Column 7: end tag for element "table" which is not open.
</table>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 690, Column 7: end tag for element "div" which is not open.
</div>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 691, Column 6: end tag for element "div" which is not open.
</div>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 692, Column 5: end tag for element "div" which is not open.
</div>

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 780, Column 14: character "<" is the first character of a delimiter but occurred as data.
if (todayy < 1000) {

This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 802, Column 226: there is no attribute "onload".
?"clear.gif" border="0" alt="" onload="countup();" />&nbsp;</td>

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 391, Column 47: XML Parsing Error: Opening and ending tag mismatch: td line 391 and a.
<td class="vbmenu_control"><a href="" /></a></td>

Line 391, Column 52: XML Parsing Error: Opening and ending tag mismatch: tr line 374 and td.
<td class="vbmenu_control"><a href="" /></a></td>

Line 394, Column 47: XML Parsing Error: Opening and ending tag mismatch: td line 394 and a.
<td class="vbmenu_control"><a href="" /></a></td>

Line 394, Column 52: XML Parsing Error: Opening and ending tag mismatch: table line 373 and td.
<td class="vbmenu_control"><a href="" /></a></td>

Line 397, Column 47: XML Parsing Error: Opening and ending tag mismatch: td line 397 and a.
<td class="vbmenu_control"><a href="" /></a></td>

Line 397, Column 52: XML Parsing Error: Opening and ending tag mismatch: div line 371 and td.
<td class="vbmenu_control"><a href="" /></a></td>

Line 400, Column 47: XML Parsing Error: Opening and ending tag mismatch: td line 400 and a.
<td class="vbmenu_control"><a href="" /></a></td>

Line 400, Column 52: XML Parsing Error: Opening and ending tag mismatch: body line 357 and td.
<td class="vbmenu_control"><a href="" /></a></td>

Line 403, Column 47: XML Parsing Error: Opening and ending tag mismatch: td line 403 and a.
<td class="vbmenu_control"><a href="" /></a></td>

Line 403, Column 52: XML Parsing Error: Opening and ending tag mismatch: html line 2 and td.
<td class="vbmenu_control"><a href="" /></a></td>

Line 405, Column 2: XML Parsing Error: Extra content at the end of the document.
</tr>

--------------- Added 1232343587 at 1232343587 ---------------

It's been six hours.
*Bump*

Dismounted
01-19-2009, 05:06 AM
Admin CP > vBulletin Options > Forum Listings Options

Make sure the depths allow those forums to be displayed.

iBardia
01-27-2009, 06:17 PM
*BUMP*

Please help

Lynne
01-27-2009, 06:43 PM
You've disabled your plugins, and it doesn't fix it. You've try a totally default style, and it doesn't fix it. Only thing left to do is reupload all the original vbulletin.php files since it isn't a plugin or style issue.

iBardia
01-27-2009, 06:48 PM
You've disabled your plugins, and it doesn't fix it. You've try a totally default style, and it doesn't fix it. Only thing left to do is reupload all the original vbulletin.php files since it isn't a plugin or style issue.

A totally different style doesn't work..

This is what it looks like the ACP
https://vborg.vbsupport.ru/external/2009/01/20.jpg

Lynne
01-27-2009, 07:56 PM
Then it should be fine. You have a Category with no sub-forums there. I think what you want to do is make Coppa Laws just a sub-forum of Webkindz Coast. Don't make it a Category also. Same with WC Rules, and Contestz, etc. None of those should be categories, just forums with Webkindz Coast as the parent.

iBardia
01-27-2009, 08:01 PM
Then it should be fine. You have a Category with no sub-forums there. I think what you want to do is make Coppa Laws just a sub-forum of Webkindz Coast. Don't make it a Category also. Same with WC Rules, and Contestz, etc. None of those should be categories, just forums with Webkindz Coast as the parent.

Well, they are not set to catorgories, they are set to forums. When I do that, I get this:
https://vborg.vbsupport.ru/external/2009/01/19.jpg

Lynne
01-27-2009, 08:08 PM
Well, I don't understand what is going on with your forum manager then. The only time I end up with a forum underneath a Forum heading is if it has no parent. I'm not sure what the problem is - perhaps reuploading all the original files in your admin panel with fix this.

iBardia
01-27-2009, 08:11 PM
Well, I don't understand what is going on with your forum manager then. The only time I end up with a forum underneath a Forum heading is if it has no parent. I'm not sure what the problem is - perhaps reuploading all the original files in your admin panel with fix this.

I have a lot of things in my ACP, including the vBa pages..

Should I just upgrade to 3.8.1?

Lynne
01-27-2009, 08:30 PM
I really don't know. If this is caused by, say, vBa, then doing an upgrade isn't going to fix the issue. You need to figure out what is causing the problem.

iBardia
01-27-2009, 08:32 PM
I really don't know. If this is caused by, say, vBa, then doing an upgrade isn't going to fix the issue. You need to figure out what is causing the problem.

I remember talking to my tech person once and he said the forums were set up wrong..?

Lynne
01-27-2009, 08:45 PM
Maybe so, it certainly looks that way from the picture.

iBardia
01-27-2009, 08:50 PM
Maybe so, it certainly looks that way from the picture.

He said he'd have to delete them all to do them right or something..

Dismounted
01-28-2009, 05:31 AM
If disabling your plugins do not work, please open a support ticket on vB.com.