Here’s the thing though – everything works correctly without 3rd party cookies enabled in the modal overlay, except the manage account link. For example, registering or paying seems to work fine. Perhaps the best solution is for the Memberful plugin to automatically detect if 3rd party cookies are enabled, and if they’re not, don’t take over the manage account link clicks. Only do it if it’s going to end up loading the overlay correctly.
Can you please run this by your engineers?
This reply was modified 3 months, 3 weeks ago by archon810.
Thank you for such a quick reply. If there is no way for Memberful show this Account Management modal without third-party cookies enabled in the browser, then it should stop hijacking the manage account URL https://OURSITE.memberful.com/account and allow it to open in a new tab, right? Otherwise, it’s basically breaking its own functionality.
This reply was modified 3 months, 3 weeks ago by archon810.
This reply was modified 3 months, 3 weeks ago by archon810.
@takayukister I’m sorry, I can’t share the list and we also have a lot of inhouse code in plugins, but I’m not sure any of it would affect the contact forms. I think it’s really about the contact form data that specific user submitted.
I just checked Sentry and there have been 2 more instances of this. Luckily, it seems that Sentry saved the form data after all in the report leading up to the crash. The bad news is I think it mangled some characters that caused the notice because a few of them are showing up as incorrect characters, and pasting the form content from Sentry doesn’t result in a form crash.
I’m not sure what the characters are, but here’s a screenshot of one such submission:
Here’s another:
It looks like spam, plus it’s in Arabic, but that’s not really the point – crashes should not happen in the form.
This reply was modified 7 months, 1 week ago by archon810.
This reply was modified 7 months, 1 week ago by archon810.
You set the status to resolved, but is it really? Most people won’t have this define, and is it really the right solution rather than modifying the underlying code? Also, if it is the right solution, perhaps it should be pointed out somewhere in the docs and/or UI?
Claude suggests this as a workaround in the meantime:
// Force direct filesystem access for Contact Form 7 v6+ compatibility // CF7 v6 uses WP_Filesystem API which needs this to avoid credential prompts define('FS_METHOD', 'direct');
