---
title: Popup Maker Detected an Issue With Your File System
description: "Table Of Contents - [What does all that mean anyway?](#what-does-all-that-mean-anyway) - [Popup settings and styles are kept in a JS and CSS file](#popup-settings-and-styles-are-kept-in-a-js-and-css-file) - [Why is this faster?](#why-is-this-faster) - [Make sure you're running Popup Maker version 1.18.1 or greater](#make-sure-youre-running-popup-maker-version-1181-or-greater) -…"
url: "https://wppopupmaker.com/docs/problem-solving/popup-maker-detected-an-issue-with-your-file-system/"
updated: "2026-02-18"
category: "Common Questions & Issues / Problem Solving"
---

# Popup Maker Detected an Issue With Your File System

Table Of Contents

- [What does all that mean anyway?](#what-does-all-that-mean-anyway)
  - [Popup settings and styles are kept in a JS and CSS file](#popup-settings-and-styles-are-kept-in-a-js-and-css-file)
  - [Why is this faster?](#why-is-this-faster)
- [Make sure you're running Popup Maker version 1.18.1 or greater](#make-sure-youre-running-popup-maker-version-1181-or-greater)
- [Trying to create the cache again doesn't work](#trying-to-create-the-cache-again-doesnt-work)
- [1) Check for errors in the Popup Maker error log](#check-for-errors-in-the-popup-maker-error-log)
  - [Debug logging is disabled](#debug-logging-is-disabled)
  - [Download the error log to share with support teams](#download-the-error-log-to-share-with-support-teams)
- [2) Check for the pum-site-scripts.js and pum-site-styles.css files on your web server](#check-for-the-pum-site-scriptsjs-and-pum-site-stylescss-files-on-your-web-server)
  - [Don't see the pum directory or the asset files?](#dont-see-the-pum-directory-or-the-asset-files)
- [3) Check for wrong filesystem permissions for the wp-content and uploads directories](#check-for-wrong-filesystem-permissions-for-the-wp-content-and-uploads-directories)
  - [Not writable is bad](#not-writable-is-bad)
- [How do you fix the filesystem permissions problem?](#how-do-you-fix-the-filesystem-permissions-problem)
- [4) Check for network mischief that's blocking HTTP connections to the files in /wp-content/uploads/pum/](#check-for-network-mischief-thats-blocking-http-connections-to-the-files)
  - [One quick check](#one-quick-check)
- [Here are some other suspects](#here-are-some-other-suspects)
- [Ask for support](#ask-for-support)

If you see the admin notification message below and want to know what to do, you're at the right place.

> 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. This may lead to suboptimal performance. Please check your filesystem and contact your hosting provider to ensure Popup Maker can create and write to cache files.

### Chat with Claude

Need a hand? You can chat with Claude about this guide. We already set up the instructions for you. Just click and go.

 ✨[Ask Claude about this topic](#).

## What does all that mean anyway?

I don't care. Just [get me to the troubleshooting steps](#make-sure-youre-running-popup-maker-version-1181-or-greater).

To help popups load faster on a page, Popup Maker grabs your popup settings and styles (assets) from the database and stores (caches) them on your web server's filesystem. That all happens by default. You can turn this off by going to **Popup Maker** > **Settings** > **Misc** and clicking **Disable asset caching**.

Remember that *checking* this setting turns **OFF** the asset cache, and *unchecking* it turns **ON** the cache.

![file 4gGygqsyr0](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/642158b8b282ac0ba214bb1c/file-4gGygqsyr0.png)

In the screen capture above, Popup Maker's asset caching is **ON**. 

### Popup settings and styles are kept in a JS and CSS file

All your popup settings will be in the `/wp-content/uploads/pum/pum-site-scripts.js` file.

All your popup styles will be in the `/wp-content/uploads/pum/pum-site-styles.css` file.

If Popup Maker can't get to those files, it'll throw up that **warning** message.

  NOTE: This is a default yet optional performance setting. Turning this off or if it isn't working is *NOT* a critical error. Your site and popups will run fine without the cached assets. You might only notice some slowness if you have many popups on a single post or page.

### Why is this faster?

Storing settings and styles from the database to the filesystem is called *asset caching*. Put it this way. If Popup Maker didn't create and use an asset cache, a bunch of database queries would need to run every time a page with a popup loads. Imagine if you have a lot of popups on a page! 

In general, getting info from a file is more efficient than getting it from a database. This is especially true if the data (like popup settings and styles) don't change all the time.

When you turn on Popup Maker, it creates the asset cache (those 2 files we mentioned earlier). The cache gets updated any time you change popup settings and styles. So you'll always have the latest settings and styles loaded for your popups.

Let's get into the troubleshooting.

## Make sure you're running Popup Maker version 1.18.1 or greater

There was a bug we found around version 1.18.0. The bug displayed that filesystem notification even if there wasn't a problem. Upgrading to v1.18.1 ( [released 8 March 2023](https://github.com/PopupMaker/Popup-Maker/blob/master/CHANGELOG.md#v1181---03082023)) will fix it.

If the notification goes away after upgrading, there's nothing more to see here. You're done. 

If nothing happened and you still see the notification, carry on reading.

## Trying to create the cache again doesn't work

Underneath the admin notification message, you'll see 3 links.

![file KPQzU5MLzT](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/64203b0d1b1cd16ee8afa08e/file-KPQzU5MLzT.png)

If you clicked on **Try to create cache again** and the notification message went away, awesome job. You're done.

If that link didn't do anything (the notification is still there), it's time to check for:

1. Errors under **Popup Maker** > **Tools** > **Error Log**.
2. The `pum-site-scripts.js` and `pum-site-styles.css` files on your web server.
3. Wrong filesystem permissions for the `wp-content` and `uploads` directories.
4. Mischief from a security plugin (i.e., firewall) that blocks [HTTP connections](https://en.wikipedia.org/wiki/HTTP) to the files in `/wp-content/uploads/pum/`.

Let's go through each one.

## 1) Check for errors in the Popup Maker error log

Checking Popup Maker's built-in error log can give you clues about what's happening.

Go to  **Popup Maker** > **Tools** > **Error Log**.

### Debug logging is disabled

Seeing "Debug logging is disabled." in the log and nothing else under it could mean a filesystem permissions problem. Jump down to the [filesystem permissions section](#check-for-wrong-filesystem-permissions-for-the-wp-content-and-uploads-directories) to confirm it.

![file E7PiHNOndy](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/6426710e7bf4bb61c0116899/file-E7PiHNOndy.png)

### Download the error log to share with support teams

If you see any other messages, especially about the asset cache, click **Download Error Log** and attach it when you open a support ticket. You can also share the same error log with your hosting support team if you've already reached out to them about this issue.

![file 3sSKhHa9EE](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/64267337a3236b1edbce8bc3/file-3sSKhHa9EE.png)

In the screen capture above, there was a temporary network problem that blocked Popup Maker from getting to the asset cache.

## 2) Check for the pum-site-scripts.js and pum-site-styles.css files on your web server

Before you start, you'll need a way to look at your server files. Here are 2 popular tools you can use.

- SFTP (e.g. [FileZilla](https://filezilla-project.org/))
- cPanel [File Manager](https://docs.cpanel.net/cpanel/files/file-manager/)

You can also ask your hosting team to do this check for you. Send them [the link for these instructions](#check-for-the-pum-site-scriptsjs-and-pum-site-stylescss-files-on-your-web-server).

We use the words *directory* and *folder* interchangeably. I.e., they're the same thing.

To check if the `pum-site-scripts.js` and `pum-site-styles.css` files are on your web server:

1. Open your FileZilla or File Manager.
2. Go to the folder where your WordPress is (e.g., "public" or your site name).
3. Go to **wp-content**.
4. Go to **uploads**.
5. Look for the **pum** folder.
6. If you see the **pum** folder, open it and make a screen capture of what's inside it.

Here's an example. In the screen capture below, we installed WordPress in a directory named **public**. To find our JS and CSS asset files, we go to **public** > **wp-content** > **uploads**.

![file foBwIkgN5y](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/64215076b282ac0ba214bb07/file-foBwIkgN5y.png)

In **uploads**, we open the **pum** folder.

![file](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/642150b469becd1202b9ed50/file-4x7cnQwqzC.png)

By now, you've confirmed that your asset cache files are either OK or missing.

### Don't see the pum directory or the asset files?

If you don't see a **pum** folder or the JS and CSS files: 

1. Make sure your Popup Maker asset caching is on. Go to **Popup Maker** > **Settings** > **Misc** and uncheck **Disable asset caching**.
2. [Check your web server's filesystem permissions](#check-for-wrong-filesystem-permissions-for-the-wp-content-and-uploads-directories) (read the next section).

## 3) Check for wrong filesystem permissions for the wp-content and uploads directories

This is an easy check since WordPress has a built-in tool that shows your website's [system info](https://wppopupmaker.com/docs/getting-started/popup-maker-glossary-of-terms/#system-info).

From your [/wp-admin/](https://wppopupmaker.com/docs/getting-started/popup-maker-glossary-of-terms/#admin) area, head over to **Tools** > **Site Health** > **Info**.

Scroll down to **Filesystem Permissions** and expand it. Make a screen capture of the content in that section.

In the screen capture below, our `uploads` directory is marked **Not writable**. That's a problem 😔

![file 6hguQcpZUF](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/64217a91b282ac0ba214bb36/file-6hguQcpZUF.png)

### Not writable is bad

If you see **Not writable** next to the **wp-content** or **uploads** directories, you've found the reason why you're getting the admin notification warning.

Popup Maker needs to write to the `/wp-content/uploads/` directory. If either of those directories isn't writable, Popup Maker can't create and use its default asset cache. Hence the warning.

## How do you fix the filesystem permissions problem?

The best way is to ask your hosting support team to make the **wp-content** or **uploads** directory writable for you.

If you're a techie, you can use your SFTP app or cPanel File Manager.

For SFTP, check out the official WordPress [Changing File Permissions guide](https://wordpress.org/documentation/article/changing-file-permissions/#using-an-ftp-client).

For File Manager, read the [cPanel doc](https://docs.cpanel.net/cpanel/files/file-manager/#update-file-or-folder-permissions).

## 4) Check for network mischief that's blocking HTTP connections to the files in /wp-content/uploads/pum/

If your filesystem permissions are OK and you still see the warning message, there could be a network problem. 

### One quick check

1. Bring up your [browser's dev tools](https://developer.chrome.com/docs/devtools/open/) network tab.
2. Filter on "pum".
3. Look for the JS and CSS asset files.

Here's what a healthy network tab should look like for those files.

![file LiHFgDguVG](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/64217b3d5b17ef2714cec155/file-LiHFgDguVG.png)

![file l7Sng0KG7S](https://s3.amazonaws.com/helpscout.net/docs/assets/559c68b9e4b03e788eda1692/images/64217b84e11bbe23cb6ac386/file-l7Sng0KG7S.png)

#### 200 is good

Status **200** is good. If you see anything but **200** for the asset files, there's a network issue.

## Here are some other suspects

1. **A security plugin**: Temporarily turn off your security plugin. If the warning goes away, then go through your security plugin settings. Try changing any settings or rules that block writing to the asset cache. Then, retest. At the time of writing, we know the [BulletProof Security plugin](https://wordpress.org/plugins/bulletproof-security/) will cause **405 errors**. You'll see "Cannot access cache file when tested. Status code received was: 405." in the [Popup Maker error log](#check-for-errors-in-the-popup-maker-error-log).
2. **A WAF** ([web application firewall](https://www.cloudflare.com/learning/ddos/glossary/web-application-firewall-waf/)): Check with your hosting or CDN provider to see if they have a WAF that might be blocking write access to the asset cache.
3. **A random network issue**: Ask your hosting provider if they've seen any network issues with your site.
4. **A bug**: This isn't network related, but there could always be something buggy on your site. [Give our support team a holler](https://wppopupmaker.com/support/#submit-a-support-ticket) so they can help you figure this out.
5. **Server-level restrictions**: Some hosting providers lock down file writing at the server level, beyond just folder permissions. This is common on managed WordPress hosts like WP Engine or Kinsta. Their support teams can usually sort this out quickly.
6. **PHP configuration issues**: If your server's PHP settings limit file writing (like a restrictive `open_basedir` setting), Popup Maker won't be able to create the cache files even if folder permissions look fine.
7. **A full disk**: If your server is running out of storage space, it can't write new files. Your hosting provider can check this for you.
8. **Object caching plugins**: Tools like Redis or Memcached can sometimes interfere with how WordPress writes files.
9. **A misconfigured CDN**: If your CDN is aggressively caching or rewriting URLs, it can block requests to the asset files in a way that looks like a filesystem problem.
10. **Conflicting file ownership**: On some servers, the files might be owned by a different system user than the one WordPress runs as. This is a server-level issue your host can check.

## Ask for support

Since this doc already covers the most likely culprits, if you're still stuck, your best bet is to [open a support ticket](https://wppopupmaker.com/support/#submit-a-support-ticket) with Popup Maker and loop in your hosting provider. The error log from **Popup Maker** > **Tools** > **Error Log** will be a big help for both teams.