[Plugin: SEO Ultimate] the new version remove all underscore characters in post and page

Hi leepton,

Thanks for the report. I’ll release 1.5.1 to fix the problem.

– John

Version 1.5.1 is released, which fixes the bug. Your posts were not edited; all your data is preserved. Upgrading to the latest version of SEO Ultimate will restore the underscore characters.

The problem was caused by the Markdown library, which is included in version 1.5 and newer; the Markdown library detected that WordPress was installed and tried to “helpfully” apply Markdown formatting to posts, which replaced the underlines with <em></em> tags with on-the-fly formatting (i.e. no database changes made).

Thanks for the bug report.

HI John,

Thank you for the swift update, now SEO ULtimate works perfectly but, ater the installation i’ve got this conflict message.

Google Doc Embedder Warning: You have an active plugin that may conflict with GDE. See more info or turn off this warning.

but each plugins as “Google Doc Embedder” and “SEO Ultiamete” are running pefecly.

i think that is a minor compatibility

regards

for more infos , this issue is already known by GDE

Known Conflicts

The following plug-ins have known compatibility issues with Google Doc Embedder. (If you can deal with these issues and wish to turn off the conflict warning, go to GDE Settings and click the plus sign next to “Advanced Options”, then check the box to “Turn off plugin conflict warnings”.)

Markdown

With the Markdown plug-in installed and activated, GDE will not work properly on any file with an underscore character ( _ ) in the URL. To bypass this error, either deactivate Markdown or escape the underscore characters. For example, “the_file.pdf”:

[ gview file=”https://path.to/the\_file.pdf” ]

It looks like this warning is caused by a bug in GDE. It sounds like GDE is checking for the existence of the “Markdown” class, when it should be checking to see if the constant MARKDOWN_WP_POSTS is true. (If you pass that info along to the GDE developers, they may be able to fix it on their end. Or you could just ignore/disable the GDE plugin’s warning.)