A free extension like this survives only by reputation. You can help by submitting a review in the Joomla Extension Directory. Please take the time to make a review by clicking on the link below (opens in a new window)
1 month 5 days ago - 1 month 5 days ago#2579by Nick
Nick created the topic: 503 (Service Unavailable)
I think I might have found a bug.
Running Gantry5 with a custom template (loosely based on Helium) (could be the issue)
Installed eprivacy -> enabled -> setup working perfectly
Installed Headtag -> enabled -> setup working perfectly
-- In this situation, everything is working perfectly --
However, when placing Joomla in "Offline" mode (or) Maintenance Mode causes some strange issues.
1. If it is your first visit you can not close the modal popup.
3. but this expereince is scetchy at best (reports from users that this has unpredicitable results)
4. You can recreate the issues by "reconsidering cookies" but only on the frontend login
5. Once login and in the normal menu structure plugin functions as usual
The result of login in is a reload of the offline page
Console Returns 2 Items:
Failed to load resource: the server responded with a status of 503 (Service Unavailable) "index.php :: 1"
Failed to load resource: the server responded with a status of 503 (Service Unavailable) "/index.php?option=com_ajax&plugin=eprivacy&format=raw&method=accept&consent=1.10&country=not+detected :: 1"
The Return for the second link returns the word "true" and only this.
Note: Disabling eprivacy - everything functions as it should
Hey Michael - not trying to cause issues or increase workload.
Our situation is that we are in development of a few sites at the moment and we tend to use the offline status during development and we understand how "useless" this would be on a site that is offline.
The point for us is when we login to develop or show clients progress we sorta need everything working as it should be. Of course, we can enable and disable the module as needed however our clients will review progress without notifying us and can't get past this section (or) the privacy requirement is there. I hope you understand why we have brought this up.
I guess the best solution for us would be to disable this only on the index.php(offline) - but not sure if this is possible.
Thanks for getting back to me and I understand that this might be a one-off - was only hoping for an easy fix!