thefitrv

I’ve applied the update.

There is still a “styles” subdirectory under divi, and now there are two zero-byte files in it.

style-dbp.min.css and style.min.css

I had previously created the second file myself, but it looks like the plugin install created the files and directory again. Is that expected behavior? Should I just leave those files and directory alone?

(I forgot to delete my own mod before applying your update.)

In any case, the rapid accumulation of 404 errors has stopped, so it seems to work.

I created the missing directory and an empty file to go in it.

This is not a permanent solution, but it has stopped the torrent of 404 errors.

Gerroald – I take issue with your reply that “bad login attempts should be considered informational, not actionable”

If you have used the feature to “hide backend” (from this very same plugin), then a bad login attempt is indeed actionable. It indicates that someone (beyond the two users who know the login slug) has defeated the “hide backend”, or your login slug is compromised. But you’ve hidden away the bad logins now, so we might not ever see this.

It’s a bit presumptuous for you to assume that you know exactly what is important to whom. Particularly when you can’t even get it right in your responses here.

What is wrong with letting users decide what they want to see?
Alternatively, if you are dead set to dumb-down the plugin, why not offer a “dummy mode” or something similar?

Ugh. I can’t believe how annoyed I am about this.
Here’s a simple use case for the logs.
Please tell me how this might be accomplished with the new stupid logs:

I review ALL of the entries in my log.
But I do not do this on a regular schedule.
Entries should remain in the log until I review them.
After that, I should not have to review them again – and I shouldn’t have to write down the date/time I last reviewed logs on a post-it note to do this.

I don’t know where this developer learned English, but the last time I checked, removing features is not generally referred to as an “enhancement”. That’s like saying that taxes are “salary enhancements”.

Hey – here’s an idea. It’s a log! Let the user decide what to do with it!
This includes clearing it.
This includes classifying the logs (Extra clicks now to see all events).
Don’t go all facebook on it and decide what I need to see and how long I need to see it.
Maybe you can have a ‘dummy mode’ for people who don’t know what a log is or who you don’t want to scare.
But for everyone on this thread and all the other non-dummy users out there… bring back the clear log button.
Reverting to 6.8.1 until these deficiencies are resolved.

Well, I got brave and tried it again.
It seems to be working now for me, so I’m guessing it was the cloudflare plugin and its rewriting.
For the record, these are the things I did between first having the problem and now:
1. Updated to php 5.6
2. Updated Cloudflare plugin to 1.3.20
3. Updated to WordPress 4.4.1

Clearly, this won’t be the solution for everyone. But it’s what I did and my back end “featured images” are working consistently now.

Another question for those having the issue.
Are you using Cloudflare and the Cloudflare plugin?
There is a “protocol rewriting” option and I’m wondering if it could be part of the problem.

Shot in the dark here, but I was also experiencing a problem with another plugin. Turns out that was a PHP version issue.

For those having the problem, what PHP version are you using? Is anyone using 5.6?

Logged support ticket with cloudflare. Included log.

Has anyone tried the new 4.4.1 to see if it still has the problem?
(I’m not too anxious to be the first.)

Floregonian – thanks for that. I had it on my list to try sdk’s code. Won’t bother now.

Hopefully, this gets fixed.

Thanks, Scott. Yes, some of them (and consistently the same ones) work fine with https through the back end, and some (also consistently the same) do not.

Hopefully, this gets fixed soon. I generally do try to keep current, and it’s been a pretty smooth ride thus far.

Downgraded to 4.3.1 and I can now see all the featured images.

When will the 4.4 cake be finished baking?

Interesting. If you’ve got something already, I’d certainly be willing to have a look and maybe test it out.

I’ll email you, rather than share details here.

Well, that would certainly be easier…
Although I’d still get the 404s when I made changes to .js or .css that required an AO cache rebuild. Those changes are much less frequent though.

Maybe I’ll do both?

Either way, thanks for the tips! I’ve got plenty to work with now.