Ryan Mitchell

Hi Dan,

That ?30441601 at the end of the file path is a query string (usually a “cache buster”). We don’t add that in our plugin, so it’s almost certainly being tacked on by a performance or caching tool on your site.

Plugins like WP Rocket, Autoptimize, LiteSpeed Cache, or even a service like Cloudflare often rewrite asset URLs like this to manage browser caching.

The 404s usually happen when a caching plugin is still serving an old, cached CSS file that points to a query string or path that no longer exists on the server.

A quick fix is usually to:

• Clear all your site, server, and CDN caches.
• Hit the “Purge/Regenerate CSS” option in your optimization plugin if it has one.

Please give that a shot and let us know if those 404s keep popping up in your logs.

Hi Dan,

Thank you for bringing this to our attention! We’ve identified and fixed the issue, and the correction will be included in the next plugin update.

Thanks again!

Hi Dan,

If you archived the author using the setting on the author’s profile page, you can unarchive them simply by going back to that same profile page and unchecking the “Archive author” option. No direct database change is needed. Could you please try this?

Please let us know.

Hi @whanklee,

Thank you for reaching out and reporting this issue. We’ve identified a possible cause and would like your help confirming it.

Could you please follow these quick steps?

1. Go to Authors > Tools in your WordPress admin.
2. Locate the Custom PHP box.
3. Enter the following line of code:

add_filter( '_authorship/get_user_by/delete_cache', '__return_false' );

1. Save your changes and check if the issue is resolved.

Let us know how it goes—we’ll be here to help either way!

Thanks,

The Molongui Support Team

Hi @ahochberg,

We’ve already responded to your other support ticket on this topic but haven’t heard back, so I’m pasting our reply here for reference:

It appears you are running an outdated version of our Pro plugin, which is not compatible with the latest version of the free plugin.

To resolve this, please update the Pro plugin to the latest version. If you’re unable to update the Pro plugin, you can also revert the free plugin to the version you were using before the update.

Let us know if you need any further assistance.

Hi @dreadsupp,

We’ve reproduced and fixed the issue you reported. A Pro plugin update (1.8.15) addressing this will be released soon.

Once the update is available, please install it and let us know if the issue is resolved on your end.

Thank you for bringing this to our attention—and for being such a great supporter of our plugin!

We’re marking this ticket as resolved for now, but feel free to reopen it if the issue persists after updating.

Thanks again!

Best regards,
The Molongui Support Team

We hope the issue was just a glitch and everything is working fine now. Since we haven’t heard back from you, we’ll be closing this ticket for now.

If you still need any assistance or have additional questions, please don’t hesitate to reopen this ticket or create a new one. We’re happy to help!