Recently, any new page I deploy on my website is acting strangely.
It might initially load correctly, but after a reload the browser displays a 404 error. If I keep reloading, it will just alternate between the two states.
The behaviour is independent of device and browser (I’ve tried Chrome and Safari) and the problem does not occur when testing on my localhost.
I stripped back the page code (just incase it was a dodgy script):
<!doctype html>
<html>
<head>
<base href="/admin/">
<meta charset="UTF-8">
<title>Test Page</title>
</head>
<body is="dmx-app" id="test01">
This is a test page
</body>
</html>
In Project Settings I have ‘Use Routing’ and ‘Add Auto Base’ both set to ON but that hasn’t caused problems with any of the previous php pages within the admin directory.
Does anyone have any suggestions I can try? Or let me know what other information to provide.
Yeah, I didn’t set up any routing for the test01.php page, but I also didn’t do this for other pages within the same admin subdirectory (eg. https://www.promostuff.com.au/admin/login.php) and these render correctly.
So I turned off routing in ‘Project Settings’ which enabled me to remove <base href="/admin/">. But unfortunately the same behaviour is occurring once I redeploy. Very strange.
That is very strange. I just tried it again as well and confirmed that line was gone, reset my browser cache and everything and it’s still happening. I’m at a loss.
Unfortunately I’m still unable to resolve this problem. After I delete the test01.php file from my server using the file manager, as expected the page doesn’t load. However once I upload it again, it starts displaying the dual behaviour I’ve mentioned in previous posts.
At this stage I’m not sure if it’s a Wappler, Docker or AWS issue.