Quick Reply BBCode Buttons (UBBC)

[Stinky666]

May 24, 2013 4:23:13 GMT -8 Chris said:

May 24, 2013 2:08:32 GMT -8 Stinky666 said:

Hi Chris,
Here to bug you again
Just noticed this new update. Does it by any chance fix this issue: support.proboards.com/thread/464916/login-registration-settings
Apparently it's being caused by your plugin.

Don't want to install this update only to have to install another one (editing plugin settings is such a bitch/pain/tedious job).

I'm not sure how and when the input type got left out and when Stinky666 (it's still there in this post) but no the newest version does not have it either so thanks for bringing it to my attention. You can manually add it by finding this line in the Javascript component and adding the red

$nosmiles: $('<input value="0" type="hidden" disabled id="' + this.element.id + '_message_nosmiles_input">').appendTo($('body'))

I'll update the nightly download later today...

--

May 24, 2013 2:08:32 GMT -8 Stinky666 said:

(editing plugin settings is such a bitch/pain/tedious job).

Ever since Proboards added the ability for plugins to set default values (saved in the PBP file itself) that "keep data" option has not worked right. It is supposed to keep your entered data from previous installs and automatically apply to newer versions but the default values (or lack of) appears to be taking precedence. This plugin comes with a couple of default entries in the custom buttons autoform and I believe  rather than doing something akin to $.extend with user data having precedence, Proboards is giving precedence to the default settings including fields left blank. I recall filing a bug report for this during beta but no fix to my knowledge was ever made. I'll remove all default values on next update to test this theory...

Brilliant, that fixed it Thanks for that.

