WayneM1

Okay. Thanks for your response ??

I can confirm hexanal’s observations. The dotted lines are missing. And the hover, click, drag & drop, actions are all very sensitive and unpredictable. Tested in both FF 42 and Chrome 47.

Just did a bit more experimenting. I’m finding that even when the drag & drop reordering appears to place a page in the right spot, after the dashboard is refreshed, the page (or pages branch) is not where I dragged them. Oooops. That’s a problem.

This is a great plugin for displaying and reordering page hierarchy. But right now I find it too touchy and unpredictable to use. ??

Great! Thanks again.

Works great!

Again, thanks very much.

Hi Aleksandar –

Thanks very much for your quick and positive response.

Looking forward to the new option ??

@ kiwi3685
No help at that link…

Okay. Got it.

Thanks as always ??

Can also confirm that the fixed version in the .zip file above works for me, too. Thanks.

Asked about this over a year ago and received no response. Would really like to at least have this request acknowledged in some meaningful way.

If there is no intention to implement this as an option, then perhaps a suggestion on something I can add to my functions.php that might work to disable the “denied” emails?

Thanks again for your great plugin.

As an admin I like to have available all the features the standard WP editor offers. Also, I like to have available the buttons that some other plugins make available in the editor.

I understand your position to keep the your plugin option-less and simple.

For those who might like to have the full featured editor only available for admins, and have all others use the CPVE, I offer this modified version of your file (tested and works with WP 4.1):

<?php
/*
Plugin Name: Client-proof Visual Editor
Plugin URI: https://github.com/hugobaeta/client-proof-visual-editor
Version: 1.4
Author: Hugo Baeta
Author URI: https://hugobaeta.com
Description: (MODIFIED: Exception for Admins) Simple, option-less, plugin to make TinyMCE - the WordPress Visual Editor - easier for clients and n00bs.
*/
if ( is_admin() ) {
	require_once(ABSPATH . 'wp-includes/pluggable.php');  /* need this line to get current_user_can */

function clientproof_visual_editor( $mceInit ) {
	// What goes into the 'formatselect' list
	$mceInit['block_formats'] = 'Header 2=h2;Header 3=h3;Header 4=h4;Paragraph=p;Code=code';

	// What goes into the toolbars. Add 'wp_adv' to get the Toolbar toggle button back
	$mceInit['toolbar1'] = 'bold,italic,strikethrough,formatselect,bullist,numlist,blockquote,link,unlink,hr,wp_more,fullscreen';
	$mceInit['toolbar2'] = '';
	$mceInit['toolbar3'] = '';
	$mceInit['toolbar4'] = '';

	// Clear most formatting when pasting text directly in the editor
	$mceInit['paste_as_text'] = 'true';

	return $mceInit;
}

	if ( !current_user_can( 'manage_options' ) ) {  /* check if user is not admin then allow CPVE */
    	add_filter('tiny_mce_before_init', 'clientproof_visual_editor');
	}
}

?>

Awesome! Thanks ??

Doing a bit more digging…

Found that I CAN post URLs – but ONLY if the URL is not the first character of text in the post form.

In other words, if I add a blank line (return), or even just a blank space before the URL, or if the URL comes later on in the context of a post – then it works fine.

All the posts that returned 403 errors happened when a URL was right at the start of the post.

I’ll pass this along to the authors at Simple:Press and see if they have any ideas.

Again, thanks for your great plugin ??

Deactivating the FVE plugin had no effect. I think most signs seem to point to an ajax issue with the Simple:Press plugin. I’ll pursue that avenue to see what I can dig up. Thanks again.

That is weird. Thanks for the heads-up. I’ll see what’s happing in my root.

I have another website running the exact same setup (BPS and Simple:Press) on a server with the same setup. That website has the WP installation in the root directory (not a sub like /3/), and I’m having the same problem with trying to post links in forum posts.

I deleted the wp-admin .htaccess. No change.

I’ll keep digging.

Followed your steps above.

When testing posting with a link, the result was a standard WP 403 page (not a BPS 403).

Testing post without link worked fine.

Looks like maybe I’ll need to track this down through the forum plugin authors.