Debugging Filesystem Errors

Popup Maker generates cache files for the styles and scripts for popups and themes. For example, when you adjust the settings for a theme, the plugin will regenerate these files. Without these files, Popup Maker would have to load all the settings from the database and parse them. However, to keep your site loading fast, Popup Maker instead caches all the settings into CSS and JS files which get loaded instead.

However, there are times where this may fail. When this occurs, you may see a warning saying something such as:

Popup Maker detected an issue with your file system's ability and is unable to create & save cached assets for your popup styling and settings.

If you are receiving that message or a similar one, here are a few things to try:

1. Try to create cache again

The alert message stays until either the caching works (after a retry) or you select to keep the current method. If it is working since you last tried clicking, the message will still remain. So, if you have not already, try clicking the "Try to create cache again" once or twice to see if the message stops appearing.

2. Check Popup Maker error logs

Starting in Popup Maker 1.12, there is a new "Error Log" tab in the "Tools" page. You can see any errors Popup Maker is encountering from this tab which might help you identify the cause of the filesystem errors. After following the rest of this guide below to identifying the cause, you can click the "Download Error Log" button on this page to send a copy to support so we can help you fix the issue.

3. Check Site Health to ensure file permissions are correct

Starting in WordPress 5.2, there is a Site Health tool that can check for common issues. One area that is checked is file permissions.

You can get to Site Health by going to the "Tools" menu in your WordPress Admin area and going to the "Site Health" page which should look like this:

Click on the "Info" tab and scroll down to the "Filesystem Permissions" section to make sure all folders are writeable as shown here:

If the plugins folder, wp-content folder, or uploads folder are not writeable, you will need to reach out to your hosting provider to get these changed.

4. Check to see if the cache files are created

If you have access to FTP or a file manager for your site, look into the "wp-content" folder to find the "uploads" folder. Inside the "uploads" folder, check to see if the "pum" folder is present. This is the folder Popup Maker creates and tries to put the cache files in.

If the "pum" folder exists, check inside to see if the pum-site-scripts.js and pum-site-styles.css files are present.

Lastly, if these are there, open them to make sure there is content inside. If there is, look for the "Last modified time" which should be near the top of each file and check to see if it is around the same time as when you last edited a popup or theme.

* Please note: If you have any ad blocking settings enabled, these names may be different. Try to turn off any Popup Maker ad blocker settings while debugging the cache files.

If the folder or files are not present at all, this means that either file permissions are incorrect or your WordPress site has some security or file system in place that is preventing Popup Maker from creating the files. 

First, if you have any security plugins, temporarily disable them and test again. If the cache begins to work, then the security plugin may have a file permission security feature which you may need to adjust. Be sure to re-enable your security plugin!

If disabling the security plugin did not resolve the issue, then you will need to reach out to your hosting provider to ensure that Popup Maker has write access to the uploads directory.

5. Check to see if cache files are accessible

Some hosting providers and security plugins will adjust the permissions of the folder and cache files in a way that makes the files not able to be loaded into a browser. To check for this, Popup Maker will try to load the cache files right after they are created. If Popup Maker does not receive a status code in the 200's, it will trigger a warning message.

One quick way to test this is to try to load the files in the browser. Depending on your site structure, the URL would be something such as

Additionally, you can test using to ensure both files are returning a 200 status code. Enter in the URL to both the CSS and the JS file and then click "Check Status":

If these files do not return a 200 status code, then you will need to reach out to your hosting provider to ensure the uploads and pum folders are accessible as well as these individual files.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.