Recent content by Cadellin

Thanks - I'll try that. Can't understand it - must be a conflict somewhere. Sent from my iPhone using Tapatalk

I must admit this problem has be scratching my head. There aren't any plugins active which mess around with the parsing or the editor and I've had a good look through your code but I can't see anything different to how I parse WYSIWYG output. A few of things I have also checked: Disabling...

Thank you Fillip H.. Sent from my iPhone using Tapatalk

Thank you. It would certainly be very useful and much loved by our editors! Sent from my iPhone using Tapatalk

Here's a sample of the type of message. I've tested it in vBMail and it produces the same result as reported. I'm not sure what you mean by "exact configuration of your TABLE BBCode". The table BBcode is native to vBulletin and I haven't modified it. 1 2 3 4 5 6

Thanks for the reply. Is there any possibility of this changing in a future update? It would be incredibly useful to be able to preserve the original template when saving a draft so it can be re-used. At the moment we have to choose between either preserving the template for re-use and having...

I've created my own custom pages using CKEditor in VB4 and they don't have the same problem. For some reason in vBMail the BBcode is partially parsed prior to being saved into the database. Just to be sure I've saved exactly the same BBcode in both products and only vBMail produces this bug...

If you "Save Draft" in a new message which has been created from a template then template is converted into a draft. Similarly if you click "Save as Template" on a draft then the draft is converted into a template.

No I'm saving in the standard mode - I haven't set a DOCTYPE at the top in other words.

If you have a table in your e-mail and you save the content whilst in WYSIWYG mode either as a draft or template then the table bbcode is converted into raw HTML making it uneditable using the vBulletin editor. If you switch to "Source Mode" (using ) in the editor prior to saving then the bug...

Same issue. Looks like a missing file or incomplete feature in the update. Can we have a fix please Fillip H. Separately my update subscription expired yesterday but I presume I will get the patch which fixes the issue as your update broke the product.

Thanks for the reply Fillip H.. Could you be more specific please? Turning on "Is Excluded Usergroup" blocks all users in the group from being mentioned at all from my tests. Basically all I want to do is turn off the usergroup ability on a couple of usergroups but leave everything else...

I've just upgrade to Pro and I'm wondering how I can prevent a specific usergroup e.g. Registered Users from being tagged on-mass without preventing everyone inside that group from being tagged seperately?