That is certainly not what we want! I am more than willing to hop in and see how I can replicate that problem, and see about a fix. Is simply activating jetpack alongside my plug in and viewing a page sufficient to replicate the problem? Do I have to have any specific blocks or other content on a page in order to see the error?
Let me know as soon as possible, and I’ll have a look. In the meantime I will be trying to replicate the issue on a test site, but so far I’ve not had any luck with that.
I use Jetpack for subscribers and gallery only. However, the only way to eliminate any issue was to deactivate Better Click to Tweet.
The error occurred when I tried to edit a post on the backend. It would pop up a blank page with “The editor has encountered an unexpected error attempt recovery/copy paste text/copy error” These were on posts that were scheduled. These posts included the Better Tweet in them. If that helps.
I’m having the same issue as Kim. Only mine isn’t just for scheduled posts. It’s for any I try to edit.
Hi. Following up on this error, which I still have when both Jetpack and Better Click to Tweet are activated. This is what shows up when I hit “copy error.” *All I removed is my URL.
TypeError: e.match is not a function
at c (https://[]/wp-content/plugins/jetpack/_inc/blocks/editor.js?minify=false&ver=74c62ddf4e7f5e16d2eb:67:5876)
at https://[].com/wp-content/plugins/jetpack/_inc/blocks/editor.js?minify=false&ver=74c62ddf4e7f5e16d2eb:61:8952
at ct (https://c0.wp.com/c/6.1.1/wp-includes/js/dist/vendor/react-dom.min.js:9:43430)
at os (https://c0.wp.com/c/6.1.1/wp-includes/js/dist/vendor/react-dom.min.js:9:111136)
at Ur (https://c0.wp.com/c/6.1.1/wp-includes/js/dist/vendor/react-dom.min.js:9:77643)
at Ir (https://c0.wp.com/c/6.1.1/wp-includes/js/dist/vendor/react-dom.min.js:9:77571)
at Dr (https://c0.wp.com/c/6.1.1/wp-includes/js/dist/vendor/react-dom.min.js:9:77434)
at Pr (https://c0.wp.com/c/6.1.1/wp-includes/js/dist/vendor/react-dom.min.js:9:74429)
at https://c0.wp.com/c/6.1.1/wp-includes/js/dist/vendor/react-dom.min.js:9:30173
at unstable_runWithPriority (https://c0.wp.com/c/6.1.1/wp-includes/js/dist/vendor/react.min.js:9:7431)
I’m also having the same problem. It occurs when I try to add Click-to-Tweet to a post. And it sometimes occurs when trying to edit an existing post that uses the Click-to-Tweet feature.
I first noticed this problem after installing JetPack 11.7.1
On my staging site, I removed JetPack and I could again use Click-to-Tweet without any problem. (Curiously, when I added JetPack back to my staging site, Click-to-Tweet continued to work.)
Unfortunately, I’m continuing to experience the problem on my live site. I have the current version of both plugins active.
-
This reply was modified 1 year, 7 months ago by
peterdblog.
I am getting this problem too. I loved the plugin, but because of this problem, I have to disable bctt every time I have to edit an old post.
replaced site name with example.com
TypeError: e.match is not a function
at c (https://e.com/wp-content/plugins/jetpack/_inc/blocks/editor.js?minify=false&ver=873455a375b7035ac001:70:5876)
at https://example.com/wp-content/plugins/jetpack/_inc/blocks/editor.js?minify=false&ver=873455a375b7035ac001:64:9013
at ct (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:43430)
at os (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:111136)
at Ur (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77643)
at Ir (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77571)
at Dr (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:77434)
at Pr (https://example.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:74429)
at https://exammple.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:9:30173
at unstable_runWithPriority (https://example.com/wp-includes/js/dist/vendor/react.min.js?ver=17.0.1:9:7431)
Hey folks. Sincere apologies for the slow turnaround here. I am able to reproduce the problem here, but I’m at a bit of a loss on how to resolve it. I’m reaching out to some friends here to try and find someone who knows more than I do.
In the meantime, it appears you need to temporarily disable Jetpack to add in a Better Click To Tweet block on a page or post.
I’ll update here as I learn more.
Update here: The Jetpack team is handling at least part of this from their side. Here’s the PR that is currently open but will resolve this issue. https://github.com/Automattic/jetpack/pull/29681
