Make sure your site is PHP8.2
Click on components > banners > banners
Click on components > banners > tracks
Click on components > banners > clients
Page loads
503 error.
Please note components > banners > categories loads fine.systeminfo-2023-04-26T15_45_15+01_00.txt
Labels |
Removed:
?
|
Labels |
Added:
No Code Attached Yet
|
I put it to maximum and I don't see any errors or any debug information.
unable to replicate on a "clean" 4.3
can you try without extensions ?
Labels |
Added:
Information Required
|
@uglyeoin Does your thumbs up for the previous comment mean that you have successfully tried without 3rd party extensions? Or does it just mean that you have liked the comment? If the issue was caused by a 3rd party extension, please close it, or let us know so we can close it. Thanks in advance.
I am now not seeing any issues despite being on 8.2 and having done nothing different with extensions. I can only assume that this was a hosting issue that they have resolved somehow.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-05-01 18:57:23 |
Closed_By | ⇒ | uglyeoin |
I can't tell you why this only happened on some com_banners pages, but I believe this may have been a problem with the Engagebox plugin/module/component.
Interesting: I have just come across the same problem, ie I had a 503 error page on all com_banners links in the backend.
After investigating a bit I realized that the 503 would only trigger
I could reproduce this on the 3 different websites I tested for this:
(the 3rd one is a test website where I only had 2 extensions installed. I disabled them and still had the same issue)
If debug is enabled without the plugin you still get all the non minified assets
Also please confirm if it's a litespeed 503 or a joomla 503. If it's the former I have commented elsewhere what to check on your server.
@brianteeman where can we find the somewhere elsewhere to check? I use Litespeed server but mine is now working. I think it may have been firewall related. Which seems odd, perhaps banners is doing something weird that it didn't like. It also triggers on the edit overrides page or something. My host has now added a rule.
Sorry at an airport. It's a setting in litespeed for prams in urls
As I can see in your system info, you have debug on (good) but error reporting = default. Could you change error reporting to maximum and check if there is something shown?