You might sometimes get the following error when clicking on a menu link:
403 – You are not authorised to view this resource. You may not be able to visit this page because of:
1.an out-of-date bookmark/favourite
2.a search engine that has an out-of-date listing for this site
3.a mistyped address
4.you have no access to this page
5.The requested resource was not found.
6.An error has occurred while processing your request.
Please try one of the following pages:
•Home Page
If difficulties persist, please contact the System Administrator of this site.
Go to joomla backend > Sections > Make sure none of the sections’ Access Level‘s are set to registered.
You may not be able to visit this page because of:
- an out-of-date bookmark/favourite
- a search engine that has an out-of-date listing for this site
- a mistyped address
- you have no access to this page
- The requested resource was not found.
- An error has occurred while processing your request.
Please try one of the following pages:
If difficulties persist, please contact the System Administrator of this site.
Hi.
I am using Joomla 1.7.3 with K2 2.5.4 which are the latest versions. I have set access both J! and K2 access levels as appropriate. All articles can be viewed properly, but I find that neither registered user nor author nor even super user can submit an article from the frontend. I created a menu item for frontend article submission using K2 Item edit form menu type
What could be the problem? I am not even sure if it is a J! or K2 problem?
Glad if you could help
Sorry, I don’t work with K2 so I won’t be able to help at this stage.
Anyone else that can help with the Joomla 403 error, please?
I have the exact same issue
I have a menu item called “add a blog” that is set to be viewable only by “special” usertypes… When I click it as a special usertype it launches the add a blog view…. and everything works EXCEPT the add image button in the editor :-/
I am forced to link images from the web!
also, make sure the category itself is public. it didn’t work until I made this change.
since this problem happens whether using JUpdate or a manual method, then this would be a K2 issue. After all, the Joomla source is published and up to date, and it’s K2′s responsibility to maintain compliance.