Issue: tables without borders not working in CMS Articles.

Which table code are you using in the CMS? The VW, the German TableCode version, or the default CMS table option used by vB? I'm sure I've seen a user having issues with tables in the CMS since 4.0.3...

hello Mokonzi,

same one we are looking at here I believe. I have no idea really. How do we tell, and how do I fix my problem?

hello again, I'm assuming its the stock vb editor with the VW added to it?

I'll have a look to see if I can duplicate it.

I have this issue on my install, but not certain it's VWs fault...

YES!

accordingly to vb4 support, the stock vb 4.0.3 is not producing this error. They cannot duplicate this. If my memory serves me well, I noticed this after VW was installed on version 4.0.2

All I can assume is that it's a conflict between the table bbcodes. I don't even know how the stock one works... but if it uses the [table] setup (Which I assume it does), then you'll need to adjust like you would do for the other [table] codes that are out there. Though, I'd always understood that these would stand side by side, I've just never needed the CMS table as I think VWs works far better.

How do we do this? I have many articles effected now and cannot continue to input new articles needing borderless tables until this is patched. Can you please help me?

I have never even been able to use the CMS's table editor since vB 4 came out. It just loads continuously for me, so unfortunately I haven't been able to even test this.

EDIT: Got this to occur on a fresh test board. This isn't a real fix, and should only be used temporarily if you're planning to disable VaultWiki's table code completely when the next build is released. Otherwise, you should be using the VW format in the CMS and not the WYSIWYG tools in the CMS editor.

Unfortunately, this is due to an oversight in the way custom BB-Codes are handled in vBulletin (2 different methods that frequently conflict). Essentially, you can't add an editor image for your BB-Code unless you create a record in the database - but this means you need to use a different hook than vBulletin intended if the BB-Code also has a PHP handler.

In includes/class_bbcode.php, find (2 places):
Add before:

Thanks pegasus, though I'll be sticking with your superior version. I got the continued loading, which was due to the CMS needing HTML rights for the user you are editing.

i.e. if you edit another users post, it won't let you add HTML in, whereas if you edit a user who can use HTML, it will let you use it. Or at least that's what I found with my tests earlier.

Should I still go ahead and add this?

Also, how do I deactivate the stock vb4 editor? And/or what do you recommend I do that is the best for my clients and myself long term?

If you're not going to use VaultWiki's TABLE BB-Code, you can go ahead and add it. But long term if you plan on continuing to use VaultWiki, I'd recommend using the TABLE BB-Code included in VaultWiki since it offers much more flexibility than the stock TABLE code, and can be used in non-CMS areas.

Settings > Options > Message Posting Interface Options > Enable Clickable Message Formatting Controls

I think I'm missing something because I don't see your table editor at all. I did remove the stock editor in the admin>cpanel>settings>Message Posting Interface Options> remove Editor and when I did, your editor was removed with it.
Very confusing?

I guess I didn't quite understand what you wanted to do. You can't remove just the vB editor and leave VaultWiki's buttons. VaultWiki doesn't have its own editor, it just adds buttons to vB's editor. This is the way any vBulletin modification that adds BB-Code would work.

VaultWiki doesn't have a popup with options for its TABLE code, at least not at the current time.