jrhall

I am also having the same issue.

iansml and Naz, are you hosting on a Linux server or Windows/IIS?

jh

Found a solution to my issue – may be helpful to others.

The plugin I suggested does actually work.

The problem is actually that another plugin will prevent that plugin, and any other manual code insertions to remove the wpautop filter, from taking effect. It turns out that, for me, the Shortcodes Ultimate plugin was the culprit. Once I disabled that plugin, the Enable Raw HTML plugin fixed the issue.

Hope this helps someone else.

First, I just noticed that the content in my earlier post isn’t quite correct. The issue is that WordPress is changing any instance of ]]> to ]]& g t ; (I’ve inserted the spaces because I don’t know how else to force the HTML reference to display without converting to the >. While that works great for displaying text on a page, it’s definitely not the same thing when the browser goes to interpret HTML code.

I found a solution, though it’s less than desirable.

Unfortunately, the only way I can find to stop WordPress from mangling the Polldaddy ratings code is to alter a WordPress core file. I’ve tried unloading every filter, and the issue still persists. The “solution” is this:

Modify file: /wp-includes/post-template.php

Original:
Line 168: $content = str_replace(']]>', ']]&gt', $content);

Modified:
Line 168: //$content = str_replace(']]>', ']]&gt', $content);

Again, this isn’t really an ideal solution since you have to modify the WordPress core, but it’s the only half-way solution I’ve found so far.

I’ll mark this thread resolved, but it’d be nice if there were a better solution…

Okay. New info for comment woes:

The plugin I posted isn’t completely effective, as it turns out. It will prevent comments from being fouled up in the editor, and those changes from being reflected in the editor, but it won’t fix the page output.

WordPress is still slapping <p> on comments. If I post a single line comment:
<!-- some comment -->
When I view the HTML source, it becomes:
<p><!-- some comment --></p>

It’s not a huge deal, except for when you want to do a multi-line comment.

In that case, your comment:

<!-- Line one
and two
and three -->

Winds up:

<p><!-- Line one </p>
and two
<p>and three & #8211;></p>

Then any subsequent comments you try to make are completely obliterated. You’ll get the initial <!-- but then your closes all become & #8211;></p>, and your whole content area goes to pieces.

No problem.

Are you referring to HTML comment code
<!-- comment -->
Or HTML in post comments?

I found a plugin that seems to do the trick:

Enable RAW HTML – Disable Corruption

The Graphene slider uses the post excerpt text (if you’ve set your “Slider display style” to “Thumbnail and excerpt” or “Background image and excerpt”). Unless you’ve manually set your post excerpt, the automatic excerpt is used (the first 55 words of the post).

This is not the same as the ‘<!–more–>’ tag.

To show the excerpt field, you’ll have to manually change your screen options for the post editor (the dropdown in the upper right-hand corner).

One of the easiest ways I’ve found to edit post excepts in bulk is with the Excerpt Editor plugin. There’s some more helpful excerpt information here: https://op111.net/67/.

We use a rotating slider on our site with current “news flash” stories. I’ve configured it to 200px height. You can also use line breaks to push the “View Full Post” button to be consistently against the bottom. It takes a little guesswork, but if you’re picky about that sort of thing, it’s well worth it.

However, I’m not sure how you managed to get our dashboard widget to show posts in a certain category when you don’t actually have any

I just had a similar issue with the “Drafts” category. It looks like the plugin isn’t filtering a distinction between Pages and Posts, which WordPress stores in the same table (wp_posts).

If a category shows a count and you can’t find a match in either the Pages or Posts listing, install the Adminer plugin, select the wp_posts table, and set the search filter to (e.g. for “draft” category):
post_status Like %% draft

I removed the old page that was “draft” status since I didn’t need it anymore anyway, and the counter issue went away.

Negative – waraha is using the correct endpoint for Google OpenID.

Google has changed their Federated Login settings for OAuth 2.0, possibly earlier than that. I’m new to the game.

The updated Google OpenID information can be found here:
https://code.google.com/apis/accounts/docs/OpenID.html

The new endpoint information is here:
https://code.google.com/apis/accounts/docs/OpenID.html#endpoint