Plugin data has never saved for me on any forum, with any plugin. It's possible it's remembered stuff on the forum itself, but although that is great (you don't wanna be using a like plugin for example, then everyone losing the like count when you upgrade the plugin), it's horrible having to copy and paste over the content from within the actual manager for plugins.

[tunescool]

i did what they asked me on the support board, disable 4 of my plugins, the problem didnt happen until i enabled this plugin. so i did the obvious, make the plugin creator aware of the situation

[Chris]

May 24, 2013 12:00:21 GMT -8 tunescool said:

i did what they asked me on the support board, disable 4 of my plugins, the problem didnt happen until i enabled this plugin. so i did the obvious, make the plugin creator aware of the situation

I apologize tunescool, I was in a pretty foul mood regarding something totally unrelated when I wrote that. I know that is no excuse but I am sorry.

[Chris]

May 24, 2013 6:58:56 GMT -8 Stinky666 said:

Plugin data has never saved for me on any forum, with any plugin. It's possible it's remembered stuff on the forum itself, but although that is great (you don't wanna be using a like plugin for example, then everyone losing the like count when you upgrade the plugin), it's horrible having to copy and paste over the content from within the actual manager for plugins.

Don't confuse the two, a like plugin would most likely "remember" dynamic data by saving that data to a plugin key. The problem I speak of is regarding settings data (that stuff you enter when configuring the plugin in admin panel) and that is what broke and no longer migrates to newer versions when authors finally got the "Preview & Set Defaults" button.

[kesler17]

Hey I am using this right now, but I don't want the image to show up as a tag, I want it to show up in the thread something like this :ANA: , so that we can put it into censored words to make it an image. We did it with the old proboards, and it worked awesome.
Is there any way to do that?

[Chris]

Jun 5, 2013 5:24:00 GMT -8 kesler17 said:

Hey I am using this right now, but I don't want the image to show up as a tag, I want it to show up in the thread something like this :ANA: , so that we can put it into censored words to make it an image. We did it with the old proboards, and it worked awesome.
Is there any way to do that?

As I said in the other thread (Adding images to the BBcode that don't involve tags) what you're after is a smiley solution not a bbcode solution, in fact the reference code from V4 that you posted is entitled /* extra smileys in posting area by california */.
BBcode are tags so what you're asking is in fact an oxymoron, you need a smiley code if you do not want it inserting tags.

I understand the reason you do not want to use the already existing smiley plugins or to simply add your custom smileys through the improved V5 admin panel where no code/plugin would be needed, you prefer the smileys to be shown like they were in V4 without no effort on your part such as clicking a smiley button to get a list of smileys so here is a code you can drop in your global footer to always have your smiley buttons show. You don't need this plugin or any plugin to use the code and I frankly
haven't tested it for conflicts with any plugins or even tried it
installed on a forum but it should look like the preview image following the code with any
additional smileys you might add in your admin panel



code:

<script type="text/javascript">
$(function(){
	/* Always Show Smiley Menu */
	$('.wysiwyg-smiley-menu').each(function(i,e){
		var $button = $(e).data("menu").options.button,
			$editor = $button.closest('div:not(.group)'),
			$menu
		if($editor.length){
			$menu = $(e).clone(true).addClass("pinned-smiley-menu")
			$menu.data("menu").element = $menu;
			$menu.data("menu").options.onClose = function(){$menu.show();}
			$menu.css({
				position:"static",
				width: "auto",
				display: "block",
				zIndex: "auto",
				border: "0 none",
				boxShadow: "none"
			})
			.removeClass("ui-menu")
			.find('.no-smiles').css("display","none").end()
			.find('li').css("height","auto").end()
			.wrap('<div class="group no-hide ui-helper-clearfix"></div>').parent()
			.appendTo($editor)
			$menu.menu("option","clickHide",false)
			$menu.menu("enableAllOptions");
			$button.hide();
		}
	})
})
</script>

and here is a preview

[kesler17]

Hey thanks exactly what i needed!!! I just need to find out how to make it bigger now though, right now it looks like this:

[Chris]

If your images are larger than the normal smiley image (e.g 22x22) then you'll need to override the height of 22px currently being enforced.

SPOILER: Click to show

Although this works I thought it better to add a specific class of "pinned-smiley-menu" to allow for future CSS targeting and simply remove the 22px height in the jQuery code itself, so just recopy the code in the previous post since the change was made there instead.

To do that add the following below the previous code


<style type="text/css">
   .ui-wysiwyg .controls .group .smiley-menu li {height:auto;}
</style>

Recopy the code to get the changes I just made

It should make it so this



becomes this

[kesler17]

Eton Bones, really appreciate the help, you answered all my questions

[Former Member]

<------ Please be kind, Silver Surfing Grandmother!

Is there anyway the highlight button could be added to reply too please Chris?

[Chris]

Jun 7, 2013 1:57:47 GMT -8 @ritab said:

<------ Please be kind, Silver Surfing Grandmother!

Is there anyway the highlight button could be added to reply too please Chris?

The option is already there but depending on what version of the plugin you're using the process is different.

If your version has a "Hire" tab then the option to apply ALL custom-made buttons to visual or bbcode (or both) wold be found at the bottom of that tab.



If your version has the "Custom Controls" tab then EACH custom button has the option to be included in quick, visual or bbcode (or any combination of the 3) independently.

[Former Member]

<------ Please be kind, Silver Surfing Grandmother!

Ahhh could be I'm using one of the older versions of this plugin then - thanks Chris.

[Chris]

Version 0.8.5 is the latest stable build and version 0.8.8²⁰ is the latest nightly build

Any version prior to the stable build would be susceptible to bugs that were already corrected so it is recommended to update to the latest stable build. One caveat though is when you apply any settings to the bbcode or visual tab the stable build uses a method that may be unfriendly to other plugins that add elements to the editors without first registering those elements in which case the nightly build would be more suitable if such conflicts exist.

[Former Member]

<------ Please be kind, Silver Surfing Grandmother!

Sorry to say I don't understand what 'nightly build' is… and I ask myself if I really should make any changes that could end up being 'unfriendly'?

[Chris]

Jun 9, 2013 22:56:44 GMT -8 @ritab said:

<------ Please be kind, Silver Surfing Grandmother!

Sorry to say I don't understand what 'nightly build' is… and I ask myself if I really should make any changes that could end up being 'unfriendly'? :-/

The nightly build is an incremental version used to test out changes to make sure they are stable before committing them to the stable version, so for example someone reports a problem with the regular version a fix for that problem would end up in the nightly mainly to see if that fix works and also does not inadvertently introduce other problems. This basically serves to keep the "stable" version stable and not introduce unknown bugs. The nightly also is the test bed for future features and an example of that would be the ability to capture a button added there by a totally different plugin and move it around like any other button (buttons added after wysiwyg instantiation would not be manipulable). Once a change or bug fix has been determined to be stable over time and repeated use then it is introduced into the stable version.

When I said "unfriendly" I was referring to the stable version not the nightly since the way it operates is if you apply button changes to the visual or bbcode tab instead of just quick reply it will delete all the buttons then remake them with the changes. This behavior is of course unfriendly because it will also delete buttons or other elements added by other plugins to the controls area. The nightly build no longer does this since it makes the changes backstage before the buttons have a chance to make their grand entrance making it much more friendly to other plugins.