michaelbgood
Forum Replies Created
-
UPDATE 2: this appears to be a conflict with perfmatters. When I deactivate the plugin, the problem goes away. Thanks!
Follow-up: i turned on php debugging and got these on the page with the form:
Deprecated: Return type of Groundhogg\Form\Posted_Data::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/staging38.construction-english.com/public_html/wp-content/plugins/groundhogg/includes/form/form-v2.php on line 2048
Deprecated: Return type of Groundhogg\Form\Posted_Data::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/staging38.construction-english.com/public_html/wp-content/plugins/groundhogg/includes/form/form-v2.php on line 2052
Deprecated: Return type of Groundhogg\Form\Posted_Data::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/staging38.construction-english.com/public_html/wp-content/plugins/groundhogg/includes/form/form-v2.php on line 2056
Deprecated: Return type of Groundhogg\Form\Posted_Data::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/staging38.construction-english.com/public_html/wp-content/plugins/groundhogg/includes/form/form-v2.php on line 2060
Deprecated: Return type of Groundhogg\Form\Posted_Data::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/staging38.construction-english.com/public_html/wp-content/plugins/groundhogg/includes/form/form-v2.php on line 2064
Forum: Fixing WordPress
In reply to: WordPress core block editor display problem on LD post typesi brought it up with LD Support and it seems they have more serious issues to resolve. They fed me a CSS snippet that didn’t work, and I ended up using chatgpt to get a php snippet that fixed the sidebar tools/save button issue.
I couldnt resolve the top toolbar issue. I’ve just adjusted my workflow to use the floating toolbar instead.
if you want the snippet to resolve the save button problem, let me know and I’ll share it here.
Hi Tahmid! thank you so much for your response.
How are the WP user meta (the source) mapped to the custom Fluent contact fields (destination)? Is this integration included in the plugin, or do I need some sort of automation or plugin with a webhook?
Thanks!
Michael
@shresthauzwal I’ve updated to the latest plugin and the new patch fixed the problem.
Thanks for your quick response and resolution!
I’ve had the same problem since updating the plugin yesterday. email confirmation not sent/received.
EDIT: I rolled back the plugin to a previous version and it works fine now.
- This reply was modified 3 years, 2 months ago by michaelbgood.
Hello-
I got it sorted. Apparently, I needed the WPe login shortcode in the login page.
Thanks for your quick reply!
Michael
@civilengbt Have you found a solution? ‘
I’m having the same problem. Create a test account, and after logging in with the CORRECT password, I get this error:
https://pasteboard.co/RAyVdyn5QfPt.png
This is solved by resetting the password using the UM reset form, but that’s not an appropriate solution.
Forum: Fixing WordPress
In reply to: Gutenberg Block editor UI has a display problemthanks- I solved the problem by getting a bigger monitor! it’s a whole new world. thanks for replying.
