inherit
193064
0
Aug 20, 2013 10:28:52 GMT -8
bigd52
31
April 2013
bigd52
|
Post by bigd52 on May 16, 2013 14:26:34 GMT -8
Thanks a lot, Chris. I didn't see the nightly build at the bottom of the first post earlier. I just installed that instead of changing the code in the original one and it works again. I'm not great at coding and wasn't sure what needed to be replaced in the section you posted, but the nightly build has all the buttons showing up like before. Thanks again.
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on May 17, 2013 20:19:56 GMT -8
could you add this at some time if youre not planning on it. it should be the same thru out the forum anyway WTF! I didn't say that ... v0.8.817 Anywho, I updated the nightly to v0.8.8 17 and revisited the lack of a sortable image selector, for reference here is an image of the problem The added images have no double-ended arrow next to their deletion X which would allow them to be dragged and placed in a specific order, the control group itself can be dragged but the button images added within cannot This update adds a few new bells and whistles but one in particular is a field that allows you to force a determinate sequence to the buttons within the control group. The tooltip description for this field basically says In the above image subscript and strikethrough have been omitted so they would appear at the end of the control group after a sequence has been forced on the other buttons
This version also adds optional board and a member group selectors if you wish to make a group of buttons that appear only in certain boards or only to certain member groups. Version 0.8.8 15 had removed a feature where you could assign an empty control group (no buttons) to one of the editors effectively giving no buttons to that editor, this behavior was desirable by some to keep buttons out of the quick reply yet still customize buttons for the full reply page. The latest version brings that behavior back. If a plugin properly registers its buttons with command and control it can add an "img" property containing the URL of their button to the control and have this plugin take care of the rest. This will also allow the user to assign that plugin's button to any control group they've created by also creating a custom button and giving it an attribute of plugin:PLUGIN_NAME and no image then setting the index to the index of the control group or the name of the control group if it was created with a name.
|
|
inherit
Jack of All Trades, Master of None
27090
0
May 30, 2013 20:36:34 GMT -8
Stinky666
8,818
July 2004
stinky666
|
Post by Stinky666 on May 19, 2013 1:37:43 GMT -8
Hi Chris. Not sure if this is intentional but, we are using custom BBCode images, and when you have it set to they show in the quick reply, it displays the PB default images, and not our uploaded/linked to ones. smangii.proboards.com/I have disabled all except the smiley, so you can see.
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on May 19, 2013 6:06:04 GMT -8
Hi Chris. Not sure if this is intentional but, we are using custom BBCode images, and when you have it set to they show in the quick reply, it displays the PB default images, and not our uploaded/linked to ones. smangii.proboards.com/I have disabled all except the smiley, so you can see. Hi Stinky666, it is unclear to me if you're referring to button images (e.g. ) or smiley images (e.g. ) since you mention both. If it is the latter case then there is a workaround regarding the shoutbox listed in the first post of this thread but if it is the former then (although it is never mentioned) the nightly build at the bottom of that first post addresses that issue by saving the buttons (locally) whenever they're displayed on full reply page for use on pages with quick reply where they are not available, previous versions simply used the standard static list. Nightly Update (v0.8.818)This nightly update expands on the control a forum has over buttons created by other plugins (provided they formally register that button with WYSIWYG). In the above image you see the soundcloud plugin button placed into a user created control group along with the highlight pencil. This allows greater control since that button is now subject to restrictions enforced by the control group such as board (appears only in certain boards) or groups (appears only to certain groups) or editors (appears on "quick", "preview" and/or "bbcode"). There was a passing mention of this feature in the previous update This will also allow the user to assign that plugin's button to any control group they've created by also creating a custom button and giving it an attribute of plugin:PLUGIN_NAME and no image then setting the index to the index of the control group or the name of the control group if it was created with a name. So to expand on this feature here is a pic of the third-party soundcloud plugin button on the custom controls tab You'll see it is configured to appear on quick reply and bbcode tab but not visual (just to test) and is also set to live within a control group created on the standard controls tab by the name of vizzi making it also subject to any configuration settings that was applied to vizzi.
|
|
inherit
Jack of All Trades, Master of None
27090
0
May 30, 2013 20:36:34 GMT -8
Stinky666
8,818
July 2004
stinky666
|
Post by Stinky666 on May 19, 2013 12:29:39 GMT -8
Hi Chris. Not sure if this is intentional but, we are using custom BBCode images, and when you have it set to they show in the quick reply, it displays the PB default images, and not our uploaded/linked to ones. smangii.proboards.com/I have disabled all except the smiley, so you can see. Hi Stinky666, it is unclear to me if you're referring to button images (e.g. ) or smiley images (e.g. ) since you mention both. If it is the latter case then there is a workaround regarding the shoutbox listed in the first post of this thread but if it is the former then (although it is never mentioned) the nightly build at the bottom of that first post addresses that issue by saving the buttons (locally) whenever they're displayed on full reply page for use on pages with quick reply where they are not available, previous versions simply used the standard static list. It's the actual button image - For buttons that there are no default images for (blockquote, spoiler, and other customized ones) all work fine, I assume this is because you add the url for it in the actual Plugin manager. So it's all the other ones that the default images show for, instead of the custom ones. For example that's the customized image we have for the "smiley" list: Yet it shows - in the quick reply - the default one:
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on May 19, 2013 17:57:28 GMT -8
It's the actual button image - For buttons that there are no default images for (blockquote, spoiler, and other customized ones) all work fine, I assume this is because you add the url for it in the actual Plugin manager. So it's all the other ones that the default images show for, instead of the custom ones. For example that's the customized image we have for the "smiley" list: Yet it shows - in the quick reply - the default one: ...the nightly build at the bottom of that first post addresses that issue by saving the buttons (locally) whenever they're displayed on full reply page for use on pages with quick reply where they are not available, previous versions simply used the standard static list
|
|
inherit
Jack of All Trades, Master of None
27090
0
May 30, 2013 20:36:34 GMT -8
Stinky666
8,818
July 2004
stinky666
|
Post by Stinky666 on May 19, 2013 19:13:33 GMT -8
It's the actual button image - For buttons that there are no default images for (blockquote, spoiler, and other customized ones) all work fine, I assume this is because you add the url for it in the actual Plugin manager. So it's all the other ones that the default images show for, instead of the custom ones. For example that's the customized image we have for the "smiley" list: Yet it shows - in the quick reply - the default one: ...the nightly build at the bottom of that first post addresses that issue by saving the buttons (locally) whenever they're displayed on full reply page for use on pages with quick reply where they are not available, previous versions simply used the standard static list Didn't see that. Since the download link for the "normal" one is at the top, it makes you just ignore most other stuff Thanks though Edit: Hmm ok so Chris, for some reason, I can see the images (custom ones) in the quick reply, yet for other people they can not, they are still showing the default smangii.proboards.com/thread/38909/discussion-smangiis-theme-guide-v5(only board people can reply to as a guest, so you can see the quick reply).
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on May 19, 2013 20:14:18 GMT -8
...the nightly build at the bottom of that first post addresses that issue by saving the buttons (locally) whenever they're displayed on full reply page for use on pages with quick reply where they are not available, previous versions simply used the standard static list Probably not be obvious from the way I wrote it but it basically says the plugin will save the buttons it sees on the full reply page so when it is on a quick reply page (where that data is not available) it can use the saved data. This means one must first visit a full reply page in order to see any customized button graphics on a quick reply page. Once it is saved that is what it uses for the buttons instead of the default buttons. Once I visited the full reply page I could then return to the quick reply page and see the new buttons.
|
|
inherit
Jack of All Trades, Master of None
27090
0
May 30, 2013 20:36:34 GMT -8
Stinky666
8,818
July 2004
stinky666
|
Post by Stinky666 on May 19, 2013 20:52:45 GMT -8
...the nightly build at the bottom of that first post addresses that issue by saving the buttons (locally) whenever they're displayed on full reply page for use on pages with quick reply where they are not available, previous versions simply used the standard static list Probably not be obvious from the way I wrote it but it basically says the plugin will save the buttons it sees on the full reply page so when it is on a quick reply page (where that data is not available) it can use the saved data. This means one must first visit a full reply page in order to see any customized button graphics on a quick reply page. Once it is saved that is what it uses for the buttons instead of the default buttons. Once I visited the full reply page I could then return to the quick reply page and see the new buttons. Ohhhhh right ok. Excellent. Will let people know. Much appreciated
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on May 19, 2013 21:24:26 GMT -8
You're welcome! BTW it is a "nightly" meaning not for the faint of heart so the placement is to avoid accidental downloads. Those who are adventurous enough and want to see what is beyond the plain-vanilla stable version occasionally test the newest features using that link while those looking for simplicity won't go past the first link as you say, not even to RTFM.
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on May 22, 2013 1:20:59 GMT -8
If you are using the as yet unpatched vSoundCloud plugin then you'll need to manually patch it to make it work with some changes made to Proboards after that plugin was created.
Update: version 0.8.820 (nightly)
This update makes a critical behavioral change in order to make custom and third party plugin buttons adhere to user-defined restrictions (board and group) which were added to the previous revision. custom buttons can now independently be chosen to go to "quick", "preview" or "bbcode" (or any combination) while at the same time it can be forced into a group using the group's name as the index (this feature reported buggy right now). Groups can also be independently associated with the various editors, this means for example if you have a group set for "visual" only but tied to a custom button set for all three then on "visual" the custom button will be located inside the group and then by itself on the other two editors. This behavior is still inline with previous versions since custom buttons were loners unless you assigned it to a group using its index field the bolded words are no longer true, if a button is assigned to a group and that group is not present on the editor then that button will not appear. In other words if a custom button has "bbcode", "visual" and "quick" checked but it is assigned (by name) to a control group that has only "bbcode" and "quick" checked then that button will not appear on the "visual" tab because control group takes precedence in this relationship. This change is to tighten the bindings between buttons (custom controls tab) and control groups (standard controls tab) since they can now be reserved exclusively for certain groups or certain boards. this change also allows custom buttons and third party plugin buttons to be subject to the forced sequence field in a control group (previously only standard buttons were affected) note: as of this writing the only plugins that correctly registers its buttons with WYSIWYG is vSoundcloud and vSpoiler so are currently the only plugins whose buttons you can reconfigure using the tools provided. An interface will be eventually added to make it easier for other plugins to register their buttons either through Yootils or a direct interface provided by this plugin.
|
|
inherit
tunesrcoolii@gmail.com
86185
0
Oct 3, 2013 8:48:20 GMT -8
tunescool
4,399
August 2006
tunescool
|
Post by tunescool on May 22, 2013 5:54:17 GMT -8
eton ive been having a problem modifying my threads for like a month or so. after i hit save it just goes to the Modify Post page again and i get a message saying, You Have To Provide A Message. i have a thread on support where they were helping me and eventually they asked me to disable any plugins thay would affect that page. i went in to the Modify Post page at least 30 times and typed more into the post and resaved it everytime. it wouldnt do it but as soon as i added this plugin i got the message again heres the thread support.proboards.com/threads/recent/462142it doesnt just happen in the thread i mentioned in the first post thread on pbs it happens in any thread
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on May 22, 2013 6:24:43 GMT -8
Since I or anybody else using the plugin has encountered that problem then it would appear to be a case of "ice cream being the cause of polio" so I'd suggest disabling the plugin until further credible information emerges. Edit:
And the following thread which sports 3 plugins none of which is this plugin is complaining of the same problem and they are not blaming the ice cream for causing the polio Some of my members on my forum evthreads.proboards.com is having issues posting. This is what one of my members wrote on our support sub-board, giving her perspective on it. I like to add that I have been having lag issues at times and just recently I was trying to edit a post and I wanted to switch to BBCode mode but it seemed to just flat out hang. I think it's mostly due to some kind of slow-down with the servers or something. So is there any issues on my forum or is this something on ProBoards' end? EDIT: Oh btw I understand that it may not be biz hours right now. I'm content with waiting. i cant explain it anyway else, ive said it twice and posted pics showing exactly what is wrong, maybe someone else can help Peple around here generally help with a problem when asked nicely but pulling accusations out of one's butt and throwing them against the wall to see what sticks is just stupid and unsanitary...
|
|
inherit
Jack of All Trades, Master of None
27090
0
May 30, 2013 20:36:34 GMT -8
Stinky666
8,818
July 2004
stinky666
|
Post by Stinky666 on May 24, 2013 2:08:32 GMT -8
|
|
inherit
Official Code Helper
65613
0
1
Oct 22, 2024 1:56:19 GMT -8
Chris
"'Oops' is the sound we make when we improve"
9,018
December 2005
horace
RedBassett's Mini-Profile
|
Post by Chris on May 24, 2013 4:23:13 GMT -8
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... -- (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...
|
|