next »

[garryn]

Hi,

Looking at the phpMarkdown instructions, I think the following plugin should work - set it to run on the 'OnWebPagePrerender' event:

Code:

// phpMarkdown integration

$e = &$modx->Event;

switch ($e->name) {
case "OnWebPagePrerender":
include_once("markdown.php"); //change path to where the markdown script is located
$pg=&$modx->documentOutput;
$modx->documentOutput = Markdown($pg);
break;
default:
return;
break;
}

I've not tried this yet but, in theory, should work. 

Cheers, Garry

[davidm]

If it's as simple as that, then it's truly a testimony of MODx power

Berlueur, could you try that and report ?
Thanks !

[Berlueur]

Yeah, I have made my "own" Markdown plugin after posting my message and before reading the responses here... (by totally ripping off Raymond Irving's plugin).

I'm actually a bit excited to have "made" my first MODx plugin... so much so that I made a little package.

(BTW, MODx thoroughly rocks...)

The plugin lives here.

[Djamoer]

Yeah, I have made my "own" Markdown plugin after posting my message and before reading the responses here... (by totally ripping off Raymond Irving's plugin).

I'm actually a bit excited to have "made" my first MODx plugin... so much so that I made a little package.

Here goes.

(BTW, MODx thoroughly rocks...)

Did you post it somewhere on the forum? Please make a new topic with [Plugin] as the prefix of the title, and name the plugin, so we can add it to the repository Good job with your first try...

Have fun with MODx!

[Berlueur]

Yes, it is attached to my post, just above...

I will make a new topic, although it feels a bit strange since I did almost nothing...

I download the package and follow the readme but when I edit to document the FCKeditor kick in and I don't see any markdown stuff even I set FCKEditor to no in the system config.

What am I missing?

Thanks

[davidm]

Maybe the little instructions I wrote for the Textile plugin will help, since the principle is similar.

Just modify <textile> and </textile> by <markdown> and </markdown> (that is, if berlueur followed the same logic , didn't test this one yet).

Hope this helps !

[Berlueur]

Yes, Markdown directives need to be enclosed in <markdown> </markdown tags.

[davidm]

Yeah well let's also mention there is a ReadMe in the distributed plugin

Berlueur, so that everyone downloads the right version, I suggest you take your download off this thread and keep only one on your the official plugin post

This will avoid confusion and mistakes

Anyway, great work this is very nice having Mardown working

I put <markdown>[*content*]</markdown> in the template and it works but I did the same thing for <textile></textile> but for some reason it does not work the tag that tried.

[davidm]

Chanh, didn't test Markdown but Textile works for me when I put <textile>[*content*]</textile>, I just checked again.

Are you sure you ticked OnWebPagePrerender in Resources > Manage Resources > Plugin >> Textile >>> System Events ?

If that's not it, then I don't get it...

I copy the entire TexTile test text into my content to test out the snippet and yes I did set the system event and I did change the template but it does not seems to do anything.  May be the Textile.php is not compatible with the test text that I copy from the site.

I work fine with Markdown test markup those.

One little caveat is the first line have to be blank for this to work otherwise the first line does nothing.

[davidm]

Well, I tested a few elements of Textile syntax, not the sample file...

I'll try that, you're probably right something is bugging the plugin probably. Which sample file did you try ? There are Textile (like the one use in txp) and Brad Choat's Textile2.0 which has been ported from MT to many CMSes , the later having more capability.

Here is the sample that I use for my test.

http://www.textism.com/tools/textile/?sample=2

[davidm]

Ok I just tried the textism sample.

For me :

• lists (unordered and ordered) work
• title work
• links work
• emphasis works
• blockquote works
• all "second level" things like p.{color:red} or bq.[fr] or #{color:blue}doesn't work
  
• muli-level list do not work (or rather the second level of depth)
• mixed list do not work (idem)

Not in the sample file I also tried :

• quote works
• deleted text works
• superscript works
• subscript works
• accronyms work
• span doesn't work
• align doesn't work.

I'd have to check that with Jeff... or have a look myself to the plugin.