Remove 'Preview' option from thread

[GooRoo]

Using the 'Preview' option instead of BBCode results in obfuscation of tables ... cramming table elements together into strings of some arbitrary length ... making them unreadable/unmanageable.

I want to prevent ANYONE from updating threads (especially tables) in 'Preview' mode.  Doing a SAVE, then re-edit (if necessary) is what I want members to get in the habit of doing, so I do not have to fix (re-instate carriage return/new line) things before I can make the change dictated by puzzle modifications.

[Ryan]

Hmm... I'd like this too.

[Brian]

A plugin won't be able to do this. No matter how much a plugin or template modification removes at the end of the day the Preview option will still be set as the default in their profile upon joining.

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Aug 6, 2015 6:33:06 GMT -8 GooRoo said:

Using the 'Preview' option instead of BBCode results in obfuscation of tables ... cramming table elements together into strings of some arbitrary length ... making them unreadable/unmanageable.

I want to prevent ANYONE from updating threads (especially tables) in 'Preview' mode.  Doing a SAVE, then re-edit (if necessary) is what I want members to get in the habit of doing, so I do not have to fix (re-instate carriage return/new line) things before I can make the change dictated by puzzle modifications.

Couldnt you just hide the preview and posting buttons until they hit the bbcode button...(with a message saying they need to hit bbcode)

[GooRoo]

Aug 6, 2015 8:42:14 GMT -8 Brian said:

A plugin won't be able to do this. No matter how much a plugin or template modification removes at the end of the day the Preview option will still be set as the default in their profile upon joining.

To me, that just sounds like a 2-part plug-in: 1) in the Profile (eliminating 'Preview' or defaulting BBCode); 2) remove the 'Preview' button from the posting section.

Of course, if the parser simply left the provided text as-is, without removing the formatting characters, this plug-in would not be necessary at all!

[Brian]

A plugin can't change your default posting mode. Just because it can hide the option doesn't mean that the forum defaults to the other option. It's only hiding the radio button visually.

You have to manually visit that page, select BBCode as your default, then save. That's why this isn't possible.

[Chris]

GooRoo, as a workaround for the specific problem you mentioned (tables), you could insert the following template on the Translate tab of the BBCode Factory Plugin to automatically pretty print tables on the BBCode tab of the editor:

Tag Name Field:

table|tbody|tr|td|th|tfoot|thead

$[directive.reuse-for-all-endtags]
$[directive.strict-space]
$[directive.phase-set]
$[directive.mode-bbcode]
$[tag.comment.
********************************************
Format bbcode tables for easier editing  
********************************************
]

{if $[tag.name]=="td" || $[tag.name]=="th"}
{if !$[tag.closed]}
{/if}
$[tag.match]
{else}
{if $[tag.name]=="tr" || $[tag.name]=="thead" || $[tag.name]=="tfoot"}

$[tag.match]
{else}
{if $[tag.name]=="table"}
{if $[tag.closed] != "1"}

{/if}$[tag.match]
{/if}
{if $[tag.name]=="tbody"}
{if $[tag.closed]}
{/if}$[tag.match]
{/if}
{/if}
{/if}

SPOILER: Click to show

SSSHHHHH this code might not be LEGAL!
<script type="text/javascript">
/* Disable Preview Tab on Proboards V5 (Global Header)*/
/* WARNING: Dictator MOD - not suitable for tree hugging freedom lovers */
(function(fn){
var W = fn.wysiwyg.prototype._create;
fn.wysiwyg.prototype._create = function(){
//force bbcode editor upon WYSIWYG load
this.options.defaultEditor = 'bbcode';
//call original from within hook
W.apply(this, arguments);
//hide the preview tab
$('#menu-item-visual').hide();
//disable keyboard shortcuts to prevent switching using keyboard
proboards.hotkeys.wysiwyg = $.noop;
//a delegate handler also exists on document for the shortcut so step on that too
$.each($(document).data('events').keydown, function( kdi, evh){
var f = evh.handler.toString();
if(/\#menu\-item\-bbcode\s+a/.test(f)){
evh.originalHandler = evh.handler;
evh.handler = $.noop;
return false;
}
})
}
})(jQuery.ui);
</script>

SPOILER: Click to show

For those who prefer to edit tables on the BBCode tab it can be daunting with table editing now geared towards table edits occurring exclusively on the preview tab with representations on the BBCode tab "mashed together" and made illegible. The BBCode Template aims to correct this and make tables once agin legible on the BBCode tab

DISCLAIMER: this is a "beta" plugin and requires further testing by the community at large before being certified as prime time ready

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Aug 6, 2015 18:50:35 GMT -8 Chris said:

