Hi, I just installed Purity III on my site and I can’t get the xLayouts working. The website returns a “403 forbidden” error everytime I try ton configure one.
See, when using the default Joomla “Category: Blog” option, it displays correctly;
When using one of the xLayout options:
Here’s the test menu configuration screen:
This is on a fresh Joomla install, barely anything else installed. Any ideas?
Joomla 3.4.3
T3 Framework 1.5
Purity III 1.1.5
jooservices
Friend
Hi there
403 Forbidden would came from server side. Please check it with your sysadmin
https://en.wikipedia.org/wiki/HTTP_403
Thank you,
Viet Vu
I’ve checked the T3 Framework and Purity III files and they all have “666” permissions, instead of the usual “644”. Could this be the problem?
All folders are 755.
Edit: Well, I fixed the permissions and it still doesn’t work… Don’t know what else to check out.
jooservices
Friend
Hi there
Please provide your site backend & CPanel access. I’ll help you check it
Thank you,
Viet Vu
Hi again, I just sent you the backend access.
I created a “Layout test” menu item so you can check the problem.
Meanwhile I was testing the T3 Blank template, so you’ll see them installed.
jooservices
Friend
Hi there
I have received your PM but which site you want me check ?
And please provide reproduce steps also.
Thank you,
Viet Vu
I made a clean Joomla installation, added both T3 Framework and the Purity III, updated everything to the latest version and xLayout worked.
Then, I noticed that SEO URLs where activated, and upon deactivating them, the stopped working and gave the “403 Forbidden” error back.
Any idea what’s causing this behaviour?
I made a clean Joomla installation, added both T3 Framework and the Purity III, updated everything to the latest version and xLayout worked.
Then, I noticed that SEO URLs where activated, and upon deactivating them, the stopped working and gave the “403 Forbidden” error back.
Any idea what’s causing this behaviour?
jooservices
Friend
Hi there
As i said it look like server side issue.
You should work with your sysadmin first.
But i can help you inspect it with backend & CPanel access.
Thank you,
Viet Vu
jooservices
Friend
Hi there
As i said it look like server side issue.
You should work with your sysadmin first.
But i can help you inspect it with backend & CPanel access.
Thank you,
Viet Vu
This topic contains 10 replies, has 2 voices, and was last updated by 
We moved to new unified forum. Please post all new support queries in our New Forum
