Update to 0.2.3 causes a PHP Warning

  • Resolved Joe Hana

    (@joehana)


    4 years, 9 months ago

    Hi,

    since the last update from 0.2.2 to 0.2.3 I have the following warning on the whole website: Warning: file_get_contents(/www/htdocs/xxx/xxx/wp-content/uploads/elementor_icons_files/fontello-96786cf2.zip/fontello-96786cf2/css/fontello.css): failed to open stream: No such file or directory in /www/htdocs/xxx/xxx/wp-content/plugins/custom-icons-for-elementor/elementor-custom-icons.php on line 411

    Of course I’m aware that this issue won’t display by disabling WP_DEBUG and I’m aware about the included CSS Regeneration tool which perhaps might solve this but I’m a little afraid to do so since the last time this resulted in all icons to be resetted, in other words I needed to replace all icons on the whole website once again.

    Do you know of another reliable way to get this fixed?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Michael Bourne

    (@michaelbourne)

    4 years, 9 months ago

    Hey @joehana

    Any chance you can push your site to staging and give me admin/ftp access to take a look? A couple people have had this issue, but I can’t replicate it on any of my test sites.

    I can mute the error simply enough, but I’d like to see if I can find the cause of it first.

    Thread Starter Joe Hana

    (@joehana)

    4 years, 9 months ago

    Thanks for getting back so quickly. In the meantime I could fix this by myself. Few weeks ago we’ve re-organized the webspace a bit and have renamed the folder containing the website, and it seems like this was at fault. For some reason the search and replace on the database didn’t change every instance of the old path.

    Still curious why the warning didn’t show up earlier, but nevertheless it is working now as it should. Thanks for everything again.

    Hope for the others a solution can be found as quickly as I found one.

    All the best

    Plugin Author Michael Bourne

    (@michaelbourne)

    4 years, 9 months ago

    Thanks for the update, glad it got fixed!

    Only a few issues out of 30k+ installs, so I’m assuming they’re all edge case like yours.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Update to 0.2.3 causes a PHP Warning’ is closed to new replies.