BothHands

Hello again, Dinesh,

This is probably more than you’re willing to consider. A lengthy (and frustrating) interaction with Divi AI chat support yielded the following four items:

ITEM 1
“I apologize, but I don’t have specific information about integrating the WP Armour plugin with the Divi Opt-in Module. Divi doesn’t have built-in hooks or actions specifically for this integration.” (but WP Armour *DOES* work with the Divi Contact Module…)

ITEM 2
“We understand your interest in integrating WP Armour with the Divi Opt-in Module. However, we don’t directly assist third-party plugin developers with integrations. Here’s what you can do:
a) Contact the WP Armour plugin developer directly. They’re best positioned to work on integrating their plugin with Divi modules.
b) If the developer identifies specific issues on our end, please let us know their findings so we can review and potentially address them.”

ITEM 3
“While we don’t have specific hooks for the Divi Opt-in Module, there are some general JavaScript hooks that might be helpful for the WP Armour developer. The ‘{module_type}.css.selector’ and ‘{module_type}.processed.css.selector’ filters can be used to modify module selectors, which could potentially be useful for integration.

However, for more detailed assistance with custom module development, we recommend joining our Developer team’s Slack channel. There, you can ask specific questions about integrating third-party plugins with Divi modules, and our dev team can provide more tailored guidance.”

To join the Slack group, please fill out the form at the provided link. Once you receive an invitation, you’ll be able to discuss your integration needs directly with our development team.

ITEM 4
ITEM 3 above referenced this link: Divi Builder Javascript Hooks

To put this in context, Divi is not serious about their own modules. For years their “updates” have focused on silly new features, while failing to repair/improve glitchy fundamental features. Case in point: in the course of today’s inquiry, the AI support bot suggested I use WPForms contact and opt-in forms instead of Divi’s own modules. That SUX.

I don’t expect you to tackle this, but I’ll be glad if you do. And so will other Divi users. Let me know if I can be of further assistance.
Tom

Thank you, Darshana. Yes, it helps a lot. I appreciate your quick, considerate reply. I must have missed those checkboxes during setup.

Duh =]

Thank you, Nawawi, for your prompt reply. I have looked through your FAQ and cannot answer this question: When I “Disable Object Cache” as you advise, all pages of the website do load/display properly. Does “Disable Object Cache” bypass the Docket Cache? Or does it simply bypass my particular problem? I want the page load benefits, so I do not wish to bypass or turn off your plugin. Can you please explain what “Disable Object Cache” does?

Also, I had disussion with my hosting provider today. My website is small and simple; their server is certainly capable of serving up my pages without difficulty. But the following information may be useful to you:

The iPhone that is experiencing the problems outlined above is an older model, an iPhone 7. Its iOS is up-to-date, but for that phone, the iOS is 15.7.7. Not 16.x.x as used by newer phones. And I assume the Safari browser for 15.7.7 is lesser than is Safari for 16.x.x. My hosting provider’s Support Team tested my website (with your Docket Cache plugin installed) on various browsers, operating systems and hardware platforms, and they report NO problems such as I describe (they did not test on an iPhone 7, with its older version of Safari).

So the issue I have been experiencing might only pertain to OLDER PHONES running lesser operating systems, with lesser/older Safari browser versions. I hope this information/idea might benefit you and your development. If this really is the problem, perhaps you can modify your excellent plugin to address/overcome it. My pages load MUCH faster on Windows desktop, with no issues at all.
Thank you,
Tom

Hey, Rolf ==

Yeah, I hear you. =]

Having struggled for months to overcome the relentless quirks and counter-intuitive aspects of Divi–due in part to the development team’s penchant for fancy new features THAT DON’T WORK RIGHT(!)–I am less and less a Divi fan. On the other hand, the design flexibility/versatility is difficult to find in another theme.

I certainly understand your POV. Thanks for the reply.

Thanks, t-p.

On the off chance that anyone here might find this useful:

I’m rebuilding my website from scratch, and noticed the following last night after posting here:

It appears the Divi theme is the culprit. Divi provides a really helpful “Portability” feature that enables exporting pages, posts, theme option settings, etc as .JSON files. Those files can then be imported into new pages, posts, etc.

It appears that either the Portability EXPORT or IMPORT function is rewriting my image locations, automatically modifying the URL so it points to the WordPress Media Library. Whatever is at work here is also copying each image file to the WP Media Library.

Strange but true…

Thanks. I’ll modify the file in public_html.

And thanks for the additional link.

As I understand it, placing that Options -Indexes command in a .htaccess file protects THAT directory and all its subdirectories from directory listing.

I see. So I’ll have to disable those two options. Too bad, as that would otherwise be a useful indicator of trouble afoot.

Just a suggestion: The details page that explains WF Advanced Options is a very helpful resource. Perhaps you will include instructions for the two options in question, stating clearly that they do not work for DYNAMIC IP addresses

I think it’s very common for administrators of small websites to have dynamic IP addresses. STATIC IPs are usually optional and are fairly expensive.

In any event, thanks for your assistance.