Lightquick Web Design - High Quality, Low Cost

If you have found that are getting the Joomla  "You are not authorised to view this resource" message on news or other similar items when your site appears to be working in all other respects then try this sequence of changes - it might just help.

Access levels as they should be - Public

Check whether the access level to see whether the offending items should show for all users or only for users with privilege.

If your item is a news item then  If your item generates the error when using the latest, most popular or similar modules then check to see if the item appears in the normal blog or news pages.

This will give you an idea as to when the problem occurs and should help to point you toward a possible solution.

This error occurred on one of my sites when I installed a latest news module which showed a valid link to the news item. However, when I clicked on the offending news item link I received the dreaded "You are not authorised to view this resource" message. This occured a lot when creating new news items. In this particular case the news items appear in the BLOG but are not reachable via the latest items module.

These are the things that each suffering news item appeared to have in common:

• The names of the news items were long
• The news names often contained a non-text character such as !
• The news items had a name but no alias title

To get round this I have tried a lot of different fixes but in the end I have a solution, of sorts, that works for me:

• If Artio JoomSEF or similar SEF tool is installed and enabled - then clear the SEF cache
• If you have 3rd party cache tools like Pagecache installed then be sure to turn off the default Joomla cacheing, it is not necessary to have both.
• If you have a 3rd party cache tool installed then temporarily disable the cache component.

turn off the default Joomla cache

• 

  Is there an alias for the article?
  Shorten the news item name and remove any non-alpha numeric characters
• Ensure that the offending items have suitable aliases in place, not too long, no non-alpha numeric characters 
• clear the 3rd party caches

These modifications often fix the problem but if the problem still persists I do the following:

A news item can have intro text and main text. I always make sure there is some text in both text areas, this causes a "read more" link to appear on the BLOG page. For some unknown reason this appears to be beneficial to reducing the occurrence of this error. I don't know why.

Finally if it still occurs then you need to copy the content from the offending article and create a new article of the same name, remember to unpublish the old.

MyContent and Artio JoomSEF

There is a minor conflict between MyContent and Artio JoomSEF that can also generate this error.

 MyContent is a tool that allows editing a list of articles via the front end. 

If you have a module, mod_latest_created_updated_date, which shows a list of the most recently Created or Updated content Items then this module should work correctly for any item created using the normal methods displaying each item and linking across as you would expect.

However, when you create a content item using mycontent the link shown by
mod_latest_created_this module will show : "You are not authorised to view this resource You need to login"

All other links working fine, just the new links in this module created using mycontent will be adversely affected.

Reason

When MyContent creates a new content item it uses the incorrect item id. Joomla has a unique item id for all content, modules &c. When Mycontent creates a new content item it picks up the default item id for the mycontent component rather than from the chosen content item category.

Once an item has been created with the wrong item id Artio creates a SEF URL for the newly created item with an incorrect itemid. It will then point a visitor to the wrong part of the database using the wrong id. This is a fault of Mycontent not Artio.

So, in general links to the SEF URL do not work when you are creating items with MyContent.

Solution

A quick work around is to remove the original SEF URLs generated by Artio or modifying them to reflect the correct item id.

 A quick change to the component PHP code forcing it to use the static content itemid is another workaround (which is what I did) but the MyContent component really needs a permanent fix.