Textile Editor Helper (TEH) extension

Hi and thanks for the swift reply. Yes. The web link issue does appear to be an IE issue. It goes crazy in IE7 as I described, and I have just tested in IE6 and the web link buttons just do not work at all. Personally, I can live with it, as I use Firefox and Safari (anything but IE!) - but the client uses IE7, although it loks like I will have to insist on them using Firefox.

The display issue I mentioned happens in ALL browsers though, so I am hoping to get some assistance with that problem, if possible 😊

EDIT - Sorry I completely missed your post earlier in this thread about the IE7 issues. I thought I’d read every post! At least its not just me then! It will have to be Firefox for now I suppose.

Yeah, you’re in the same boat as I am. I’m fine with it because I use Firefox, but our users at work use IE, so they run into some problems with it, but it’s not be too bad thus far.

Hi Deron, could I just ask if you have noticed the display glitch that I mentioned above, whereby the TEH toolbar buttons block out items in the Publish and Edit list? Just wanted to know if you experienced this at all.

The display problem is causing great frustration to the content editors, so I am extremely keen to see if this can be fixed, or just to hear back from anyone else who may have experienced the problem.

I included a screenshot earlier for reference.

I’ve never experienced it, but on all of my sites we have the TEH set on a field that is usually at the bottom of the publish form. I did go and test it out real quick in Firefox by changing the formatting on a field at the top to Textile and yes, it’s happening on my end as well.

Thanks Deron, thats good to know.

So the workaround is to not have fields using Textile at the top…. not ideal thats for sure… but I will see if I can juggle things around unless I hear of a fix.

Any thoughts on this from the developer of the EE extension? 😊

One thing that I do on one of my sites is use the tab forward extension. On the publish page where you’ve got the “publish form,” “date,” “categories,” etc., tabs at the top, the tab forward extension will allow you to show any tab you one first rather than always defaulting to the “publish form” tab. We use the tab forward extension to show the “show all” tab by default so as soon as the publish page is brought up it shows the entry/expiration date area, categories, options, etc, all at once and thus pushing all custom fields down further in the page. This may work for you depending on how many tabs you have available as options. Hope that makes sense. 😉

Hi Deron and thanks,

It does indeed make sense, although I think the client is pretty happy switching between the different tabs, rather than having them all show up in one long list. I will have a good think about it though, thanks for the excellent tip.

Hi Deron and thanks, It does indeed make sense, although I think the client is pretty happy switching between the different tabs, rather than having them all show up in one long list. I will have a good think about it though, thanks for the excellent tip.

Sounds good. Yeah, for us, showing all by default was great so that the users who update the site didn’t miss anything like an entry date or expiration date because they forgot to switch tabs. 😉

Thats a very good point. I might look into that. If not for this project, then the next….

Think I will have to take a look at Markdown though, if I can’t solve this current display issue.

Have you tried Markdown before? I have it a go before I started using Textile and I just found Textile to be a little easier for some reason. There’s a lot of people that love Markdown though. I guess it’s just what you get accustomed too.

My clients are not experienced in either Textile or Markdown, in fact I think they were probably expecting a WYSIWYG, so I had a choice as to what I could implement. I needed something with a toolbar like TEH uses, and I tried unsuccessfully to get Ryan Masuga’s MarkItUp extension to play ball for me, so the options became limited. I am hoping Ryan’s new version of MarkItUp (1.5) will work better for me, alas I think it may come too late for this project.

@angstmann - I have seen the problem of with a really long publish menu being obstructed by the TEH toolbar - and also Mark Huot’s file extension as well. It’s an easy fix, but it does require a small addition to the control panel theme’s css file, as it appears to be a positioning problem.

In your themes/cp_themes/default/default.css file around line 664 add a z-index declaration:

#publishdropmenu { 
    position: absolute; 
    visibility: hidden; 
    background-color: #E1E8E9; 
    margin: 0; 
    border-bottom: 1px solid #ccc; 
    border-left: 1px solid #ccc; 
    border-right: 1px solid #ccc;
    z-index: 100; /* make sure menu is always on top */
}

Of course, this assumes you’re using the default cp theme, so if you’re using the “classic” theme or a custom cp theme you’ll have pick the correct file of course. And it doesn’t have to be 100 - I just picked a high value

-mike

That is absolutely FANTASTIC! Thanks imagehat - tried it and it works a treat. I had a feeling it would be z:index related as I know that controls stacking order of things, but had no idea where or how to implement it!

Thanks ever so much - that will really make my client happy! 😊

Just found this. Wow! This is great.