Ben1098765

Following up on this for anyone that it may assist.

Our IIS server (Plesk) had placed its error rules before the WordPress rewrite rules within the web.config file.

So by moving the <httpErrors> block after the <rewrite> block, the plugin was able to do its thing before being intercepted by the 404 page.

Many thanks to Emre – your patience and help was hugely appreciated! ??

Hi Emre, many thanks for the response. Sorry I didn’t get back to you, the problem completely fell off my radar, but it is now back on, and we do need to speed up the homepage.

So I’m pretty certain it’s not a permissions issue, as I can delete the /cache/ folder and WPFC then recreates the whole folder when requested for the other pages.

Part of my original post was misleading as I’d forgotten that I’d actually excluded the homepage in WPFC because of the problems it was causing. In fact, the index.html file does get created, but it gives me a 404.

Interestingly, when I rename the cached homepage file to default.html, the page works, but only once, as WPFC then creates another index.html file in the /all/ folder which supersedes default.html in the DefaultDocument order.

It’s weird because index.html works fine in all the subfolders, just not the root /cache/all/ folder. If WPFC were to output the cached files as default.html, then I’m sure it would work.

Any ideas?

Thanks again in advance

Ben

Smashing, that seems to have worked.

Thanks Nadia!

Brilliant, thanks Nadia! ??

Looks like the format of the attachment’s remove button has changed in 4.3.

EML Disabled (Working in 4.3):
<button type=”button” class=”button-link attachment-close media-modal-icon”><span class=”screen-reader-text”>Remove</span></button>

EML Enabled (Not working in 4.3):

I presume EML replaces the core button with its own code; unfortunately that now prevents the core gallery functionality from working.

I’m using the PRO version, by the way.

A bit more information: this only seems to be an issue after updating to WordPress 4.3.

Thanks

Ben

+1 for this feature. From my point of view, it’s the one thing missing from making it perfect for managing large libraries.

Great work so far though – really looking forward to the update (hoping it comes soon!)

??

It’s good to know that the taxonomies aren’t being registered, so there’s no direct impact on my project.

As such it’s no inconvenience at all, David. I can happily turn a blind eye to that ??

Thanks for getting back to me with such a detailed explanation!