GooRoo, as a workaround for the specific problem you mentioned (tables), you could insert the following template on the Translate tab of the BBCode Factory Plugin to automatically pretty print tables on the BBCode tab of the editor:

Tag Name Field:

table|tbody|tr|td|th|tfoot|thead

$[directive.reuse-for-all-endtags]
$[directive.strict-space]
$[directive.phase-set]
$[directive.mode-bbcode]
$[tag.comment.
********************************************
Format bbcode tables for easier editing  
********************************************
]

{if $[tag.name]=="td" || $[tag.name]=="th"}
{if !$[tag.closed]}
{/if}
$[tag.match]
{else}
{if $[tag.name]=="tr" || $[tag.name]=="thead" || $[tag.name]=="tfoot"}

$[tag.match]
{else}
{if $[tag.name]=="table"}
{if $[tag.closed] != "1"}

{/if}$[tag.match]
{/if}
{if $[tag.name]=="tbody"}
{if $[tag.closed]}
{/if}$[tag.match]
{/if}
{/if}
{/if}

SPOILER: Click to show

For those who prefer to edit tables on the BBCode tab it can be daunting with table editing now geared towards table edits occurring exclusively on the preview tab with representations on the BBCode tab "mashed together" and made illegible. The BBCode Template aims to correct this and make tables once agin legible on the BBCode tab

DISCLAIMER: this is a "beta" plugin and requires further testing by the community at large before being certified as prime time ready

Shouldn't a fix like this be submitted to Proboards as a bug/bugfix

[Chris]

Aug 7, 2015 2:37:02 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

Shouldn't a fix like this be submitted to Proboards as a bug/bugfix

There are threads in the support board that suggest one should either edit tables/lists exclusively on the preview side or exclusively on the bbcode side but never switch between^[1][2][3][4] and given that this problem is both relatively infrequently reported as well as some years old I would think such a bug report (which I'm sure already exists in the bug tracker given the number of reports over the years) would be in the low priority category. It was mentioned a few times that this would be addressed when the WYSIWYG is overhauled to add API access for developers but any timeline on that is unknown.

[Brian]

Aug 6, 2015 18:50:35 GMT -8 Chris said:

SPOILER: Click to show

SSSHHHHH this code might not be LEGAL!

No extra AJAX requests, no problem.

But if you have to post a disclaimer like that you really should ask first rather than incurring someone's wrath.

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Well I always heard it's easier to ask for forgiveness than to wait a week for permission.

[Chris]

Aug 9, 2015 9:16:53 GMT -8 Brian said:

But if you have to post a disclaimer like that you really should ask first rather than incurring someone's wrath.

Thanks for the clarification Brian but of course you know I would not have posted it if I had not considered it "LEGAL", my disclaimer was really tongue-in-cheek referring to the ethical aspect of removing someone's right to CHOOSE, ergo the comment in the code:

/* WARNING: Dictator MOD - not suitable for tree hugging freedom lovers */

I actually debated posting it since I am a firm believer in not taking away someone's rights.

[Brian]

Aug 9, 2015 9:23:20 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

Well I always heard it's easier to ask for forgiveness than to wait a week for permission.

*insert Kappa here*

David, Michael, and I cover all 7 days of the week and check our PM inboxes whenever we're on. If you're looking for a timely response a PM will work way better than a tag given the amount of notifications we receive daily from how often we're tagged or quoted in the Support Board alone.

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

Aug 9, 2015 10:10:20 GMT -8 Brian said:

Aug 9, 2015 9:23:20 GMT -8 P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ said:

Well I always heard it's easier to ask for forgiveness than to wait a week for permission.

*insert Kappa here*

David, Michael, and I cover all 7 days of the week and check our PM inboxes whenever we're on. If you're looking for a timely response a PM will work way better than a tag given the amount of notifications we receive daily from how often we're tagged or quoted in the Support Board alone.

A week was an exaggeration. I know you all do good job at what you do and I'm really sorry you have to deal with alot of stupid questions. I will hit up the PM next time I have a question. We really appreciate being there for us developers and users alike.

[GooRoo]

I am perfectly willing to be considered a 'dictator' on my Forum, if it means I do not have to spend sometimes an hour reversing the obfuscations before I can actually perform updates to tables when new information (or pieces of the puzzle) are provided.  The codes provided to assist me in my 'dictatorship' are much appreciated ... as indicated by my 'like' of the post.

I hope to be able to post back another reply saying how well the solutions worked ... and how delighted I am with the results!