This plugin looks great and I would love to use it, however, I am having trouble getting it to show up.
I’ve tried it on 1.6.1 and 1.6.2 and in both cases it does not show up, no matter if I use normal field names ({body}, {summary} etc) or custom ones and unlike another poster here, it does not even show up for published articles.
I triple-checked the paths to the various folders and they all return the expected files. I also did a check of the source of the publish / edit section and it does not contain ANY links to the javascripts used by the editor, even though the extension is enabled.
I’d highly recommend adding “check path settings” as one of the instruction items in the readme file! I spend a while trying to figure out why things weren’t working, then I read on down this page and saw some other folks with the same issue.
Just a quick note to say thanks to lavalamp for his work on this extension. After much procrastinating, I sat down to write something similar, and began by searching the forums for advice and ideas.
Having done similar searches on several occasions previously, I was very surprised to uncover this gem. The ways things are going it may soon find a home in my list of “must install” extensions for every project. Congratulations on a job very well done.
Thanks for the extension!
Textile works for entries so far ... though no Buttons for formatting text with textile show up.
What am i doing wrong? Do i have to switch on a textile formatting button bar somewhere?
Thanx for help in advance…
Here’s a weird bug: If I go to edit an entry through the Edit tab, everything works fine. If I try to edit a page (created through EE’s Pages module) and go to the edit screen via the Pages module, TEH doesn’t load in the text areas.
This Extension hoses Brandon Kelly’s “Playa” (and possibly other extensions that are putting JS in the header). I’ve been trying to fix this all night. Wondering if there is some sort of conflict in the JS in the header and the Playa JS?
It’s unfortunate that this one uses Proyotype. Anyone think they can convert this to a jQuery version?
EDIT: Better yet, has anyone seen markitup? Wonder how difficult that would be to implement as a custom field?
Not entirely certain what the problem is there but you may try adding in the no conflict script for jQuery and see if that works. I recently had problems with getting a script to work as I had both jQuery and Prototype enabled on a page and so added :
<sc*ipt type="text/javas*ipt"> var $j = jQuery.noConflict(); </sc*ipt>
to the page and it all worked out fine. Perhaps check out this page here and see if that helps at all. Not sure if that is what you are experiencing or not but I don’t suppose it would hurt to try. Admittedly any jQuery calls will in any of the jQuery scripts for that page / template that you are using them on will need to have the $j in them instead of just $ but you never know?
I don’t think jQuery is involved here…um, amywhere. Have you read this thread or are you just boosting your post count again, you naughty monkey!?
How dare you suggest such a thing. If I was just boosting post count then I wouldn’t have posted some technical jargon and gone looking over the net for it!
I feel deeply hurt by that Going to sulk in the corner for a bit now!!
Actually I got confused as I thought that Playa used jQuery from reading what you had put above. You asked if anyone could convert something to jQuery and not have it as Prototype and as I had this same problem myself (jQuery & Prototype working together and causing problems) just thought I would post what might be a fix.
Now I’m going to go off and sulk!!
Posts + 2 now though instead of 1 because of what you said
For the record, I just whipped together an Extension for a Markitup custom field...and Playa and Markitup both play very nice together. Seems that Markitup is playing nice with everything so far, actually.
It isn’t ready for prime time, but it’s working quite well. If anyone is interested, and I can polish it a bit, I may release it.
For the record, I just whipped together an Extension for a Markitup custom field...and Playa and Markitup both play very nice together. Seems that Markitup is playing nice with everything so far, actually.
It isn’t ready for prime time, but it’s working quite well. If anyone is interested, and I can polish it a bit, I may release it.
Yep! Interested. Polish it. Release it and I’ll take it!! Markitup does look very nice.
Will make up for what you said about me earlier !!
I might try to release a super simple version, just so it’s out there. It would be nice to incorporate per-field settings (like, default for one field, textile for another, etc). Attached is a screenshot of the field in action.
I might try to release a super simple version, just so it’s out there. It would be nice to incorporate per-field settings (like, default for one field, textile for another, etc). Attached is a screenshot of the field in action.
This might make for a nice alternative to TEH.
Now that’s just naughty posting an image preview but no extension download!!
I think from what I have seen from Markitup it seems as though you can make it spit out the code you want as opposed to the bloat that other Text Editors seem to do which in my mind makes it the best yet for this kind of thing.
Looking forward to perhaps a look at the extension!
Going to sulk in the corner for a bit now!! 