michelfortin
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: All copy in posts has disappearedOk so you’re telling me my plugin could be the cause. Without more specific information it’ll be difficult to find the culprit however.
What would be useful is the server log which may contain the errors that caused this. Other helpful data would be the actual HTML page given by WordPress when the problem arise, a list of the active WordPress plugins you have, and the PHP version on your server.
Forum: Plugins
In reply to: Markdown <!–more–> renders invalid HTMLAre you using the latest version of the Markdown plugin? I think this has been fixed in PHP Markdown 1.0.1.
Forum: Fixing WordPress
In reply to: Markdown plugin having trouble with PHP 5.1.1Get the latest version of PHP Markdown, this has been taken care of.
Forum: Alpha/Beta/RC
In reply to: Markdown supportSee my notes about Markdown and WordPress 2.0. In short: Markdown works fine, but you must disable the “rich” WYSIWYG HTML editor. Email me if you find any problem.
Forum: Plugins
In reply to: wordwrapping not working?This is a well known difficulty in web design. Browsers will do word wrap but won’t break a word when it is too long. IE expands the box (which in your case push the sidebar below) while Firefox and other browsers following web standards will simply let the text overflow without changing the layout.
The best answer I can give you is that that you should break your “binary text” with spaces.
Read this if you’re interested in the technical details.
Forum: Plugins
In reply to: Disable plugin parser in commentsnitio, if you’re using Markdown, make sure you have the latest version of PHP Markdown. On the PHP Markdown page you can read:
WordPress-Specific Settings
By default, the Markdown plugin applies to both posts and comments on your WordPress weblog. To deactivate one or the other, edit the
$md_wp_postsor$md_wp_commentsvariable under the “WordPress settings� header at the start of the “markdown.php� file.Forum: Plugins
In reply to: How to temporarily disable Markdown?I’ve checked this on the PHP Markdown Dingus:
<script><[CDATA[ test() // ]]></script>And Markdown doesn’t change anything. Are you sure Markdown is the problem? Are you using the latest version (1.0.1b)? It could also be another WordPress filter down in the chain in which case the problem would still be visible when deactivating Markdown.
Forum: Fixing WordPress
In reply to: Replace <p> in text areaSince you are using Markdown, you should use the Markdown syntax for line breaks which says:
> When you do want to insert a
<br />break tag using Markdown,
> you end a line with two or more spaces, then type return.Forum: Plugins
In reply to: Markdown ignores paragraph breaks in commentsI see what it is now. It’s a bug that slipped in version 1.0.1a, because of my lack of testing I guess.
What happens is that WordPress 1.5 now enforce a list of tags that can be inserted by the user in comments and strip those not in this list. This caused problems to Markdown because the automatic link syntax looks like a tag and was stripped prior Markdown filtering. To work around that in 1.0.1a, I’ve postponed the tag filter until after Markdown has done it’s work. But now since
<p>is not an allowed tag for user input, it strips it, along<blockquote>and some other.I’m not sure what to do exactly yet. I guess I could completely disable the tag filter. If you want to do that now, you can remove or comment line 56 in markdown.php:
add_filter('comment_text', 'wp_filter_kses', 45);Forum: Plugins
In reply to: Markdown ignores paragraph breaks in commentsMaybe I should add that to break the text into paragraphs (instead of line breaks), you need to leave an empty line between the two paragraphs.
Forum: Plugins
In reply to: Markdown ignores paragraph breaks in commentsYes, PHP Markdown 1.0.1a is the latest version.
The Markdown syntax on paragraphs and line breaks says:
When you do want to insert a
<br />break tag using Markdown, you end a line with two or more spaces, then type return.Because of this, Markdown works well with “hard-wrapped” text paragraphs.
Forum: Fixing WordPress
In reply to: Pingback confusionI you are still using WordPress 1.2 with Markdown, please make sure you have the latest version of Markdown. The version of PHP Markdown that ships with WP 1.2 becomes very slow when paragraphs are too long. This has been fixed in later releases.
Forum: Fixing WordPress
In reply to: SmartyPants Type PluginYou may also try my own PHP port of SmartyPants. It already works as a WordPress plugin, just like PHP Markdown.
Forum: Plugins
In reply to: Autolink (Markdown) doesn’t work as expectedThis is WordPress trying to correct what looks like a tag *before* Markdown convert the text to HTML. Try deactivating the “WordPress should correct invalidly nested XHTML automaticallyâ€? box from the WordPress admin interface in Tools > Writing
Forum: Fixing WordPress
In reply to: in-post <div> and markdown?Nice workaround. Markdown formatting inside
divand other block-level tags is planned for a future version (probably 1.1). Until then, this is a nice trick indeed.