Hi. I’m using an old, unsupported theme, Royale, and it seems to work fine, and all changes I make are updating except to the Home Page. When I go to the home page directly, it is the older Home page. I can tell this as there is the old text there and also the menu shows some old submenus.
This is what is the old Home Page that is being published.
When I’m in the site (ie click into another page) the menu is now correct, with no sub pages.
This is the Home Page in Rapid Weaver, and isn’t being published
It’s only relevant as I’m thinking of updating my show reel, but as it’s on the Home Page, currently it won’t appear.
I’ve noticed that one of the top line menus shows the sub menu, while the others don’t.
Have you tried to re-publish all files & then clear the browser cache?
I looked and you are going to two different URLs.
From the main Web address
http://www.leviathan-films.co.ukyou are going to This URL
http://www.leviathan-films.co.uk. You also get to that address from the Logo.
From the Menu, if you hit the Welcome button, you end up at this address:
index.html at the end. The last mod date for the
http://www.leviathan-films.co.uk/index.html file is
Sun, 24 Oct 2021 12:48:43 GMT.
The Last Mod date for the file without the index is
Mon, 01 Mar 2021 10:33:47 GMT .
It looks as though you aren’t using tidy links as the menu items all use full addresses.
It’s also strange that your HTML pages
index.html seem to have a cache control being set into the future.
That would allow the user to read from browser cache or proxy servers cache for up to 180 days (
Fri, 22 Apr 2022 17:48:49 GMT from today). That’s not probably what you want. Prior users would need to clear their browser’s cache to get any updates.
So back to the question, why you are getting different pages for the “full URL (With index.html)” as compared to the URL without the index.html? My best guess is something is going on with the host configuration or htaccess file.
I’m seeing some status code 307’s on at least some pages.
307 Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.
That’s kind of strange. Hate to say this but it looks like something is a miss at your host.
BTW: you really need to get the site switched over to https.
Thanks so much for such a detailed reply. I’ll take this to my ISP, who are very good at support. And I’ll sort out the https. Thanks again.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.