Textile Editor Helper (TEH) extension

just installed the latest version and enabled the extension - installed the textile plugin as well - adding a new post, I don’t get any toolbar at all - no error messages either - am I missing something here?

thank you in advance for your help.

mmjaeger - is the folder named “teh” uploaded your site root? That’s the default location the extension expects, but you can go into the extension’s settings and change the paths if you want it somewhere else.

this is my setting for instance: http://localhost/sites/dev_mmjaeger/teh/javascripts/prototype.js - it’s just not working

Hi, thanks for the update. I just updated this Ext on a site that previously had 1.0.2 running. Going in to edit an entry results in:

Notice: Undefined index: help_url in /home/.../.../.../extensions/ext.textile_editor.php on line 132

Lines 130-134:

// Help link
  function teh_help() {
    window.open("'.trim($this->settings['help_url']).'", "_blank");
    return false;
  }

Looking under settings, then to see if the help url is there. Line 220:

$settings['help_url'] = 'http://hobix.com/textile/';

These lines appear correct to me. I tried uninstalling and reinstalling the extension, but I’m still getting the error. Thanks for taking a look!

UPDATE: There is a phenomenon on the forums known as the Fonzie effect. All you have to do is come here, write a post about what your problem is, and then go back to find it fixed. All I apparently did was go back to the site, and made sure to click “Submit” on the settings page, and now it appears to be working correctly. Whatever. I’ll take it! Thanks for this very useful extension.

Hi lavalamp,

Thank you for this beautiful adaptation of the Textile Helper Plugin for EE. I think its great that you even improved it.

I am wrestling to get your latest version working on my frontend (via SAEF). It works great in all browsers, except in Internet Explorer 6 and 7. I am sure it’s a javascript problem, but I can’t seem to find the problem.

It has something to do with this piece of javascript you wrote which is inserted in the publish/edit pages of EE. What’s making it break in IE and not in all other browsers?

Could you please tell us how to enable the plugin for SAEF?

PS: The orginal TEH works on my SAEF, but due to the space/lists problem, I can’t use it reliably for my members.

I really like this extension and I was about to start building some custom buttons. Frustrating that it’s not in the add-on library, I would have found it much much quicker.

If it could just have a dash of WYSIWYG… Sorry, but that’s what the punters want!

Frustrating that it’s not in the add-on library, I would have found it much much quicker.

I think you’d be utterly shocked at how many things aren’t in the add-on library. That is actually one of the last places I look for add-ons.

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.

any thoughts?

Try going to the custom fields section:

CP Home › Admin › Weblog Administration › Field Groups › Custom Fields

Check under Edit List under the “Default Text Formatting for This Field” bit, and you should find a Textile option…

I attached a screenshot of the area I suppose you were talking about.

FWIW, I am using Publish Page Improvements (v.2.0.0) , but even with them disabled, I do not get the TEH.

any more thoughts?

Not under “Edit List”?

ah! Found it, apologies for the confusion. It is still early around here.

[edit] working as expected! I might even have a shot at extending this.

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.

This is a super useful extension, thanks so much!

-dave

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.

Cheers, Stephen