Carl Gross

Thanks very much @tomcobbley !

I’m not sure I follow.

I should be able to implement any custom code required. I just wanted one final confirmation that custom code would be required to both customize the content of this section and completely hide this section, or if there was perhaps some UI option to hide the section. The former is probably true, but I just thought I’d ask since we were here.

OK thanks for that info. Let me ask a follow-up question about the free version.

With the free version, in order to edit, or completely hide this section, I’ll need to use custom code. Am I understanding correctly?

Hi Gary,

Sorry for the late reply.

Thanks for the suggestion. Even though it’s not explicitly listed in my short list of issues/enhancements (see here), emailing users is on the longer, unpublished list that I keep.

For the past few years I haven’t had much time to devote to the plugin. But recently that has changed, and I plan to get back on it. I’ll see about adding this to the list. Realistically though it may not be for another couple months at the earliest. If/When that occurs, I will plan to notify you.

You’re welcome! Thank you very much for the review.

>> However, you can update the plugin to the latest version where We have made changes in the recent versions of the plugin to make the user experience better and give more flexibility in customizing the maintenance page, as you can now use Gutenberg editor or a page builder to easily customize the page and select a pre-created design or create your new custom one. You can also add different social site icons and choose their size according to your own preference.

OK great, thanks. I did just that and it did the trick, thanks.

We can consider this resolved.

Hello. These 404 errors should occur for every plugin installed on your site that is *not* found in the WordPress plugin repo.

>> How do I fix this or turn off the json files?

Unfortunately at this time there is no way to do that. I acknowledge it is not best practice–what should occur is that these network calls should fail without the jarring red 404 errors you’re seeing. It’s been on my to-do list, and I’ll see if I can carve out time for it. But unfortunately I don’t have too much time these days to work on the plugin :-/

@galanos OK thanks for that link. It does indeed answer my question.

Hey thanks very much for the message. These are definitely great suggestions. And indeed, they are already on the plugin’s to-do list. I unfortunately don’t have too much time to devote to adding new features these days :-/ If you or anyone you know has the time to implement these features, I’d be happy to have some contributions.

Yep. Also should note that the article indicates a proof of concept of the exploit will be released May 12. So I was hoping to be able to update the plugin before then. The plugin is still offline, so I might have to go with an alternate strategy for now.

Update: I found the cause of the issue. It was due to custom code that *I* had added in my child theme–code to defer the loading of scripts. Geesh.

So sorry about that–I very much appreciate your time. Let’s consider this resolved.

Sorry for the delay. I just tested the site, with all plugins deactivated, except for Hummingbird. The issue is not present.

I also tested the site in which all plugins were activated, except Hummingbird. The issue is still present.

During the tests, my usual theme (Spacious) was active, and I was sure to carry out hard refreshes.

Thoughts?

Haven’t we already ruled that out as a culprit?

>> I would advise you to focus on the plugin before reporting to the theme author.

By ‘plugin’ you mean CF7, correct?

OK I just switched to the default theme (Twenty Twenty), and had only CF7 activated. The issue went away. So I guess my theme is the culprit? If so, what do I do now? Specifically, if I bring this up with theme support, I’m sure you know that they will point to the CF7 plugin and say, “The bug is in that plugin.” If they say that, what would be my best reply? Maybe I don’t mention your plugin just yet, and tell them only, “The issue occurs when I activate your theme.”

• This reply was modified 4 years ago by Carl Gross.