Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • February 14, 2019 at 5:45 pm #1067081
    AdrianSmithUK

    Hi
    My customer had 4.4.1 installed and we upgraded to 4.5.3.

    Everything seemed to go fine when we are logged in but when I view the home page in Incognito Mode on Chrome we get a 404 error.

    I tried:

    Disabling WP Super Cache
    Switching to Query Parameter Permalinks
    Refreshing the WP .htaccess permalink rewrite rules settings
    Clearing the Browser Cache
    Viewing on a fresh computer
    Setting the Home Page / Blog Page Settings Using WP and Enfold

    Nothing had any effect.

    I switched back to 4.4 and both themes are available in the Appearance Section.

    I am including the login details below.

    Can you help?

    Kind Regards,
    Adrian Smith

    • This topic was modified 5 years, 10 months ago by AdrianSmithUK.
    February 16, 2019 at 6:59 am #1067632
    Rikard

    Hi Adrian,

    I see that you are running 4.4.1 and it works in that version I assume? And the problem start when you activate 4.5.4? If so then can we activate the new version for testing purposes?

    Best regards,
    Rikard

    February 16, 2019 at 10:34 am #1067673
    AdrianSmithUK

    Hi Rikard,

    I’ve backed the database and files up so feel free to do what you like (including enabling / disabling plugins).

    Kind Regards,
    Adrian Smith

    February 16, 2019 at 10:35 am #1067674
    AdrianSmithUK

    PS: Make sure that you view the home page in incognito mode when you switch to 4.5.4. It works fine when logged in.

    February 18, 2019 at 11:04 pm #1068625
    Basilis

    Hi,

    What is your server giving for the 404 error?
    Anything loged into the log file?

    Best regards,
    Basilis

    February 19, 2019 at 11:33 am #1068879
    AdrianSmithUK

    Hi Basilis,

    Sorry for the delay. The website is on a shared hosting platform (1&1 Ionos) and I had to enable the error logs.

    I have produced a 2 minute video showing you the tests I did and what the problem is and I have put the link and password in the Private Content below.

    I have also created you an FTP account on the server and the details are below.

    You will see in the video that there is nothing in the error log. After the video I checked that the error logs were working by creating a php file with an error in it and they work fine. (See my-error-file.php)

    I hope that helps.

    Kind Regards,
    Adrian

    February 21, 2019 at 12:24 pm #1069893
    AdrianSmithUK

    Any Progress Basilis?

    February 24, 2019 at 6:46 pm #1070996
    Mike

    Hi,
    Sorry for the late reply, and thank you for the video. While I see this error on your site, I was unable to reproduce it on my localhost, so I tried disabling some of your plugins without success, but this I noticed that your root folder file permissions is: 1705, instead of 0755, which means the “group” can’t read your site root. Which makes sense because in incognito mode you can see other pages, such as /about-us/ you just can’t see the root.
    Please see your Loginizer Dashboard and look at the file permissions, then ask your webhost to fix your root file permissions.

    Best regards,
    Mike

    February 25, 2019 at 12:03 pm #1071246
    AdrianSmithUK

    Hi Mike
    Many thanks for your help.
    I created a new home sub-directory on the server, moved the files across and set the permissions to 755 but unfortunately it didn’t work.
    I’m going to migrate the website to a different server and see if that fixes it.
    Kind Regards,
    Adrian Smith

    February 25, 2019 at 2:03 pm #1071282
    Mike

    Hi,
    I have seen cases where I couldn’t change the file permissions, but the webhost could with a shell account, perhaps this is also happening to you?

    Best regards,
    Mike

    February 25, 2019 at 3:22 pm #1071307
    AdrianSmithUK

    Hi Mike
    I moved the website over to my own AWS EC2 server which has 5 healthy Enfold websites running on it and it still exhibited the same problem.
    I wondered if it might be a general WordPress issue so I did some research and found a post where somebody had fixed the problem by duplicating the home page and pointing at the new page.
    That fixed it!!!
    Many thanks for your help.
    Kind Regards,
    Adrian

    February 26, 2019 at 6:57 am #1071642
    Mike

    Hi,
    Thanks for sharing your solution, I’m glad it’s sorted out now.
    I assume we can close this now, but I like to ask. Shall we close this then?

    Best regards,
    Mike

  • Author
    Posts
Viewing 12 posts - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.