Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • The plug-in provides a very straightforward means of applying nonce or hash to inline scripts and styles as needed.

    For anyone who has encountered this hardship, I think it is implied by the name of the plugin.
    “No unsafe-inline”

    It’s a brilliant plug-in. Just activate it, and the configuration screens are very self-explanatory.

    WordPress does include a nonce function, however applying nonce or hash to inline scripts and styles should really be a last resort to first trying to build the site without the use of inline scripts, and ensuring styles are contained in a external stylesheet etc. Until builders and plugins catch up, this plug-in provides a realistic means for most WP websites to achieve a CSP free of high and medium priority risks.

    Thread Starter kojis

    (@kojis)

    Hello @mociofiletto

    I can confirm that the upload directory is _not writable_ on WPVIP hosting.

    This information seems helpful:
    https://wpml.org/errata/wordpress-vip-hosting/

    Unfortunately, despite the fact that it is not writable, the check_write_permission function you cited, does in fact return true which generates the error.

    I have found that forcing this function to return false, allows the plugin to function on WPVIP with an additional minor change:

    $mu_dir    = trailingslashit( WP_CONTENT_DIR ) . 'client-mu-plugins';

    Must be changed to:

        $mu_dir = '/client-mu-plugins';

    in two locations within
    /src/Nunil_Manage_Muplugin.php

    and the muplugin must be specifically committed to version control and deployed during the build pipeline process.

    I have noted the same behaviour as programmin with a site I am working on now.

    This is even the case on the demo site where the same symptom may be observed.
    http://huge-it.com/wordpress-plugins-gallery-demo/

    • This reply was modified 9 years, 7 months ago by kojis.
Viewing 3 replies - 1 through 3 (of 3 total)