Leon
Forum Replies Created
-
Hello, thanks for the quick response!
Unfortunately I cannot paste screenshots. The post editor shows an infinite loading spinner when I try to do so. Anyway, these are my Honeypot settings:- Enable Honeypot App: ✅
- Store Honeypot Value: ✅
- Global Placeholder: blank
- Accessibility Message: blank
- Use Standard Autocomplete Value: ❌
- Move Inline CSS: ✅
though I also received spam with this turned off. It was the first thing that I tried. - Disable Accessibility Label: ❌
- Enable Time Check: ✅
- Time Check Value: 4 Seconds
This is my contact form’s code:
<label for="your-name">Ihr Name</label>
[text* your-name id:your-name autocomplete:name]
[honeypot your-lastname]
<label for="your-email">Ihre E-Mail-Adresse</label>
[email* your-email id:your-email autocomplete:email]
[honeypot your-company][honeypot your-website][hidden your-marketing-consent "on"]
[honeypot your-message]
[submit "Abonnieren"]I’ve used my browser’s developer tools to fill in the hidden honeypot fields.
Forum: Plugins
In reply to: [Shariff Wrapper] Replace Twitter with XThey do have this page, but admittedly it’s not much. Just a few downloads and no actual guidelines.
I understand your decision though. Elon is really putting his heart into making this as chaotic as possible.
Forum: Plugins
In reply to: [Contact Form 7] editing pages with cf7 element in editor crashes editorI was able to narrow it down to the Categories and Tags sections of the sidebar, and also found a workaround in the process that doesn’t involve downgrading the plugin.
While in the editor, click on the three dots in the upper right and then on “Preferences”. Go to “Panels” and make sure both “Categories” and “Tags” are disabled. The switches will only appear if the page type currently being edited has categories and tags. You will still be able to change categories and tags using the Quick Edit feature in the post list.
Forum: Plugins
In reply to: [Contact Form 7] editing pages with cf7 element in editor crashes editorAre there any news on this?
I have since made a few discoveries:- This only started to happen with CF7 5.7. Version 5.6.4 and earlier work fine.
- For the error to happen, a CF7 block with a form selected must already be present in the content when the editor is loaded. If I add a CF7 block after the editor was loaded, no issues arise until I reload the editor.
- If no form is selected in the CF7 block’s dropdown, or if the form that had been selected has since been deleted, no error occurs.
- It doesn’t have to be a CF7 block; adding a form using a simple CF7 shortcode causes the same problems.
- At least in my case, the error only occurs when trying to edit a post that belongs to a custom post type created with Custom Post Type UI. Normal posts and pages can be edited just fine.
- It takes a while for the error to show. Everything seems to load fine at first. The error comes up shortly after the red “Move to trash” button appears and when the metaboxes appear.
- The error only happens if the right sidebar is visible. If I’m quick enough to close it before the error shows up or if it was already closed, or if I shrink my browser window down to the mobile layout, everything works fine. If I open the sidebar or increase the window size again, the error pops up immediately when the sidebar would become visible.
- The error is only caused on the first tab of the sidebar (labelled “Page”, “Post”, or after whatever type of content is currently being edited). If the “Block” tab is open, no error happens. The error shows up immediately when I switch to the first tab.
That being said, I still wasn’t able to recreate the error from a fresh WP installation.
Forum: Plugins
In reply to: [Contact Form 7] editing pages with cf7 element in editor crashes editorI’m having this issue as well. Trying to edit a page or post containing a Contact Form 7 block crashes the editor after a few seconds. The JS console says that
l.useSelect(...)is undefined. Frontend works fine. Disabling the visual editor doesn’t help. Firefox’s network inspector doesn’t show any unsuccessful requests. No error occurs if the block’s dropdown is left blank.Oddly enough, this doesn’t happen on all pages. I’m still trying to figure out why that is.
Unfortunately, I haven’t been able to put a MWE together and I obviously can’t give you access to my company’s backend, but I’ll be happily to provide more information if requested.