Joomla Direct Access to This Location Is Not Allowed Error
After installing Joomla! 1.5, webmasters may encounter the following warning message saying “Direct Access to this location is not allowed” when changing template, installing components (plugins, modules etc) or attempting to enter a component from administrator backend. Sometimes users may successfully change to another default template, but when viewing the CMS website or homepage, the error message appears.
The problem occurred even if you logged in as superadministrator or administrator, because components and modules developed and done for older version of Joomla! 1.0.x are not compatible with the future generation of Joomla, Joomla! 1.5, as the latest version of CMS has undergone major architecture change in coding and design. However, there is still hope as Joomla v1.5 provides a legacy mode that supports backward compatibility for older modules, components, plugins and templates which haven’t been updated for version 1.5.
The Legacy Mode is provided via plug-in, and is disabled by default. To enable and turn of Legacy Mode, follow the guide to enable Joomla! Legacy Mode.
Related Articles
- How to Enable Legacy Mode in Joomla! 1.5
- PHP Allowed Memory Size Exchausted Fatal Error
- Fix Session Save Path Red Unwritable When Installing Joomla!
- Change or Increase vBulletin Maximum Number of Total Allowed Private Messages (PM)
- Internal Error 2739 Error in Vista (32 or 64-bit) When Install Adobe Photoshop CS3 and Reflector Related Programs
- Grant Read Write (Full Control) Permissions on Registry Keys (Fix Cannot Import and Access Denied Error in RegEdit)
- Set Allowed Sites for Google AdSense Publisher Account
- Disable Direct Root Login and User Access via SSH to Server
- WordPress Call To Undefined Function get_currentuserinfo() PHP Error
- PHP Parse Error: syntax error, unexpected $end










































November 28th, 2009 17:58
Hi all, the solutions given here is awesome, It solved my problem completely, it was the version issue in fact. I had the same problem and I logged into the admin panel in the backend went to the plugin manager in the extensions tab and enabled the legacy mode, which was disabled by default, thanks a lot the help
July 14th, 2009 17:45
I faced the similar problem as both the site as well as back end administrative page were showing ‘Direct Access to this location is not allowed’.
I entered the server through ‘ftp’ and deleted the latest entries of plugin and components. and It worked. My system is restored.
April 7th, 2009 09:30
Doesn’t help me out. I’ve this error message in joomla 1.0 when i trying to upload image using tmedit.
January 29th, 2009 14:50
Yo this was mad helpful, thanks
January 27th, 2009 12:14
thankyou, never seen this before after 20 joomla installs, legacy on, no worries..found this in virturmart adding a payment module.
came up first link in google search, saved me hours!
ta!
October 28th, 2008 09:03
Thanks!
July 13th, 2008 18:27
An example of jamrock’s situation in case of jomcomment you can check out How to uninstall Jom Comment Manually if it breaks your site.
May 8th, 2008 05:28
as jamrock stated, turning on legacy mode offers no solution to some of us. the problem, for me, is installing a component with legacy mode enabled and still getting the error. so im at a loss.
for jamrock, i would recommend going into your server via ftp and deleting all instances of the plugin. you might also need to enter the database and doing the same. that gave me access back to my website but i still have no solution to the problem im having.
May 4th, 2008 11:17
I found I had the same problem after installing a component (wysiwyg Pro). Turning on legacy Plugin worked for me too
April 21st, 2008 02:16
I enabled Legacy mode and my two of my websites and still got that error message. I can not log in to change anything front nor backend, so my website is basically lost. There seems to be no solution for this as people keep saying it might be a template, and I only used the default template that comes with joomla 1.5. I wish someone would find a solution for the problem.