Viewing 28 posts - 1 through 28 (of 28 total)
  • Author
    Posts
  • #765024

    Hello Enfold Support,
    I have atlease 30 websites running on Enfold and I am getting this error on all of them. This one of the them:
    The following error (see below and screen shot link in private area of the message) presents on all my sites using Enfold Theme, when I am in WordPress Dashboard. I updated a couple of sites from 4.02 to 4.03 to no avail. I am not using any security plugin and all my plugins are up to date. I have not modified functions.php and not using any child theme.
    Everything was working fine when I upgraded to 4.02 a couple of weeks ago and nothing was changed. I noticed this error today, when I logged in to WP admin.

    These are the errors in WordPress Dashboard:
    tent/p3pnexwpnas13_data02/17/3053117/html/wp-content/plugins/home/content/p3pnexwpnas13_data02/17/3053117/html/wp-content/themes/enfold/config-layerslider/LayerSlider/layerslider.php): failed to open stream: No such file or directory in /home/content/p3pnexwpnas13_data02/17/3053117/html/wp-includes/functions.php on line 4783

    Warning: fread() expects parameter 1 to be resource, boolean given in /home/content/p3pnexwpnas13_data02/17/3053117/html/wp-includes/functions.php on line 4786

    Warning: fclose() expects parameter 1 to be resource, boolean given in /home/content/p3pnexwpnas13_data02/17/3053117/html/wp-includes/functions.php on line 4789

    #765250

    Hi ayshehab!

    Can you please provide us on Private Data, the 30 licenses of Enfold please?
    Thank you very much for that

    Cheers!
    Basilis

    #765517

    Please see info requested in private date.

    #765536

    Hi!

    It is not about ” sespecting “. As right now we do not have a way to handle, we try to keep the process manual.
    That you for that.

    Kriesi is working to push an update.
    That issue is a false alarm of Wordfence which making the problems.
    Kriesi is notified and as layersldier tam released yesterday an update to by pass that fake warning, he will do push a LayerSlider update as soon as possible.

    We appreciate the patience and please note that there is no reason to panic at all.

    Best regards,
    Basilis

    #769627

    Enfold Support,
    I just updated a few sites from 4.0.2 and 4.0.3 to version 4.0.4 and still I have the same exact error. So, I guess the new update did not resolve this issue. Again, I am not using WordFence & all my plugins are up to date.
    Thanks

    #771757

    Hi,

    Sorry for the late reply!

    We have released Enfold 4.0.5 – kriesi.at/documentation/enfold/updating-your-theme-files/ which comes with the latest version of LayerSlider. It should help :)

    Best regards,
    Yigit

    #773484

    Hi Yigit,
    I updated a couple of sites to 4.0.5 and Still gets the same jibrish error about php. Just go to your WP dashboard and click on plugins.
    see original screen shot:
    http://cliolab.com/wp-content/uploads/2017/03/Enfold-Error-2017-03-22.jpg
    Thanks a million for looking in to this.

    #773546

    Hey!

    Is the server on every sits the same?
    The issue can be with the naming of the files that layerslider has, for example: controlerLayer with the L been capital.
    Can you check that?

    Best regards,
    Basilis

    #774060

    Hi Basilis,
    Every site is with different server (all with GoDaddy). I have not changed the original name of sliders (see screen shot link in private section). Even on the ones I changed, I still get this error, no matter what naming convention I have used. I contacted Godaddy before opening this case, they referred me back to the developer of the theme, pending “errors coming from the script” & I do not have child theme, have not modified the any of the .php files.
    Thanks

    #774305

    Hi,

    May you share your WP and FTP credentials, please? This way is easier to our team check it.

    Best regards,
    John Torvik

    #775545

    Sure, I have shared the info you requested in the private area. Please, if you find the issue & how to fix it, let me know every details, since I have to fix 20+ other sites with the same issue.
    Thank you very much

    #775593

    Hi,

    Can you please contact your hosting provider and ask them to upgrade PHP version to 7.0.x and check if that helps?

    Best regards,
    Yigit

    #775606

    Hey Yigit,
    If you are familiar with Go daddy, they do not change their environment unless there is a massive effect effecting many customers. Still, I contacted them regarding php 7.0. They are saying that it is still on the works and they won’t update until later this year. The earliest time (if it happens quickly) will be end of 2nd quarter of 2017. Honestly, I don’t think this issue is related to version of php on the server. I started experiencing this around 2 updates ago (Enfold 4.0 and later updates).
    Thanks

    #777525

    Hi ayshehab,

    Which version of php are you running? Those errors are most likely due to another Layer Slider update, which is not part of Enfold yet, but we are working on it. If your websites are not down, please bare with us.

    If you need further assistance please let us know.
    Best regards,
    Victoria

    #778724

    Every time a different person reads our about our issue, we get a different solution to the problem and non has worked out so far. Also the last person updated the case, seems did not bother to read the case history. Here Victoria, again: It is not one or two sites. We are running 25 -30 websites and all on Enfold with Godaddy hosting and majority are on php 5.2.6. The person prior to you, also pointed sliders naming convention as a possibility, which was not the case. Then asked for the login credential, and I provided the login credential. So, someone kindly login and see if you can truly pinpoint the issue. This is one site, once you find the problem, I have to do it for many more sites.
    In addition, based on support forum, it seems it is widespread complaint among Enfold users, so it can’t be specific to our sites / servers.
    Regards

    #778757

    Hi ayshehab,

    Well, 5.2.6 is a very old php version and as for WordPress requirements it is called a legacy environment. Which means that not all the features can work as the should and there have been many other php versions until php7, which I am sure, you hosting provider has available. The one before php7 was 5.6+. The longer you stay with the old php version the more issues you might have and multiplying that by all the websites that you have looks like many many problems that we might not be able to help you with.

    If you had your custom website and you were the one doing all the coding, you would not have to worry about plugins and themes that do not support old language versions, but WordPress and it’s infrastructure are moving forward towards faster and more reliable websites and you might want to consider catching up, before all your code base goes obsolete.

    If you need further assistance please let us know.
    Best regards,
    Victoria

    #778765

    Hello Victoria,
    That is typo. The php is 5.6.2 or higher. Please go back and read my response in regard to moving to php 7. Basically it is still in development state and hosting companies in US are reluctant to upgrade at this point. + honestly, this issue does not seems related to version of php on the server. just to let you know the big hosting companies in US are not upgrading to php 7 until 2nd or 3rd quarter of 2017 (if the development completed & released with stable version).
    Thanks

    #778925

    Hi ayshehab,

    I am pretty sure that issue is due to Layer Slider update, which will be available with the new version of Enfold. And if you’re running 5.6.2, you should be fine (for a little bit :) ).

    And if the errors are not breaking anything, please be patient and let our developers do their job.

    If you need further assistance please let us know.
    Best regards,
    Victoria

    #778956

    Hi Victoria,
    I found the problem.
    I did more digging and started to disable plugins one by one. It seems one of the plugins (Simple History) we are using does not like to work with Enfold. As soon as I disabled this plug in all php error went away. I don’t know if Enfold has problem with other Security Plugins or not, but it definitely does not like the one we are using. Enfold support team, still has access to WP dashboard, in case you want to check it yourself.
    Thanks

    #779065

    Hi,

    Thanks for the feedback and glad you found the culprit. The theme can’t be compatible with all plugins out there unfortunately, could you try out an alternative to it maybe?

    Best regards,
    Rikard

    #1001095

    ayshehab,

    you can also get some problem on GoDaddy while updating general themes and compatible plugins as GoDaddy often times out mid-update and it creates errors in your Functions.php like you originally mentioned. Solutions are to deactivate all plugins to see if it fixes it, but sometimes you can’t even get into the dashboard and need to remove plugins/themes via FTP.

    You may want to add the All In One WP Migration plugin tool to make zip backups local off all 30 of your sites from time to time as their backup/restore function also isn’t reliable.

    Jon

    #1001478

    Hi Jon,

    Thanks for sharing, much appreciated :-)

    Best regards,
    Rikard

    #1001510

    Things to note for others with this issue:
    1. Use a child theme as it makes updating easier without overriding any customs changes you make to functions.php in the child theme if you have to reinstall the theme

    2. Do occasional local website backups onto your harddrive. You should also keep recent versions of your plugins and themes in your project folder on your computer for your site in case you need easy access and save a notepad file of your purchase liscenses/keys.

    3. If you get errors like this after a update and can’t access the site or dashboard you may need to delete and reinstall the plugins or themes your were updating via ftp. Luckily with Enfold your theme settings save to the database and you can delete the theme and reinstall without normally losing any content or settings.

    4. Because of this it is good to keep the generic 2017 WordPress theme as an install backup in case you have to temporarily disable or delete enfold from a hosting or update error.

    Jon

    #1042368

    /public_html/wp-content/themes/enfold/functions.php on line 134
    enfold 4.5.1
    website url

    • This reply was modified 5 years, 6 months ago by amin tabrizi.
    #1042373

    in manual update error removing
    tanks

    #1042656

    Hi amintab2001,

    Thanks for the update, I assume you got things working?

    Best regards,
    Rikard

    #1042675

    yes that right
    tanks

    #1042722

    Hi,

    Tanks for the clarification.

    Best regards,
    Rikard

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