Article Tables Broken

[bigtree]

Not sure if this is a conflict with you or 4.03.
When creating a table in an article the table now breaks.

This is what's happening

[TR]
[TD][/TD]
[TD][/TD]
[/TR]

here is my vb thread

http://www.vbulletin.com/forum/showt...r-work-for-CMS!

I deactivate vault to test for conflicts but the advanced codes still stayed active.

[Mokonzi]

I assume you added the table tags in?

[pegasus]

Since you're using vBulletin's CMS TABLE BB-Code, you should refer to this post about disabling VaultWiki's TABLE BB-Code: http://www.vaultwiki.org/threads/4341/#post10843

[bigtree]

Thanks but that didn't help. Its like the html is off. The editor creates the table but once saved the table doesn't resolve. It just shows the [TD] tags

[pegasus]

In that case, you'll have to continue the discussion at vbulletin.com. I've already given you instructions to remove VaultWiki's involvement with the TABLE code, and you mentioned that your problem persists with VaultWiki disabled.

[bigtree]

When I remove Vault, my original vb editor does not come back. Your editor is still there but with out images. What am I doing wrong?

We are using the same versions of everything>
If you do this here, what are your results?

Test:
Create New Article>insert table (no borders) >save. Look at saved article now to see if the table is broken, only showing the raw [tr] code?
Repeat this but this time create a table (with borders or grid)>save. Article tables are correct now.

My issue is the tables with no borders is not working. Is it a VW conflict or bug?

[bigtree]

In that case, you'll have to continue the discussion at vbulletin.com. I've already given you instructions to remove VaultWiki's involvement with the TABLE code, and you mentioned that your problem persists with VaultWiki disabled.

Maybe I'm missing something here.

there seems to be two pages and a third to another link that tells me its a royal PITA because it will all need to be reversed with your next release. On top of that, I don't know what part is confirmed to remove because the thread goes on extending to another link.

Could you be so kind to confirm the exact code (on one posts for us) the steps which we should do to get tables working with vb 4.0.3 ... if we... use your "Vaultwiki for vBulletin"?

Thank you so much.

[bigtree]

Ah... I think you think I am talking about the vborg table hack for vb forums created back in 2006 ?
If so.... NO, this is not what I am talking about! I am not using a table hack for the vb4 forums.

This is an issue with vb4 CMS Front Page Articles. When I installed VW, I recall this happening after.
NOTE: Using stock vb4 Article editor, inserting tables with no border something is conflicting causing the tables to be broken.

This is what's a no border table looks like after you save the Article.

[TR]
[TD][/TD]
[TD][/TD]
[/TR]

Do you understand now?

[Mokonzi]

I think I see what you mean. I'll have a play with mine to see if I can duplicate it... though I think what Pegasus is saying is that if you've disabled VaultWiki, then it should be 'fixed' if it's VWs fault. The fact it isn't suggests it's a conflict with some other mod, or a vB problem.

With the amount of things vB haven't fixed, I'm not surprised that there are new errors.

[bigtree]

I have isolated the problem!

Front Page CMS>Create New Article> When inserting a table (no borders) choose Automatic and don't fill in the table pixels and %. We confirm it doesn't work.
If you repeat this, but this time check the % box and put the value 100 in both pixel and % boxes, it works!

The problem is, I have over 200 article tables broken because before I installed Vault I never needed a value in those boxes when selecting Automatic. We now have to put a value in the pixel and % boxes to make the no border table work. Simply put: Choosing Automatic was enough. Something is conflicting with VW and vB4 now.
Can you suggest a patch that adds a value of 100 in both those boxes when selecting Automatic?

This is why its not working.

Can you please help?

[pegasus]

I already posted a file edit that will fix this problem in the report you posted. If you can't migrate your tables, just make that edit.

[bigtree]

removing this

if (empty($parser->tag_list['no_option']['table']['callback']))
	{
		// [TABLE]
		$parser->tag_list['no_option']['table'] = array(
			'callback'			=> 'handle_external',
			'external_callback'	=> 'special_bbcode_table',
			'strip_empty'		=> true,
			'strip_space_after'	=> 1
		);
	}

does absolutely nothing for this issue. You really don't understand...

[pegasus]

In your bug report on this issue, I posted this temporary fix: http://www.vaultwiki.org/issues/1408/#note6452

[bigtree]

Note: its doing this again with the new version of vw. Correction... with the new version of vB 4.0.4. if anyone else is experiencing this. The patch http://www.vaultwiki.org/issues/1408/#note6452 fixes the broken tables.

Thanks

[pegasus]

Check AdminCP > VaultWiki > Wiki Code Manager > TABLE. Edit and where it asks if it should parse in non-wiki areas, select "No". If you just don't want the VW Tables in the CMS, and still want them in other non-wiki posts, then I think that patch you mentioned is what you need.