irislines web design
irislines web design

Posts Tagged ‘Joomla!’

Modifying Read More links

A question was posted in the Joomla! New England  forum about getting rid of the titles from the read more links generated by the Beez template overrides.  Here is how I responded:


The Beez template was designed for accessibility.

It is an accessibility No-No  to have multiple links on the same page with the same text that point to different urls — so…
the Beez template overrides  pull in the article title, creating unique links to the various articles. Continue Reading

jce configuration use template.css? yes

JCE editor styles – and re-visit editor background color problem…

This topic came up at Joomla! Day New England — how to get template styles to show up in jce styles dropdown and to affect the content in the editor window.

For some time now I have been installing the JCE editor for my clients to use on their Joomla sites.   And each time I have to make a decision about how to configure the editor, because this can be done in different ways and “It Depends…”  is always the right answer.

Here are a few possible issues:

1.  If the site has a colored background or image for the body tag, then the editor will also display that background — and it’s hard to edit black text on a dark background!

2.  Some templates include css something like this:

body { text-align:center ; /* for ie */ } div#wrapper { text-align:left; /* reset text alignment */ width:748px; /* or a percentage, or whatever */ margin:0 auto; /* for the rest */ }

This was for early versions of IE and we no longer need to use text-align:center; in order to center the page in the browser window, but… if you have these styles, then everything is going to appear centered in the editor window if you use template.css styles.

3.  If I want the client to be able to choose and apply special styles to the content, I need to think about what’s enough and what’s too much.

Back in May of 2009 I posted about a solution for the background color issue — it was coming up with WYSIWYG-Pro.

That solution involved modifying the template’s html to include a class on the body tag. And then, in template.css, set

body {background-color:white;} —  this will be in play in the editor window

body.body {background-color:dark;} — this will be what displays as the background when site is viewed in a browser.

This works  if you configure JCE to use the template.css styles.

jce configuration use template.css?  yes

But..   This will also display all classes used in your template.css   including things like .moduletable  and .menu.  On a large site with many custom styles, this could be overwhelming, when all your client needs is the ability to use  a few styles for controlling floated images, or a style for .quote,  .quotee,  or .alert.

jce editor with long styles dropdown


In this case, I would opt to NOT use the template.css file, and to create a special  editor_content.css file, including only the classes and styles that I need the client to have access to.

jce configuration use template.css?  no

jce editor with short styles dropdown.


If I choose to create a separate editor_content.css file, there is no need to add the class to the body tag, as I can create a rule setting a white or light body background (and aligning text) that will apply in the editor window.

Redirects using .htaccess

Set up additional domains as “parked” domains.  Then,  open the .htaccess file for the primary domain and add these lines immediately after the   RewriteEngine On  line.

RewriteCond %{HTTP_HOST} ^(www.)? [NC]
RewriteRule ^(.*)$$1 [R=301,L]

Change the BADDOMAIN AND GOODDOMAIN as appropriate.


Greenhouse Website

At the CMS Expo I shared a site I had developed for the University of Massachusetts:  New England Greenhouse Up-dates  I’ve gotten several emails from Expo attendees asking about the extensions used, so here’s that info.

Note:  I had to edit this blog entry in order to save it —  all references to up-dates would normallly not have the hyphen, but my host has great security and will not allow certain database terms to be used in an article or blog.   I will need to ask them to make an exception for this site and will edit the blog post once that is done.

The site features a blog of “up-dates” about all the things that can go wrong in greenhouses – and best practices to avoid them.  Some articles are just text, while a photo library provides a visual database organized in categories.  When we began the conversion to Joomla! we considered various photo gallery extensions, but ended up using regular Jooma! articles and two separate category blog displays.

For the greenhouse site we were most interested in a single search mechanism that would return “up-dates”  (text articles)  with “photos” (images with captions – sometimes article length) — we also wanted the client to be able to use the same interface for maintaining or adding new content of either type.

The extensions used to make this work were:   imagesized   to create the thumbnails from the normal article images  and

custom properties  for the tagging and search functionality that allowed searching by keyword, type of article and/or topic.

There was a template override with variables so that up-date article “readmores” would say “read more”  but the image library blog readmore links would be just the title.

I wrote that up in this blog post.






Yemuzip for packaging custom templates

Yemuzip was recommended at CMSExpo for zipping Joomla templates, modules, extensions, etc.  because it doesn’t include some Mac junk that the Finder’s Compress command does.  I haven’t had trouble with normal Mac zip files as long as I didn’t have any files with **s or other special characters in the file or folder names.

I downloaded this and tried it.  It’s very easy to use and offers PC or Mac compatibility.

Ignite Gallery 2.5 – category descriptions stripped of all html tags

Fix posted by Matt on ignite’s support forum:

Edit components/com_igallery/views/igcategory/view.html.php change line 189:

$document->setDescription( substr( JFilterOutput::cleanText($category->gallery_description), 0, 200 )  );

so it is now these 2 lines:

$description = $category->gallery_description;
$document->setDescription( substr( JFilterOutput::cleanText($description), 0, 200 )  );

My Blog name and description

You can’t have one without the other —

To have the name and description of the blog appear, you must turn on the toolbar.

(Or write a template override!)

Mighty Resources

At first when I configured Mighty Resources for the Weed Herbarium project we were getting a listing of titles “on this page”  ahead of the ABC links and the table of links to the individual weeds.

The parameter I needed to disable was: Section: Properties: Elements:  Title Index.

Now I’m just going to go into Language file and try to change Title to scientific name.


IrisLines LLC
101 Washington Street
Brattleboro, VT 05301

802 257 7391