PopupMaker is unable to create & save cached assets for your popup styling

For anyone else running DIVI… So far, latest release of PUM is returning the same “Popup Maker detected an issue with your file system’s ability…” error message on EVERY Divi site I have it installed on (and updated) regardless of host – looking forward to a resolution

Hi @klynam

Thank you for this information.

The investigation is ongoing, and we’ll update this thread once our team has a solution.

Thank you for your patience.

Plus 1, same issue as everyone else is describing. It’s been a week, any updates?

Hi @lookwhoo

We’ve asked for a follow-up about this issue.

We’ll update this thread once we have new information.

Thank you for your kind understanding.

While this issue is waiting to be resolved, If I choose “Keep current method”, will I be able to set up cache when a fix is released? Thanx

I know you’re already working on a fix, but in case it’s helpful for your developers to have as much info as possible, I have the same problem since the last update to PopupMaker ver. 1.18.0, my WP version is 6.1.1, database is MySQL 5.7, and PHP version is 8.0.

After reading a few more Posts above, I thought I’d add this:

I do not use page builders like Divi, but I do use the Classic Editor plugin (all of my content writers just hate the blocks editor), maybe that’s a helpful clue too.

• This reply was modified 1 year, 9 months ago by TrishaM.

Hi @newfignewton

Thank you for joining the thread.

We don’t have information for that. On our tests, the old popups and newly created popups are not affected with that message.

Let’s wait for our team to finish their investigation, and release a fix.

@trisham thank you for this information. The issue also happens when just Popup Maker is the only active plugin.

We’ll update this thread once we have new information.

Thank you all for your patience.

I’ve tracked down the issue to classes/AssetCache.php, line 125:

if ( true !== get_option( 'pum_files_writeable', true ) ) {

The problem is that the option in the DB is set to 1 instead of true, which is false when compared with !==.

I fixed it by running wp eval "update_option('pum_files_writeable', true);" in the command line, but the devs should probably try to find out why it was set to 1 in the first place.

Cheers,
Vinny

Hi @usestrict

Thank you for looking into the issue

We’ve passed this information to our team.

We’ll update this thread for a possible fix.

Thank you!

Hi everyone!

Our team have a fix for the cached assets notification. Here’s the link if you’d like to learn more about the fix.

https://github.com/PopupMaker/Popup-Maker/commit/95f21ec308cab06ee9054278625d77bcbdfcdac5#diff-e7811066f05647cffa94a0a5fa8ba3d1746a249a90ea746e7a96a9af229a7e86R133

We will release the new version soon, including the other fixes.

Let us know if you have questions.

Hi everyone!

Popup Maker v1.18.1 is now available. Can you check your WordPress > Updates and update the plugin?

We’ll mark this as resolved, and feel free to create a new thread if you have any other questions.