qco

So, I’ve tried three methods for enabling tinyMCE for certain requirements we have on our forum and ease of use

1) enabling tinyMCE using built-in BBPress filters:

function bbp_enable_visual_editor( $args = array() ) {
	$args['tinymce'] = true;
	$args['quicktags'] = false;
	return $args;
}
add_filter( 'bbp_after_get_the_content_parse_args', 'bbp_enable_visual_editor' );

2) Using bbp style pack plugin
3) using Image Upload for BBPress plugin

In all cases, while the tinyMCE editor is active on the reply box, the @mention feature of this plugin does not work.

Here is a screenshot: https://www.dropbox.com/s/qm3aglade5p85ry/comment-mention-mce.jpg?dl=0

• This reply was modified 4 years, 1 month ago by qco.

After some more digging, it appears that this was actually a failure that was a result of a disallowed character in the featured image that was uploaded (?). After fixing that, it appears to publish correctly.

Hi damen02,

The template scripts are loaded in the wp_footer and admin_footer (if you want to override the admin template as well) actions, loaded through the wp_playlist_scripts action. You can actually override those templates directly:

remove_action( 'wp_footer', 'wp_underscore_playlist_templates', 0 );
add_action( 'wp_footer', 'my_underscore_playlist_templates', 0 );

If it were me, for the sake of removing code repetition, I would probably just add an attribute to the playlist shortcode to define a template, and then override those wp_footer actions based on that attribute ([playlist template="my_template"]), instead of having separate playlist and my_playlist shortcodes.

FWIW, I was finally able to override these templates for my own needs. My issues were mostly related to just dealing with how the Backbone integration works with everything. I was unfamiliar with Backbone, and after learning more about it, I was able to work through my own specific needs.

I apologize, I was looking at the wrong plugin (very similar names) when submitting this thread.

I’m with phloo on this one, with regards to managing client sites. Even if there is a security issue with “hiding” the account selection box after authentication, in this case, security through obscurity is better than nothing.

One suggestion, as a couple of other GA plugins do, would be to add an option to disable that settings screen (or all settings) for all but a single administrator account. This way I would be the only one able to access those settings and the client could not change properties. I’m not worried about malicious actions so much as I am about misconfiguration or mistakes made by other admins who accidentally change a setting.

I understand your stance, but I think it would be nice to at least have the option.