kegill

Thanks!

THIS IS ONE BUG.

the tweet contained emoji.

????????

When I deleted the emoji from the text of the tweet, all worked.

This has been reported as a bug with various Twitter plugins. I have not seen a report relating emoji characters with breaking the WordPress “save” feature.

One down. One to go. But now I know they weren’t related!

On a whim, I removed the Twitter embed code that was the lede for the WiredPen article.

Save draft now works on that installation. The other one didn’t have Twitter code that might lead to a javascript conflict.

On a whim, I deleted the Twitter embed code that was the lede for the article in WiredPen. Suddenly, “save draft” works.

This is the Twitter code:

<blockquote class="twitter-tweet" lang="en">Someone get me an invite to <a href="https://twitter.com/THISdotcm">@THISdotcm</a> already ????????

— Jessica Reed (@GuardianJessica) <a href="https://twitter.com/GuardianJessica/status/533397678864883712">November 14, 2014</a></blockquote>
<script src="//platform.twitter.com/widgets.js" async="" charset="utf-8"></script>

Argh. ??

Only common denominators (besides me) are WP 4.1 and SiteGround as the host.

I have four WordPress installations on MediaTemple.

I ran the MT SQL script for wp_posts and the MT SSH script (which is missing one of the four URLs, btw).

According to the SSH script, only two sites needed disinfecting — but one of the sites “disinfected” is still viral, according to Sucuri.net, and one of the sites that the SSH script skipped is also still viral. Both “clean” sites are .orgs. Both “dirty” sites are .coms. Probably no coincidence.

I remain POed that the first form letter response that I got from MT (21 hours after filing the ticket, btw) made it sound like I was all alone with this problem.

This is my first “hack” and I am less than thrilled with MTs trying to blame this problem on ME. My passwords are secure. My sites are up-to-date. I have minimal plugins. And I’ve not touched the DB permissions, passwords, etc. or the wp-config.php files (until today). If the DB security is “weak” it’s because MT made it that way with the one-click install.

My adventures: I’ve Been Hacked. I guess this makes me an adult now?

Check your .htaccess file.

See this thread for what the file should contain. It should live at WordPress root unless you have changed the blog homepage to be different from the directory where you installed WordPress … then it should be at your account root.

https://www.ads-software.com/support/topic/257400?replies=3

You need to check your .htaccess file.

See this thread:
https://www.ads-software.com/support/topic/257400?replies=3