fopen Directive must be Enabled

  • Resolved crookesa

    (@crookesa)


    2 years, 2 months ago

    I have this option enabled in my php.ini file and it’s also showing as on in my phpinfo().

    Can you advise further please?

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

    (@wpseahorse)

    2 years, 2 months ago

    Hi,

    We have had reports from some users where this directive is showing on phpinfo() but is being overwritten by another parsed php.ini file(s)

    On both occasions this was because of multiple versions of PHP on the same server. Can you review any additional .ini files parsed: e.g. /path/to/php/php7*/etc/php.ini and make the change there also.

    This should resolve the issue but if you need further support, please feel free to raise a ticket with our support team who can offer more hands on assistance: https://www.seahorse-data.com/wp-on-aws-support-portal/

    Thread Starter crookesa

    (@crookesa)

    2 years, 2 months ago

    Thanks I spoke to my hosting company and their response was

    I was also able to resolve the issue temporarily by globally enabling the option. This wouldn’t be able to remain this way.

    I’m not sure what could be causing the issue. Reviewing phpinfo.php you will see that fopen is enabled both local and master. The error remains unless the option is enabled globally which can’t be altered on our shared fleet.

    We could temporarily enable it at times you need to run it but the plugin shouldn’t be requiring a global value when the local and master values are showing correct.

    Could you check and see if this is the case with the plugin and it’s not looking for a global setting?

    Plugin Author wpseahorse

    (@wpseahorse)

    2 years, 2 months ago

    Hi

    This is a limitation of the shared hosting platform as opposed to anything within WordPress. The software reads what is output from the server, so WordPress (and its associated plugins/themes) is not aware whether this is a local/global setting (it’s the only one available) so without control of this parameter our software will not run. Hope this makes sense?

    We do offer custom migration services for edge cases however and would be happy to have a look at this one for you? Having this little control of the server is unusual and my concern would be there are other limitations that may restrict a seamless automated process e.g. can the site run on latest versions of PHP etc.

    This case needs some investigation and if this is something you would like to pursue please raise a ticket here: https://www.seahorse-data.com/wp-on-aws-support-portal/ quoting the forum thread title and we will pick it up there.

    Thanks – Seahorse Team

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘fopen Directive must be Enabled’ is closed to new replies.