Support

Most likely you need to add more exceptions using the procedure you have already followed. After applying those exceptions and accessing your site, do you see any more non-loading items in the network view? Tip: Try CTRL-Refreshing the page to make sure nothing gets loaded from the cache instead of the server. This will let you find out all exceptions more easily.

CAn you give me the URL of a page where the calendar shows up so that I can take a look?

OK, I can see what is going on. It is not a conflict with ATP, it is a bug in the module. Upon clicking on the next month arrow, it tries to fetch a url like modules/mod_eventlistcalqajax/modules/mod_eventlistcalqajax/mod_ajaxloader.php?modid=303&Itemid=&el_mcal_month=6&el_mcal_year=2011 which is, of course, invalid. See how it duplicates its own name? That's the problem you have. This URL does not correspond to a valid location in your site, goes through Joomla!'s SEF parser and Joomla! responds with a "component not found" error.

There are various reasons for this:
1. You need to set up the live_site parameter in your configuration.php file
2. You need to enable RewriteBase / in your .htaccess
3. The module may not be designed to work with SEF URLs

There's nothing you can configure on ATP to work around this issue because it's not coming from ATP at all.

You're welcome! Please let me know of the outcome :)

It seems that the .htaccess file generated by Admin Tools, as well as the Web Application Firewall, have nothing to do with your issue. The problem seems to be with the calendar and the way it works when you have SEF URLs turned on. You will have to contact its developer. The common mistake with those modules is that the developers don't realise that the base URL is no longer the site's root when SEF is turned on. That's a bug in the module; I can't help you to fix it, but its developer should.

It's the third time I will try to explain why ATP has nothing to do with your problem and why the module doesn't work. Please read my replies above. I'm not going to say anything new here, I will just put what I said above in bullet points.

- Each Joomla! page emits a base tag
- The URL of the base tag is the current page's URL
- The base tag's URL is used to determine the full URL of relative URLs on the page
- E.g. base URL www.example.com/a/b/c.html and a relative URL with an href attribute of d.html result to the full url www.example.com/a/b/d.html
- All top-level pages have a base tag of www.example.com/a.html, ergo a relative URL to d.html is parsed as www.example.com/d.html
- The module emits relative URLs
- The relative URLs in the module are parsed by the browser to create full (absolute) URLs
- On top level pages, that works just fine by accident (NOT by design!)
- On pages deeper down the menu structure, the relative URLs emitted by the module in combination with the base URL of the page result to INVALID ABSOLUTE URLs.
- The invalid absolute URLs are caught by Joomla! and then tried to be parsed as SEF URLs
- Of course, they are not SEF URLs either and Joomla! throws a 403 Component Not Found error
- ADMIN TOOLS PROFESSIONAL HAS ABSOLUTELY NOTHING TO DO WITH THIS ISSUE AT ALL.

The structure of your old site is different. The calendar always displays on top level pages, where the base href address is 0 levels deep, e.g. http://www.example.com/somepage.html. This means that the relative URL used by the module is always correct. If you try to publish the calendar module to the blog pages and go inside a blog post's page, you'll see that the module will not work any more.

No worries! I know that most people don't realise how the browser parses the URLs you send to it or what is the difference between a/b/c.html and /a/b/c.html when referenced in a page at www.example.com/d/e/f.html. I'm glad you understand how the URL parsing process works now - that was my main objective when replying to this thread :)