• I use wp-stateless plugin. This redirects the uploads directory to google cloud storage (meaning there is no local uploads).

    The plus blocks puts its static content (css + js) into the uploads dir, rather than in the plugin dir. This means it does not work (get a 404 on fetch of theplus-post-2011715.min.css).

    Other plugins put their css + js into wp-content/plugins/<name> instead, which makes them compatible.

    Can I ask why this design decision? And, can it be altered? Otherwise I cannot use this plugin at all.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author POSIMYTH

    (@posimyththemes)

    Hi @donbowman

    We got your point. Can you try Dashboard -> The Plus Settings -> Performance -> Change option of Cache Manager to “On Demand Assets”? https://share.cleanshot.com/JljQYmgL Let us know, If that helps.

    Thread Starter donbowman

    (@donbowman)

    So thank you for that.

    It changes the behaviour, but does not resolve.

    /app/wp-content/plugins/the-plus-addons-for-block-editor/classes/tp-core-init-blocks.php:739 is looking for gs://path (which is the underlying Google Cloud Storage path of the wp-stateless), so it seems its not using the wordpress filesystem redirection, but instead going straight to the uplaods dir.

    /app/wp-content/plugins/the-plus-addons-for-block-editor/classes/tp-core-init-blocks.php:752 also looks for a different thing. It has removed the gs://, but still has a URL in it that is not correct

    below is a sample error message. The /agilicus/www, this would be gs://agilicus/www (which is the underpinning storage). it did not ‘upload’ the file (plus-css-1067.css) so its not there either, even if the path was correct.

    Both these errors are with the “On Demand”. Interesting, yours shows a “in header” optimisation option that i don’t have available in config.

    [agilicus-swww-stagingsr4k-ssnpzsgsn-846595c8ff-5z4dj www-staging] 2023/02/17 22:16:06 [error] 102#102: *519 FastCGI sent in stderr: "/agilicus/www/theplus_gutenberg/plus-css-1067.css') /app/wp-content/plugins/the-plus-addons-for-block-editor/classes/tp-core-init-blocks.php:752" while reading response header from upstream, client: 127.0.0.1, server: _, request: "GET /two-factor-herd-immunity/ HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.0-fpm.sock:", host: "www.agilicus.com", referrer: "local-cache-build"
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘incompatibility with wp-stateless due to use of uploads for static’ is closed to new replies.