Andrew Mills

(facepalm) Well, that was silly of me. Let me try this again.

that should have read:

“I’m not talking about <br /> line breaks, but the kind of line breaks generated . . . ”

Okay, that’s progress. Glad to hear you’ve got it working, Susan.

Jonnie, how about you? Any luck?

Hi, Susan Warren and JonnieDarko

I’ve read the Jetpack Markdown instructions (https://jetpack.me/support/markdown/) but there isn’t any mention of a Markdown setting under Settings -> Writing, only under Settings -> Discussion (to activate the feature for comments).

Here’s what I did to get it working on my site. Basically, you activate the Markdown feature within Jetpack, go to a page or post, and then start typing in text with your Markdown syntax.

By any chance, are you trying to use Markdown in the Visual Editor?

“For best results, use the Text tab in the Editor. The Visual Editor can produce unexpected results.”

Just going to second what Kimberly said. “/” is unlikely to be the root of your website, and you probably need to fine tune the setting for the “File Check Root” a little bit.

For example, it might be something like:

/home/SkyCaptain/public_html

(Note: This examples pretends/assumes SkyCaptain is your web hosting account name. Substitute that part accordingly.)

I’d be very surprised if the logs folder was inside your public_html folder, so this change should resolve that issue as well. If I’m mistaken, then definitely exclude them because they are going to give you constant alerts.

Please do not modify WordPress core files (e.g. wp-includes/wp-db.php) to fix this issue. The wpdb->prepare command has been improved for security purposes. When you modify or overwrite it, you are decreasing the security on your website and breaking the clean upgrade path to later versions of WordPress. Nobody wants that, right?

Hansaplastique has the correct approach.

If you read Andrew Nacin’s item on this topic, he tells you exactly what to do. I highly encourage you to read it, whether you are a WordPress user experiencing this issue on your own website or a theme/plugin developer trying to fix this issue in your own product. Nacin’s item speaks to both audiences.

On IE 10, the “Console” tab appears after CSS and before Script. Are you using a different version of IE?

Fortunately, IE also has a console. There should be a little “gear/wheel” in the top right corner of your browser window. If you click that wheel, a drop down menu should appear, and you can choose “F12 Developer Tools” from that menu. The bottom portion of your window will reveal a separate pane, and one of the tabs on that pane should be console. After you click on that tab, you can start seeing any error messages as you manipulate the “Add Media” link.

Ok, I don’t think MSE blocks or disables JavaScript.

But the changes you mention in Item 2 might possibly break the “path” to such things as the JavaScript.

By any chance, are you using Google Chrome for your web browser? I ask because if you right click and choose “Inspect Element”, it gives you access to an item called the “Console.” If you try using the “Add Media” link with the Console visible, it may give us a specific error message (like a 404/Not Found, for example) that will help us pinpoint the cause.

Let’s stay focused on the original problem with the “Add Media” link, please.

The “Add Media” link should trigger a JavaScript function that reveal the Insert Media dialog box. It sounds like something is preventing that JavaScript from being executed, based on the description you have provided. This problem is typically caused by a theme or a plugin loading jQuery incorrectly, but we’ve eliminated that possibility by testing with a default theme and also disabling all the plugins. Is there anything else that might be interfering with the JavaScript execution that you can think of?

That’s peculiar. Do you have JavaScript disabled in your web browser, or something that might be preventing JavaScript from running?

If you temporarily revert the theme back to TwentyTwelve does the “Add Media” link work? If so, then the issue is with your theme.

If it still doesn’t work, then the next step is to temporarily disable all plugins and see if the “Add Media” link works. If it does, then you know one (or more) of the plugins must be causing the issue and can identify which one(s) by the process of elimination.

Your site appears to be coming up fine for me, both the front page and the wp-admin log in screen. Did you get it fixed, or is there more to the issue than what I can see?

It sounds to me like you should look into a plugin that handles 301 redirects so the old URLs/links can be forwarded to the new location.

Have you tried disabling all plugins? If so, what was the outcome?

Okay, I misunderstood your original intent . . . so the WordPress API suggestion makes less sense, obviously.

The way I’d go about what you’re trying to do would be something like using phpMyAdmin (or a similar tool) to manually operate on the database. First thing I’d do before changing anything would be a full backup/export of the database, just in case. Hopefully, you won’t need it, but if you do, it’s there.

Then I’d build my SQL queries with a SELECT first, DELETE second approach. Like this:

1. SELECT * WHERE meta_key IN (‘metakey1’, ‘metakey2’, etc.)

2. Count and inspect the records to make sure I’m getting what I wanted to get.

3. DELETE * WHERE meta_key IN (‘metakey1’, ‘metakey2’, etc.)

That way, if your WHERE clause turns out to be faulty somehow, you have a chance to catch it during the inspection phase of step 2 before you delete anything.