Plugin error: open_basedir restriction

  • Resolved tigzik

    (@tigzik)


    2 years, 9 months ago

    Hi there,
    I downloaded and activated this plugin resulting in several errors:

    Warning: is_readable(): open_basedir restriction in effect. File(/www/doc/www.mydomain.com/www/wp-content/plugins/tutor-lms-divi-modules/tutor-lms-divi-modules.php/tutor-lms-divi-modules-cs_CZ.mo) is not within the allowed path(s): (/www/doc/www.mydomain.com:/disk2/doc/www.mydomain.com:/usr/share/php:/www/tmp:/tmp) in /www/doc/www.mydomain.com/www/wp-includes/l10n.php on line 741

Warning: Cannot modify header information - headers already sent by (output started at /www/doc/www.mydomain.com/www/wp-includes/l10n.php:741) in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 6712

Warning: Cannot modify header information - headers already sent by (output started at /www/doc/www.mydomain.com/www/wp-includes/l10n.php:741) in /www/doc/www.mydomain.com/www/wp-admin/includes/misc.php on line 1310

Warning: Cannot modify header information - headers already sent by (output started at /www/doc/www.mydomain.com/www/wp-includes/l10n.php:741) in /www/doc/www.mydomain.com/www/wp-admin/admin-header.php on line 9

    I have the last updates for Tutor LMS, Tutor LMS Pro and Divi. I tried the same with two different setups where one of them was WP with only these plugins installed/activated. I’m using child theme. It seems like a security issue/restrictions on the WP/hosting site?

    Thanks for the help.

Viewing 5 replies - 1 through 5 (of 5 total)

  • Hello @tigzik,

    First warning appears to be related to your translation .mo file. You can put the relevant file within the allowed file path.

    Rest of the warnings are due to spaces or characters or new line before PHP opening tags or after the closing tags. Usually fixing the first warning may resolve subsequent warnings.

    Thread Starter tigzik

    (@tigzik)

    Hello @munayam,

    Thank you for your answer. I deactivated Loco Translate and switched WP into EN(US) which seems to be default language for the plugin, but this doesn’t resolve the issue.

    I found a similar topic here, that seems to be related with incorrectly defined/called path by plugin. Based on the hosting, it might ask access where it shouldn’t. Could you check on it please?

    Thank you,
    Best regards

    Thread Starter tigzik

    (@tigzik)

    I’ve double checked with our hosting provider and it is, indeed, a problem of open_basedir access rights. It’s unfortunate for us, because we run on a shared server so it’s not possible to change the settings for security reasons.

    The solution from our end is migrating to a private server and change the access rights.

    I’m not sure if the code can be changed in favour of shared hostings or not, but it would be awesome. This way, this plugin can be only used with a private server allowing to read/write all folders/files.

    For future debugging purposes of the others, we were using Active24.com shared hosting Linux Complete (for WordPress).

    Hello @tigzik,

    Thanks for sharing your findings. I will share this with my team to see if we can bring any changes in the future update.

    Thread Starter tigzik

    (@tigzik)

    @munayam Thank you. That would be helpful in the future.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Plugin error: open_basedir restriction’ is closed to new replies.