Support

I downloaded and installed the T3 Package. I’ve enabled Thememagic. When I click on Thememagic or MegaMenu I get 404 – Component not found.

Since Theme Magic uses LESS files to make the real time changes to the design, I thought the issue maybe related Admintools htaccess rules preventing the loading of LESS files. I have added less to the list of back-end and front-end file types allowed in select directories.

I also went to Components > Admin Tools > Web Application Firewall > Configure WAF > Visual Fingerprinting Protection and set "Allow Site Templates" to "Yes"

It still won't load and I get a 404 - Component not found.

Not really sure what else to try an modify within Admintools so that Thememagic and MegaMenu will load.

Thanks in advance for any suggestions.

I'm using a T3 based template on a couple of my sites without a problem. I can't see anything that I've done in the way of exemptions for the template or plugin.

In Configure WAF, on the Visual Fingerprinting Protection tab, what do you have in the "List of allowed tmpl= keywords" field?

You may get a more informative error message by setting the Error Reporting field in Global Settings to "Development". You don't want it to stay that way on a live site, we just want to see if it changes the error message.

Lastly, disable the plugin System - Admin Tools and swap your enhanced .htaccess file for the htaccess.txt file in the root of your site. That is the Joomla! standard .htaccess file. We use that as a "known good" file for testing. This will completely disable Admin Tools. If the error still occurs, it isn't Admin Tools causing it.

Dale, thanks for your reply. I will try your suggestions tomorrow.

I have List of allowed tmpl= keywords field reads: component,system,raw,koowa

This was the default. Should I add something else for T3?

Gary

Those are the keywords that I have too. Please let me know how you make out with the Error Reporting setting and disabling Admin Tools.

Thanks for your help. I temporarily set Error Reporting field in Global Settings to "Development". I think the issue is with the System – virtualdomains plugin. I disabled it and the 404 error messages went away.

I'm glad you're on the road to getting it fixed. If I can help, please let me know.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.