BothHands

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

Duh =]

Sorry. Last question.
Overview tab > Object Cache Drop-In > DISABLE OBJECT CACHE

Does selecting ‘DISABLE OBJECT CACHE’ disable the *entire* plugin?
Same as Deactivate the plugin on the ‘Plugins’ page?

Please advise. If this suggested option *disables the entire plugin* it would be better for me to simply Delete the plugin from the website.

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

Additional observation:
When the error message appears, selecting the Safari “back” button (<) typically displays the page. So the page does not load on the first attempt, but is likely to load on the second attempt.

• This reply was modified 1 year, 4 months ago by BothHands.

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.

I wish I could say it truly is worked out.

The Divi support rep claims the bizarre image file relocation/redirection is the fault of WordPress and he suggests I employ a plugin to correct all affected URLs.

I disagreed and advised him of your earlier comments. I suggested he not only double-check his source for that statement, but also enlighten me as to whatever further information he turns up…

Hmmmm. The Ol’ Blame Game. Same as it ever was… =]

• This reply was modified 7 years, 1 month ago by BothHands.

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, t-p. I’m glad to know WordPress is not inflicting this on me. =]

I think WP would like for every user to employ the Media Library, and I can see why, but it doesn’t suit everyone’s needs.

And thanks, I’ve already submitted an inquiry with the theme maker.

Deactivating plugins won’t help much because I never know when this weirdness will happen next. Some factor is causing it, but I have no buh-luddy idea what… It might happen tomorrow, or not for another three weeks.

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.

Thanks, Keith. Actually I had already consulted the link you provide. It doesn’t clarify the issue at hand. And in this case, there need to be two .htaccess files and two index.php files (if I understand correctly).

The pair must reside in the subdirectory AND in the root.

See this article:
https://premium.wpmudev.org/blog/install-wordpress-subdirectory/

• This reply was modified 7 years, 1 month ago by BothHands.
• This reply was modified 7 years, 1 month ago by BothHands.
• This reply was modified 7 years, 1 month ago by BothHands.

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.

Thanks for your reply. I followed your instructions. All logins and logouts are me from the same location, but my IP is NOT a static IP. It changes frequently – several times each day, I think. I see eight or ten IP addresses represented in about 7 days of traffic.

BOTH settings are selected (per your instructions) but I continue to receive notifications whenever I login to the site. I log in from one location only, so the notifications should not be generated.

My WordPress site is installed in a SUBDIRECTORY.
For example: public_html/wordpress

Might this be the cause of the problem?

I have identical .htaccess files in the root and in the wordpress subdirectory. Would a specific modification of the Wordfence code resolve this?

• This reply was modified 7 years, 2 months ago by BothHands.

Thanks. And thanks for the warning. In fact, I do want the entire site to be updated/restored.

UpdraftPlus has done an excellent job of backing up and restoring my localhost work. I’m glad I can continue to rely on it now that I’m (finally) publishing online.

BOTH settings are enabled per your advice above. There should be NO notifications when I login (I login only from one computer). BUT…Wordfence IS sending notification when I log in.

Please take another look at this conversation and tell me how to set options so I only receive notification/alert when someone tries to login as Admin from some other location or device.

Thanks

• This reply was modified 7 years, 2 months ago by BothHands.