Title: archon810's Replies | WordPress.org --- # archon810 [ ](https://wordpress.org/support/users/archon810/) * [Profile](https://wordpress.org/support/users/archon810/) * [Topics Started](https://wordpress.org/support/users/archon810/topics/) * [Replies Created](https://wordpress.org/support/users/archon810/replies/) * [Reviews Written](https://wordpress.org/support/users/archon810/reviews/) * [Topics Replied To](https://wordpress.org/support/users/archon810/replied-to/) * [Engagements](https://wordpress.org/support/users/archon810/engagements/) * [Favorites](https://wordpress.org/support/users/archon810/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 390 total) 1 [2](https://wordpress.org/support/users/archon810/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/archon810/replies/page/3/?output_format=md)… [24](https://wordpress.org/support/users/archon810/replies/page/24/?output_format=md) [25](https://wordpress.org/support/users/archon810/replies/page/25/?output_format=md) [26](https://wordpress.org/support/users/archon810/replies/page/26/?output_format=md) [→](https://wordpress.org/support/users/archon810/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Jetpack - WP Security, Backup, Speed, & Growth] Huge /wp-json/jetpack/v4/sync/spawn-sync spikes every day at 4am causing load](https://wordpress.org/support/topic/huge-wp-json-jetpack-v4-sync-spawn-sync-spikes-every-day-at-4am-causing-load/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [3 weeks, 4 days ago](https://wordpress.org/support/topic/huge-wp-json-jetpack-v4-sync-spawn-sync-spikes-every-day-at-4am-causing-load/#post-18884544) * [@alinclamba](https://wordpress.org/support/users/alinclamba/) If we were to proceed in public for now, for the benefit of others with similar issues, what would the next steps be please? * Nevertheless, I also submitted a support ticket (#11129616) in case that gets more traction. - This reply was modified 3 weeks, 4 days ago by [archon810](https://wordpress.org/support/users/archon810/). - This reply was modified 3 weeks, 4 days ago by [archon810](https://wordpress.org/support/users/archon810/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Memberful - Membership Plugin] Memberful account manage modal prompts for login even when already logged in](https://wordpress.org/support/topic/memberful-account-manage-modal-prompts-for-login-even-when-already-logged-in/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/memberful-account-manage-modal-prompts-for-login-even-when-already-logged-in/#post-18792822) * 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](https://wordpress.org/support/users/archon810/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Memberful - Membership Plugin] Memberful account manage modal prompts for login even when already logged in](https://wordpress.org/support/topic/memberful-account-manage-modal-prompts-for-login-even-when-already-logged-in/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/memberful-account-manage-modal-prompts-for-login-even-when-already-logged-in/#post-18792552) * Just for this management link, yes. Please have a look at my last message. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Memberful - Membership Plugin] Memberful account manage modal prompts for login even when already logged in](https://wordpress.org/support/topic/memberful-account-manage-modal-prompts-for-login-even-when-already-logged-in/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/memberful-account-manage-modal-prompts-for-login-even-when-already-logged-in/#post-18791514) * 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](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](https://wordpress.org/support/users/archon810/). - This reply was modified 3 months, 3 weeks ago by [archon810](https://wordpress.org/support/users/archon810/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Contact Form 7] ErrorException: Deprecated: preg_replace(): Passing null to parameter #3](https://wordpress.org/support/topic/errorexception-deprecated-preg_replace-passing-null-to-parameter-3/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [6 months, 3 weeks ago](https://wordpress.org/support/topic/errorexception-deprecated-preg_replace-passing-null-to-parameter-3/#post-18694693) * Any updates please? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Contact Form 7] ErrorException: Deprecated: preg_replace(): Passing null to parameter #3](https://wordpress.org/support/topic/errorexception-deprecated-preg_replace-passing-null-to-parameter-3/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [7 months, 1 week ago](https://wordpress.org/support/topic/errorexception-deprecated-preg_replace-passing-null-to-parameter-3/#post-18669285) * [@takayukister](https://wordpress.org/support/users/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: * ![](https://i0.wp.com/i.imgur.com/Qi7FF8Q.png?ssl=1) * Here’s another: * ![](https://i0.wp.com/i.imgur.com/j7qLI6d.png?ssl=1) * 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](https://wordpress.org/support/users/archon810/). - This reply was modified 7 months, 1 week ago by [archon810](https://wordpress.org/support/users/archon810/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Contact Form 7] ErrorException: Deprecated: preg_replace(): Passing null to parameter #3](https://wordpress.org/support/topic/errorexception-deprecated-preg_replace-passing-null-to-parameter-3/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [7 months, 1 week ago](https://wordpress.org/support/topic/errorexception-deprecated-preg_replace-passing-null-to-parameter-3/#post-18666237) * I pasted the url, but it’s held in moderation right now. * I think the key is figuring out what in a message could lead to this exception, but the message was lost due to the crash. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Contact Form 7] connect(): Could not access filesystem after upgrade to v6](https://wordpress.org/support/topic/connect-could-not-access-filesystem-after-upgrade-to-v6/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [7 months, 1 week ago](https://wordpress.org/support/topic/connect-could-not-access-filesystem-after-upgrade-to-v6/#post-18666061) * 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? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Contact Form 7] connect(): Could not access filesystem after upgrade to v6](https://wordpress.org/support/topic/connect-could-not-access-filesystem-after-upgrade-to-v6/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [7 months, 2 weeks ago](https://wordpress.org/support/topic/connect-could-not-access-filesystem-after-upgrade-to-v6/#post-18664320) * Claude suggests this as a workaround in the meantime: * ```wp-block-code // Force direct filesystem access for Contact Form 7 v6+ compatibility// CF7 v6 uses WP_Filesystem API which needs this to avoid credential promptsdefine('FS_METHOD', 'direct'); ``` * It seems to work. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[ElasticPress Debugging Add-On] User Notice: Function _load_textdomain_just_in_time was called incorrectly](https://wordpress.org/support/topic/user-notice-function-_load_textdomain_just_in_time-was-called-incorrectly/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [1 year, 5 months ago](https://wordpress.org/support/topic/user-notice-function-_load_textdomain_just_in_time-was-called-incorrectly/#post-18153399) * Cross-posted to [https://github.com/10up/debug-bar-elasticpress/issues/102](https://github.com/10up/debug-bar-elasticpress/issues/102). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Site Kit by Google - Analytics, Search Console, AdSense, Speed] google-site-kit Error](https://wordpress.org/support/topic/google-site-kit-error-18/) * [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [1 year, 6 months ago](https://wordpress.org/support/topic/google-site-kit-error-18/#post-18103830) * PHP 9.3 doesn’t exist. I assume he means 8.3. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Memberful - Membership Plugin] PHP 8.2 warning](https://wordpress.org/support/topic/php-8-2-warning-2/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [2 years, 1 month ago](https://wordpress.org/support/topic/php-8-2-warning-2/#post-17553307) * Looks like 1.73.6 addresses this. [https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3064836%40memberful-wp&old=3054645%40memberful-wp&sfp_email=&sfph_mail=](https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3064836%40memberful-wp&old=3054645%40memberful-wp&sfp_email=&sfph_mail=) * ```wp-block-code 1.73.6 * Fix PHP deprecation warnings. ``` * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Table of Contents Plus] Fatal error – TOC+ Version 2309](https://wordpress.org/support/topic/fatal-error-toc-version-2309/) * [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [2 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-toc-version-2309/#post-17103848) * Fired up a Github ticket as well in case you’re not checking the forums [https://github.com/zedzedzed/table-of-contents-plus/issues/157](https://github.com/zedzedzed/table-of-contents-plus/issues/157). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Table of Contents Plus] Fatal error – TOC+ Version 2309](https://wordpress.org/support/topic/fatal-error-toc-version-2309/) * [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [2 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-toc-version-2309/#post-17088530) * This made some pages on the site crash. Had to revert. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Jetpack - WP Security, Backup, Speed, & Growth] Automattic\Jetpack\Stats\Tracking_Pixel::get_footer_to_add deprecated error](https://wordpress.org/support/topic/automatticjetpackstatstracking_pixelget_footer_to_add-deprecated-error/) * Thread Starter [archon810](https://wordpress.org/support/users/archon810/) * (@archon810) * [2 years, 9 months ago](https://wordpress.org/support/topic/automatticjetpackstatstracking_pixelget_footer_to_add-deprecated-error/#post-16981761) * Upon further review, it looks like this is caused by something we’re doing on our end (i.e. disabling certain Jetpack functions) due to [Jetpack causing major performance issues on the frontend in the past](https://github.com/Automattic/jetpack/issues/19823). We’ll take a look at resolving this internally. Viewing 15 replies - 1 through 15 (of 390 total) 1 [2](https://wordpress.org/support/users/archon810/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/archon810/replies/page/3/?output_format=md)… [24](https://wordpress.org/support/users/archon810/replies/page/24/?output_format=md) [25](https://wordpress.org/support/users/archon810/replies/page/25/?output_format=md) [26](https://wordpress.org/support/users/archon810/replies/page/26/?output_format=md) [→](https://wordpress.org/support/users/archon810/replies/page/2/?output_format=md)