happyallthetime

Thank you, allrude, shinerweb, chemaz, & all of you who left messages here;

allrude`s solution would seem to resolve the issue of the browser finding nothing to load at the requested location, not that I understand what a gmaps.min.js file is yet.

In my case my page is taking 15+ seconds to load, & that is why I came to find the error in the DevTools:Console pane, so it is a little more troubling than just a warning, as it is slowing down load time to the first interactive moment of the designated page.

In my case, the error is:
“DevTools failed to load SourceMap: Could not load content for https://example.com/wp-content/themes/divi/js/custom.unified.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE”

I am not using a google map module on my Divi page, so I`m wondering why the page is trying to load something that appears to be used to create a google map on the page, if I am to believe that referencing a gmaps.min.js file will fix it.

Also, allrude provided the code:
`{
“version”: 1,
“mappings”: “”,
“sources”: [],
“names”: [],
“file”: “gmaps.min.js”
}

But is that all there is to it, just reference a gmaps.min.js file, or do I need to also place a file named gmaps.min.js in the same folder. Can I use any gmaps.min.js file I find at GitHub? I have already located 2 there, but I so far have no idea what all of the coding in them does, or if I need them at all.

I also plan to submit a ticket to Elegant Themes, as I would like to see the issue resolved by them rather than a workaround that might be erased every time the Theme is updated, or do I need to figure out how to do all of this in my Child Theme? Either wayI want to make sure they know about the issue.

Thank you.

• This reply was modified 4 years, 1 month ago by happyallthetime.
• This reply was modified 4 years, 1 month ago by happyallthetime.
• This reply was modified 4 years, 1 month ago by happyallthetime.
• This reply was modified 4 years, 1 month ago by happyallthetime.
• This reply was modified 4 years, 1 month ago by happyallthetime.

Hi, @wfgerald;

Please pardon my learning curve, but I have a few questions:

1) How does one determine that the error is continuing? I found a different E_COMPILE_ERROR thread here concerning UpdraftPlus, & in that case the error was repeating once every 3 or 4 days for a couple of weeks, until the guy exhausted the other suggestions for resolving the the problem & finally changed hosting companies, which did fix his issue.

2) How often should I be seeing this error turn up on a specific plugin file line # if it is a continuing error? Can I force it to present itself somehow as a test? I don`t currently know for sure what caused it to appear the first & only time it showed about a week ago now.

3) If WordPress notified me about it just one time, does that mean that my website likely got a “hit,” meaning either a legitimate visitor showed up, during the update of the particular plugin, or that an malefic attacker tried to login while Wordfence specifically was being updated, & so maybe the Plugin Update itself was not corrupted during delivery? (I guess what I`m asking at the moment is whether you were answering in general what might cause an E_COMPILE_ERROR on a WordPress site, or if your response refers specifically to an E_COMPILE_ERROR concerning the Wordfence plugin?).

My error, by the way:

Error Details: An error of type E_COMPILE_ERROR was caused in line 3 of the file:
…/wp-content/plugins/wordfence/lib/wordfenceClass.php.
Error message: require_once(): Failed opening required
‘…/wp-content/plugins/wordfence/lib/wfScanEngine.php’
(include_path=’.:/usr/lib/php:/usr/local/lib/php’)

I didn`t see anything odd on Line 3 or other line of the wordfenceClass.php file, nor anything unexpected in wfScanEngine.php, which is definitely there in the lib folder.

4) How does one reinstall a fresh copy of Wordfence. I found an article at
https://docs.wordfence.com/en/I%27d_like_to_reinstall_Wordfence_completely.html,
which tells how to start over from scratch, settings & all, but can I just download the free Wordfence plugin again via the New Plugin feature of WP & cause the current Wordfence plugin to be safely overwritten? Should I disable the current Wordfence plugin first? Or, if I tried loading a new install of Wordfence, would I end up with two Wordfence plugins installed, one titled Wordfence1 in the plugins folder. Or should I just omit checking the Delete Tables & Data box as described in the article I already found & mentioned above? I haven`t had any luck finding a more specific answer so far, but your response on this thread suggests it should be easy even for newbies like me to do a fresh reinstall.

Thanks for your time & patience.

Hi, @carpentiertech001;
Just to clarify, when you say that you “Tried to push,” do you mean that you had already cloned the live site to create a staging/test site, made changes to the staging site & then tried to push the successfully updated staging site to overwrite the live site?

If so, since I was seeing the “Watch out” message right after I activated the free version, before I even cloned my live site, I would infer that you had not seen the message before you cloned your live site, that you updated the WP Staging plugin after you had already created your staging site, & that because being able to “push” the test site to replace the live site is a Premium feature, that you are using WP Staging Pro, which would indicate that this Warning Message issue affects both the free version & the premium version, & that the issue was caused recently by something introduced in the last WP Staging updates, or even a newly uploaded or recently updated other plugin which may be conflicting with either the WP Staging plugin`s ability to accurately read compatibility with WP 5.2.2, since WP Staging has indicated that the most recent plugin update is compatible with WP 5.2.2, but that their test with WP 5.2.2 did not necessarily include any other plugins in the build or diagnostic.

Thank you for your time on this.
Have you already tried deactivating the other plugins? I haven`t yet. Also, is the message appearing on the live site & on the staging site? Or have I inferred incorrectly & too much?

Thank you for your time on this.

• This reply was modified 5 years, 5 months ago by happyallthetime. Reason: content formatting issue due to contraction apostrophes

Sorry, not at the blog, it was an announcement under “Support” here that hade the new changes listed.

Wordfence Changelog shows 6.3.17 as the most recent update level, though I got there via the link under the Wordfence 6.3.18 details link on my plugins page. I found what had actually been updated by going to Wordfence & looking at their notice in the blog.

Just thought I`d let someone know.
Sincerely,
happyallthetime