It's been difficult to find an easy solution to hide menu items from registered users. Finally, I found a solution that works 100% for me using the MetaMod tool without using any template hacks. The instructions on the metamod page are very vague so I wanted to make it bit more in-depth for this specific use. I'd love to hear if this helps you. Let me know if you find any mistakes and I'll be sure to fix asap.


Thought I'd add the migration script I've been using to test my JComments migration from my Joomla CMS site version 1.5.20 to Joomla CMS site version 2.5.6.


  1. I do not work for either Joomla or JoomlaTune (Jcomments)
  2. This script is provided as is without warranty
  3. If you do not understand what this script is doing, let someone who does run it instead


  1. Install JComments on your upgraded website (at time of print: Jcomments v2.3.0 on Joomla v2.5.4)
  2. Copy the below script to a text file
    1. Change the database names to match your setup
    2. Change the table name prefixes to match your setup
  3. Run the modified SQL script against your database.
Note: It is not advisable to run this on a production website!

Applies to:

This article is a follow on from my article JComments 2.3 with PlayThru (Joomla 2.5.x) but this is for a later version of the components using the alternative called PlayThru by AreYouAHuman.Com.

The kCaptcha used by the jComments extension is easily automated and no longer blocks spam comments. Google's ReCaptcha is overrun by click farms and is unable to authenticate engaging visitors.

So I have come up with what I consider a pretty stable solution. I adapted it from various legacy solutions when using Google's ReCaptcha.

So this is an article to note an oddity when I was working with a Yootheme template called "yoo_sync". Some clever scripts (both mootools and jquery) using the equalize method to make div layers the same height, and in this case, the same width. It isn't so much a miscalculation of 100% divided by 3 that leaves 1 pixel left over, more the fact that the scripts use that 1 pixel (ceiling rather than floor?).

We have a row on a website of three boxes made of div layers. When viewed normally on a 15" Laptop, all was good using Chrome and tolerable using MS Internet Explorer. If we maximized the Google Chrome browser, the row would split and there would be 2 boxes on the top row and the third would pop under these. As for MSIE, that was ok when maximized.

You could do loads of code hacks which is what I tested but all for nothing because you always end up needing to specify a third of the width.