Joshua Fredrickson

Thanks Hardeep. I’m already on a default theme with all plugins deactivated. As mentioned, updating to TinyMCE 4.3.10 fixed the issue.

I was able to confirm that this issue is related to the version of TinyMCE packaged with WordPress 4.5.

I replaced the existing TinyMCE files with TinyMCE 4.3.10 and everything works as expected.

I have the same issue here. Vanilla WordPress 4.5 in Chrome 50.0.2661.75 beta-m (64-bit).

When I attempt to switch to the Text editor, I receive:

tinymce.min.js?ver=4308-20160323:11
Uncaught TypeError: Cannot read property 'ownerDocument' of undefined

Works fine in Firefox.

ina4301, you’re never too old to learn! ??

Glad it worked out for you.

My pleasure, sahelizabeth!

Here’s a quick fix if you’re up for editing the plugin code directly. Note: This change will disappear should you reinstall or update the plugin.

In the /wp-content/plugins/alpine-photo-tile-for-pinterest/gears/ directory, edit alpinebot-display.php.

Find the following section (around line 441):

`/**
* Function for forming Pinterest request
*
* @ Since 1.2.4
*/
function get_pinterest_request(){
$options = $this->get_private(‘options’);

$pinterest_uid = empty($options[‘pinterest_user_id’]) ? ” : $options[‘pinterest_user_id’];
$pinterest_src = empty($options[‘pinterest_source’]) ? ” : $options[‘pinterest_source’];
if( ‘board’ == $pinterest_src ){
$pinterest_board = empty($options[‘pinterest_user_board’]) ? ” : $options[‘pinterest_user_board’];
$request = ‘https://pinterest.com/’.$pinterest_uid.’/’.$pinterest_board.’/rss’;
}else{
$request = ‘https://pinterest.com/’.$pinterest_uid.’/feed.rss’;
}
return $request;
}`

Change this line:

$request = 'https://pinterest.com/'.$pinterest_uid.'/'.$pinterest_board.'/rss';

To this:

$request = 'https://pinterest.com/'.$pinterest_uid.'/'.$pinterest_board.'.rss';

Yep. All it took was a dot in front of the ‘rss’ instead of a slash.

Hi Kate,

This appears to be an issue with the plugin. It was working on a site that I manage, and it stopped a few days ago.

Here are the errors I receive:

<aside id="aptfpinbytap_domain-2" class="pinterest"><div class="pinterest-title"><span style="background-color:#fff; padding-left:5px;">Featured Pinterest Gallery - What is Beauty?</span></div><!-- Using AlpinePT for Pinterest v1.2.6 with Pinterest RSS --><!-- Request made --><!-- Failed using wp_remote_get(), simplexml_load_string() and XML @ https://pinterest.com/colorstylstudio/colorstylestudio-what-is-beauty/rss --><!-- Failed using simplexml_load_file() and XML @ https://pinterest.com/colorstylstudio/colorstylestudio-what-is-beauty/rss --><!-- Failed once using fetch_feed() and RSS @ https://pinterest.com/colorstylstudio/colorstylestudio-what-is-beauty/rss --><!-- WP Error message: A feed could not be found at https://pinterest.com/colorstylstudio/colorstylestudio-what-is-beauty/rss. A feed with an invalid mime type may fall victim to this error, or SimplePie was unable to auto-discover it.. Use force_feed() if you are certain this URL is a real feed. --><!-- Try SimplePie --><!-- Failed twice using fetch_feed() and RSS @ https://pinterest.com/colorstylstudio/colorstylestudio-what-is-beauty/rss --><!-- SimplePie Error message: This XML document is invalid, likely due to invalid characters. XML error: XML_ERR_NAME_REQUIRED at line 28, column 414 --><!-- Sorry:<br>- Please recheck your ID.--></aside>

It appears as though Pinterest no longer uses those RSS URLs. When I attempt to load https://pinterest.com/colorstylstudio/colorstylestudio-what-is-beauty/rss in the browser, I receive a 404.

However, loading https://pinterest.com/colorstylstudio/colorstylestudio-what-is-beauty/rsshttps://pinterest.com/colorstylstudio/colorstylestudio-what-is-beauty.rss does work.

Unfortunately, not much can be done until the plugin authors update the plugin to work with the correct Pinterest RSS URLs.

Unfortunately, this fix no longer works as of a few versions ago. Some of the error-handling code in SI CAPTCHA has been changed since this fix was first posted.

I recommend connecting with the developers of the plugin for an updated fix.

This is true for me as well. When you click on the ‘Check’ link in the Publish metabox, a jQuery error appears:

Uncaught TypeError: jQuery(…).parent.addClass is not a function
/wp-content/plugins/wordpress-seo/js/wp-seo-metabox.min.js?ver=2.2.1

Here’s the error it’s throwing…

Fatal error: require_once(): Failed opening required 'WPSEO_PREMIUM_PATHclasses/google/Google_Client.php' (include_path='.:/usr/local/php53/lib:/usr/lib/php:/usr/local/lib/php') in /home/username/public_html/wp-content/plugins/google-analytics-for-wordpress/admin/api-libs/googleanalytics/class-google-analytics-client.php on line 4

The WPSEO_PREMIUM_PATH constant is not defined in my instance.

Not sure how that one slipped through, but the end result is that version 5.2.5 is, as previously stated, b0rked.

Can confirm. This has been happening for a while on multiple sites (all currently running 3.8.2 or higher). Editor randomly wraps certain text with:

<span style="line-height: 1.5em;"></span>

I haven’t been able to track down when exactly it adds these tags, but I always paste plain text into the Text Editor and then switch to Visual to edit/format. When I switch back to Text to adjust something, I find the new <span> tags added.

Often the sites I work with send out a combination of plaintext and HTML emails, depending on the plugins installed or any added functionality.

When I use wpMandrill’s ‘Content’ option, linebreaks are added to both plaintext and HTML emails. This works great for plaintext emails but not for HTML (it adds an extra <br> after every line break, including closing tags).

Here’s a quick function I added to functions.php that seems to have well so far on a variety of sites. Basically, just add a filter to mandrill_payload that applies wpautop to the content instead of using the ‘Content’ option in wpMandrill.

function op_mandrill_payload($message) {
    // Add wpautop to message content
    $message['template']['content'][0]['content'] = wpautop($message['template']['content'][0]['content']);
    return $message;
}
add_filter('mandrill_payload', 'op_mandrill_payload');

This adds line breaks when needed, but not after closing tags. The result is an nearly all-inclusive solution for both plaintext and HTML emails.

Here’s a quick way to fix the ContentVipersVideoQuicktags fatal error:

Delete the ContentVipersVideoQuicktags.php file from the /wp-content/plugins/autochimp/plugins/ directory.

Viola. No more fatal error.

Same thing:
Fatal error: Class 'ContentVipersVideoQuicktags' not found ...

Running similar specs to jcontini’s.

Had to revert to 2.02.

+1

Reordering categories would be a significant improvement. Odd it’s not already available since reordering topics is already included.