Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • January 15, 2019 at 4:01 pm #1054160
    andybarn

    Hi

    I am currently running WordPress 5.0.3 on my development server
    I am running Enfold 4.4.1

    All Good.

    I tried upgrading to 4.5.2 by renaming the enfold folder to “perfecto360” and uploading the latest version of Enfold (4.5.2) to folder “enfold” so it was a clean upload.

    When I activate the new Enfold 4.5.2 I get a HTTP ERROR 500

    If I roll back to Enfold 4.4.1 all OK

    So I am just not able to update to 4.5.2 and I do not understand why, please help

    I have changed the style.css name of both enfold installations so you can see which is which.

    I currently have Enfold 4.4.1 activated and if you go to Appearance/Themes and Enfold 4.5.2 and try a “Live Preview” you also get a HTTP ERROR 500, you do not even need to try and activate it.

    I have tried disabling all plugins and that did not work.

    Please find the login details in the Private Area so you can take a look.

    Thanks
    Andy

    • This topic was modified 5 years, 10 months ago by andybarn.
    January 16, 2019 at 9:16 pm #1054745
    Victoria

    Hey andybarn,

    Can you please check server log for error?

    Which version of php are you running?

    Best regards,
    Victoria

    January 17, 2019 at 7:58 pm #1055138
    andybarn

    Hi

    I was running php5.4 when I received error

    I upgraded to 7.2 and still get the 500 error

    I spoke qwith my server people and they looked at the server logs but nothing.

    However they did come up with something, see below

    “I would suggest to contact plugin provider and ask for php requirements as the logs are not getting generated for the same, there are surely some php requirements, that needs to be done on server”

    They then added

    “getting below error in wp-admin logs, [17-Jan-2019 17:42:48 UTC] PHP Fatal error: Cannot redeclare av_countdown_events_fallback() (previously declared in /home/webuk2014/public_html/dev/perfecto360/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/events_countdown/events_countdown.php:16) in /home/webuk2014/public_html/dev/perfecto360/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/events_countdown.php on line 12
    Searched for the solution on forums and can see it is related to file events_countdown.php
    You can also provide above logs to plugin provider”

    Hope this helps you find problem

    Andy

    January 18, 2019 at 8:42 am #1055369
    Vinay

    Hi,

    Thank you for contacting us.

    It appears you have multiple version of the themes stored on the server. This will sometimes lead to conflict.

    Please back up your site and delete both versions of the theme folder from the server.

    Download the latest copy of the theme files from ThemeForest.

    Follow this step by step guide to install the Enfold theme again. It should work for you. If you still have an issue please leave the error message to show up so we can troubleshoot this issue. Without seeing the error it is not possible to troubleshoot the issue.

    Best regards,
    Vinay

    January 18, 2019 at 6:36 pm #1055593
    andybarn

    Hi Vinay

    You can see the error wp-admin logs (see below)

    “getting below error in wp-admin logs, [17-Jan-2019 17:42:48 UTC] PHP Fatal error: Cannot redeclare av_countdown_events_fallback() (previously declared in /home/webuk2014/public_html/dev/perfecto360/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/events_countdown/events_countdown.php:16) in /home/webuk2014/public_html/dev/perfecto360/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/events_countdown.php on line 12
    Searched for the solution on forums and can see it is related to file events_countdown.php
    You can also provide above logs to plugin provider”

    I only have two instances of the theme in that directory, the active 4.4.1 and the new 4.5.2 which
    I FTP’d over to a clean directory.

    The reason this is on my development server is I copied there from the live site (on a different server) which was having the same issue.
    Therefore the problem is not unique to this server.

    Please have a look at the error log and see for your self.

    Thanks
    Andy

    January 19, 2019 at 12:57 am #1055732
    andybarn

    Hi

    Further to my post above I have now done the following:-

    Created a fresh install of WordPress 5.0.2 on another domain I own

    Uploaded via FTP the latest version of Enfold 4.5.2

    Login to WordPress, no problem

    As soon as I try and change the Theme via Apperance/Themes to the Enfold Theme I get the 500 Error

    I am then stuck with the 500 error whenever I try and access the site.

    The only way tro recover back from this is to rename the “enfold” folder to some thing like “enfold_bak” using FTP and then accessing WordPress admin and making the default WordPress “twenty ninteen” active. I then rename the “enfold_bak” folder back to “enfold” using FTP.

    Everything is pointing at a problem between WordPress 5.0.2 and Enfold 4.5.2

    I provide full access details to the FTP and wp-admin in private area

    Please take a look at this, I have spent hours trying to get this to work.

    Thanks
    Andy

    • This reply was modified 5 years, 10 months ago by andybarn.
    January 19, 2019 at 2:09 am #1055754
    andybarn

    Hi

    I think I may have found the problem.

    The fresh upload of enfold 4.5.2 may not have been a fresh upload. I discovered that I had unzipped the file and overwrote the original enfold file on my local machine. I then FTP’d this to the server thinking it was a fresh install but it was not the latest file but a combination of the old and new. Looking at this file, I discovered duplicate instances of the events_countdown.php (which I notified you about on the 17th above.)

    I will now extract a fresh upload of 4.5.2 and FTP to the server (first deleting the existing enfold folder) – hopefully this will fix the problem. It is very late now so will do this in the morning but wanted to inform you not to spend anymore time on this until I had proved this is the fix (which I am sure it is)

    Kind regards
    Andy

    January 19, 2019 at 1:13 pm #1055849
    andybarn

    Hi

    OK, just to confirm, this is now all OK – update to 4.5.2 successfull

    The key to this was the error log file (error_log) in the WordPress root directory. This pointed where the problem was.

    Thanks for your help.

    Andy

    January 20, 2019 at 6:57 pm #1056246
    Victoria

    Hi Andy,

    Glad you finally got it working for you and yes, the log file is always there to help! :)

    If you need further assistance please let us know.

    Best regards,
    Victoria

    January 20, 2019 at 6:57 pm #1056247
    Victoria

    Hi Andy,

    Glad you finally got it working for you and yes, the log file is always there to help! :)

    If you need further assistance please let us know.

    Best regards,
    Victoria

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