Forum Replies Created
Hmm, okay, thanks…
Not sure how these could be related, but needed a solution fast, so, switched plugins… :-/
Thanks for the prompt reply, Joy!
The error message I provided is indeed from the Plugins page, but the Shield plugin was definitely disabled for some time before I entered that page…
In fact, the reason I opened that page was because I was seeing security issue I expected Shield to catch, went in to check its settings, and found that message…
And this has happened several times, where perhaps the update process has caused a plugin to break, but if you do not go back to that page, you wouldn’t notice it…
Just saying, it would be nice, if WP, while going about its normal business, saw a plugin suddenly deactivated because of an error, would notify the site admin, similarly to how the Recovery Mode you mentioned notifies a site admin…
Sorry, for some reason I didn’t get your message, but yes, happy to help in any way I can!
I also filed two other bugs:
Any traction on those? Anything I can help with there?
I am also a developer and would be willing to help out if possible/desired.
This issue appears to be related to some CSS from the plugin, though I would say it is more likely a Firefox bug…
white-space: nowrap;is causing the line-break to visually convert to a space, but when I edit that
textareaas HTML, the URLs are in fact on separate lines, and blocking that line of CSS makes it visually correct…
Cannot attach images to this message, so here is a link to a screengrab:
On the outside chance anyone else encounters this, it took a fair bit of tracking to find the culprit, but it boils down to the theme, maybe justifiably, removing empty paragraph tags, I guess trying to keep things clean?
I will try contacting the theme developer to ask if they can remove this in the future (though unlikely), but in the short-term, I have added a script to my template that adds a
<p role="status" aria-live="polite" aria-atomic="true"></p>so it is no longer empty, so the theme script no longer deletes it…
Okay, apologies, this is NOT related to any caching plugin, but apparently the theme, and I was not seeing it earlier because, without a caching plugin, the error only appears after clicking
The difference appears to be the change from v5.3.2’s:
$( '[role="status"]', $response ).html( data.message );
As 5.3.2 uses a comma in the selector, it allows for
[role="status"]to be missing, whereas 5.4 requires
[role="status"]to be within
And for some reason, when using our theme, the
<p role="status" aria-live="polite" aria-atomic="true"></p>element is missing in the markup.
If you have any idea what might cause this, I would love to hear it, but if not, I will begin that investigation, and again, my apologies for wasting your time…
Strictly speaking, yes, but also, why would a cached page break the plugin’s JS?
Also, same error when using WP Super Cache, which is another pretty common page caching plugin.
So far, WP Fastest Cache seems to be error free, will continue with that one for now.
Correction: WP Fastest Cache also throws the error, just not on page load as the other two do, but it does throw the same error once the “SUBMIT” button is clicked…
This is an issue, and I realize it is a conflict between plugins, but when one plugin starts conflicting with multiple plugins, the first plugin has to re-examined…
I hope I have provided enough debugging information to be helpful, but if not, happy to help some more.
- This reply was modified 10 months, 3 weeks ago by Aaron T. Grogg. Reason: Turns out WP Fastest Cache also breaks
FYI, I have also tested the same installation, Automotive theme activated, all plugins activated, but using CF7 v.5.3.2, with page caching activated, and I do NOT get this error message:
Thanks for the reply.
Theme: Automotive By Theme Suite, Version: 11.9.8
Per standard practice…
- Deactivated all plugins and reverted to Twenty Twenty-One theme, and error message disappeared.
- Gradually restored all plugins, still no error.
- Restored Automotive theme, still no error.
- Reactivated page caching (via WP-Optimize), error returned.
- Deactivated page caching, no error.
- Reactivated page caching again, error returned.
Error occurs in:
On line 230 (via Pretty Print):
e.wpcf7.parent.querySelector('.screen-reader-response [role="status"]').innerText = '',
innerTextthrows an error.
For some reason, when page caching is turned off, this line is never called (breakpoint never reached)…
- This reply was modified 10 months, 3 weeks ago by Aaron T. Grogg.
Unfortunately this site is still under construction, so you will not be able to see the form in action…
As I don’t see a way to attach any files here, here is the exported form data:
And here is the page source for a test page that includes only this form:
The test page source says:
<html lang="de-DE"> <head> <meta charset="utf-8">
I have also output the Info tab from WP’s Health Check & Troubleshooting plugin; here is a semi-cleansed version, in case that might help:
Also, I noticed in the page source that the encoding error is already in the HTML:
And finally, although the form only appears in the page once, curious why the
runForminatorFrontfunction is defined twice, beginning first on line 1297 (above) and then again on line 2149…
Appreciate the help,
- This reply was modified 1 year, 8 months ago by Aaron T. Grogg. Reason: Forgot you cannot see site as it is in construction mode
Happy to send the XML, don’t see a way to attach it here.
How can I send it?
As there is no way to “+1”, I will add a comment.
This is critical to our current project.
Is there anything that can be done to help?
All the best,
PS: I know this is a different topic, but it is also related…
I have also tried “Overriding templates via a theme” from this page:
But that also did nothing; my template was not used, so my change was not reflected…
@tgoeg: Fantastic work!
The error I see in the Dev Console says:
“Uncaught TypeError: $(…).matchHeight is not a function”
Which points to line 34 in your scripts.js file:
The problem seems to be that
matchHeightis not a jQuery function…
And no function by that name is being added anywhere else…
Any idea where this should be coming from?
I do see this plugin:
Not sure if adding it would fix the problem of not…
PS: “I am somehow at my wits end”… Welcome to the wonderful world of web development! And then when something suddenly starts working, all that pain disappears and the world will be wonderful again… 😉