[Build Asset] Notice: Snapshot store directory is unavailable.

  • neralex

    (@neralex)


    2 weeks, 6 days ago

    This debug-message is flooding the debug.log. What is the reason for and how can I stop it?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Paul

    (@paultgoodchild)

    2 weeks, 6 days ago

    If you go to Shield > Configure > Debug Info > “Current Cache Directory Path” – does the filesystem path that’s detailed there exist on your website? Have you had any major hosting configuration changes or migrations in the last while?

    Thread Starter neralex

    (@neralex)

    2 weeks, 6 days ago

    Current Cache Directory Path
    Unavailable

    This is a copy of a wp-instance, which is running in a local environment (mamp pro/macos). the /wp-content/shield/ folder exists and all needed permissions are granted. touch wp-content/shield/test.txt works as expected.

    Plugin Author Paul

    (@paultgoodchild)

    2 weeks, 6 days ago

    You’re going to need to look at the permissions more closely. Shield will attempt to create a directory for writing temporary files. If it can’t write those files, then it’s unavailable. While it may appear that all the permissions needed are granted, Shield (via WordPress) is not able to write to the disc. If it was able to write to the disc, there would be a cache directory path specified.

    Thread Starter neralex

    (@neralex)

    2 weeks, 5 days ago

    Sorry but I can upload each media, install plugins and all other plugins can write files to this installation. so apache can reach /wp-content/. only this plugin is failing. I just renamed /wp-content/shield/ but the plugin doesn’t create a new one by its own. I just disabled and reanabled the plugin but the issue still exists. So I tried to create this folder manually but no chance. this plugins still shows:

    Current Cache Directory
    Path Unavailable

    Plugin Author Paul

    (@paultgoodchild)

    2 weeks, 5 days ago

    The only thing I can suggest is that you reset the plugin. I can’t explain why it can’t write to its directory on your local host. This isn’t something that has ever been reported before.

    Thread Starter neralex

    (@neralex)

    2 weeks, 5 days ago

    I deleted before the reset the shield-folder in /wp-content/, then I did the reset and after that, the folder was created by the plugin itself. That means this issue is not based on write-permissions. Is the path or parts of it to the caching folder stored into the database?

    • This reply was modified 2 weeks, 5 days ago by neralex.
    Plugin Author Paul

    (@paultgoodchild)

    2 weeks, 3 days ago

    Hi, thanks for doing the reset and reporting back. That does speak to an issue with the cache directory being automatically recreated. We have done some work on this, and we will continue to do so before the next release. Thanks for reporting back and reporting this issue.

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

You must be logged in to reply to this topic.