Opera One does not work correctly with WordPress
tentiuzyou last edited by leocg
When we use Opera One, it does not work correctly with WordPress.
Before Opera One, we used Opera browser with WordPress without any problem.
After using Opera One, we cannot create and modify WordPress files because the visual editor, the eye-catching image insertion, and the theme customization do not work with Opera One.
I asked the WordPress theme company why Opera One is in trouble with WordPress; they answered they think all the browsers in the latest version can work with the theme without any problem. But we still have the same issues.
We have verified that Google Chrome, Vivaldi, and Microsoft Edge work correctly with WordPress. Only Opera One has the problems with WordPress.
I would be delighted if you could tell me how to resolve the problem.
Opera One(version: 102.0.4880.40)
Update Steam: Stable
System: Windows 11 Pro 23H2 (64-bit JPN)
Chromium version: 116.0.5845.141
I have been the ancient fun of the Opera browser since it launched. I paid some money to register the license and have used it until now. I cannot think I will work without the Opera browser. I need some help from you.
vr51 last edited by
Can confirm. The WordPress editor screen crashes when logged into a WordPress website with the default Opera browser window but does not crash when using incognito mode. Issue exists when after full browser cache wipe and all browser extensions disabled.
I am using Opera One version 102.0.4880.40 on Linux.
Is there a difference in the way Incognito Mode and non Incognito Mode windows handle jQuery and jQuery errors?
Example error output in Console
Uncaught TypeError: this.activateMode is not a function at media-views.js:6147:9 at It (provider.js:2:586804) at Function.ma (provider.js:2:621991) at n._createModes (media-views.js:6146:5) at n.initialize (media-views.js:6095:8) at n.initialize (media-views.js:7685:30) at n.initialize (media-views.js:7207:35) at h.View (backbone.min.js:2:14648) at n.constructor (wp-backbone.js:503:18) at n.constructor (media-views.js:10262:20) (anonymous) @ media-views.js:6147 It @ provider.js:2 ma @ provider.js:2 _createModes @ media-views.js:6146 initialize @ media-views.js:6095 initialize @ media-views.js:7685 initialize @ media-views.js:7207 h.View @ backbone.min.js:2 constructor @ wp-backbone.js:503 constructor @ media-views.js:10262 n @ backbone.min.js:2 n @ backbone.min.js:2 n @ backbone.min.js:2 wp.media @ media-models.js:1429 MediaUpload @ media-utils.js:290 constructClassInstance @ react-dom.js:14333 updateClassComponent @ react-dom.js:19698 beginWork @ react-dom.js:21621 callCallback @ react-dom.js:4151 invokeGuardedCallbackDev @ react-dom.js:4200 invokeGuardedCallback @ react-dom.js:4264 beginWork$1 @ react-dom.js:27461 performUnitOfWork @ react-dom.js:26567 workLoopSync @ react-dom.js:26476 renderRootSync @ react-dom.js:26444 recoverFromConcurrentError @ react-dom.js:25860 performSyncWorkOnRoot @ react-dom.js:26106 flushSyncCallbacks @ react-dom.js:12052 (anonymous) @ react-dom.js:25661 01:44:13.891 react-dom.js:18697 The above error occurred in the <MediaUpload> component: at MediaUpload (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/media-utils.js:259:5) at https://example.com/wp-content/plugins/jetpack/_inc/blocks/editor.js?minify=false&ver=28f8b8388fd72942a32e:113:1285 at FilteredComponentRenderer (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:71844:9) at MediaUploadCheck (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/block-editor.js:29484:3) at div at PostTypeSupportCheck (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/editor.js:6409:3) at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/data.js:4132:22 at WithSelect(PostTypeSupportCheck) (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/compose.js:3117:10) at ThemeSupportCheck (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/editor.js:7197:3) at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/data.js:4132:22 at WithSelect(ThemeSupportCheck) (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/compose.js:3117:10) at PostFeaturedImageCheck at PostFeaturedImage (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/editor.js:7321:3) at FilteredComponentRenderer (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:71844:9) at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/data.js:4286:25 at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/data.js:4132:22 at WithSelect(WithDispatch(WithFilters(PostFeaturedImage))) (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/compose.js:3117:10) at Component (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:72026:89) at div at UnforwardedPanelBody (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:62764:5) at PostTypeSupportCheck (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/editor.js:6409:3) at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/data.js:4132:22 at WithSelect(PostTypeSupportCheck) (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/compose.js:3117:10) at ThemeSupportCheck (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/editor.js:7197:3) at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/data.js:4132:22 at WithSelect(ThemeSupportCheck) (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/compose.js:3117:10) at PostFeaturedImageCheck at FeaturedImage (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/edit-post.js:7613:3) at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/data.js:4286:25 at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/data.js:4132:22 at WithSelect(WithDispatch(FeaturedImage)) (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/compose.js:3117:10) at div at UnforwardedPanel (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:62690:3) at div at SlotComponent (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:20706:5) at Slot at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:21289:3 at ComplementaryAreaSlot (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/edit-post.js:1214:3) at div at NavigableRegion (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/edit-post.js:1428:3) at div at div at div at InterfaceSkeleton (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/edit-post.js:1500:3) at Layout (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/edit-post.js:9006:84) at ErrorBoundary (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/editor.js:6115:5) at BlockRefsProvider (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/block-editor.js:22307:3) at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/block-editor.js:23657:5 at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/block-editor.js:23319:5 at WithRegistryProvider(Component) at BlockContextProvider (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/block-editor.js:16628:3) at EntityProvider (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/core-data.js:6200:3) at EntityProvider (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/core-data.js:6200:3) at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/editor.js:13229:3 at https://c0.wp.com/c/6.3.1/wp-includes/js/dist/editor.js:12782:5 at WithRegistryProvider(Component) at SlotFillProvider (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:21134:3) at provider_SlotFillProvider (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:21157:5) at Provider (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/components.js:21302:3) at div at ShortcutProvider (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/keyboard-shortcuts.js:749:75) at Editor (https://c0.wp.com/c/6.3.1/wp-includes/js/dist/edit-post.js:9528:3) React will try to recreate this component tree from scratch using the error boundary you provided, ErrorBoundary. logCapturedError @ react-dom.js:18697 callback @ react-dom.js:18765 callCallback @ react-dom.js:13933 commitUpdateQueue @ react-dom.js:13954 commitLayoutEffectOnFiber @ react-dom.js:23374 commitLayoutMountEffects_complete @ react-dom.js:24698 commitLayoutEffects_begin @ react-dom.js:24684 commitLayoutEffects @ react-dom.js:24622 commitRootImpl @ react-dom.js:26833 commitRoot @ react-dom.js:26692 performSyncWorkOnRoot @ react-dom.js:26127 flushSyncCallbacks @ react-dom.js:12052 (anonymous) @ react-dom.js:25661 01:44:14.856
nawkrzy last edited by
Hi. After update Opera One to version 102.X i have a problem with my WordPress. Yes, with WordPress and I noticed that no one has written about this yet.
When I try to create new post or edit a post I get message that the editor encountered an unexpected error. I can copy the text from post or copy the error code. Error code is below. I am using WordPress 6.3.1 and I noticed this problem is only when I try to use Gutenberg Block Editor. What is weird, this error only appears in Opera Browser on Windows PC. On the same PC but in Chrome, Edge or FireFox everything works fine, as well as on MacBook Air in Opera. I tried to clear all cache in Opera and in my website, I deleted Opera folders in AppData, I reinstalled Opera to the older version and the problem is the same.
TypeError: this.activateMode is not a function at https://galaktyczny.pl/wp-includes/js/media-views.min.js?ver=6.3.1:2:59604 at It (chrome-extension://gojhcdgcpbpfigcaejpfhfegekdgiblk/web3/provider.js:2:586804) at Function.ma (chrome-extension://gojhcdgcpbpfigcaejpfhfegekdgiblk/web3/provider.js:2:621991) at n._createModes (https://galaktyczny.pl/wp-includes/js/media-views.min.js?ver=6.3.1:2:59564) at n.initialize (https://galaktyczny.pl/wp-includes/js/media-views.min.js?ver=6.3.1:2:58973) at n.initialize (https://galaktyczny.pl/wp-includes/js/media-views.min.js?ver=6.3.1:2:79857) at n.initialize (https://galaktyczny.pl/wp-includes/js/media-views.min.js?ver=6.3.1:2:73432) at h.View (https://galaktyczny.pl/wp-includes/js/backbone.min.js?ver=1.4.1:2:14648) at n.constructor (https://galaktyczny.pl/wp-includes/js/wp-backbone.min.js?ver=6.3.1:2:2602) at n.constructor (https://galaktyczny.pl/wp-includes/js/media-views.min.js?ver=6.3.1:2:106817)
What is wrong? Yes, I tried to find the solution and checked almost every instruction to solve it, but the problem is still here.
tentiuzyou last edited by tentiuzyou
Hi. Thank you everyone for your replies.
I wanted to report the issue to the WordPress Team, but since I do no know the cause, I posted it on the Opera forums.
There are other people with the same problem, so it seems like I'm not the only one.
The one I use to post on WordPress is not "Gutenberg".
I use the "Classic Editor" for posting on WordPress. You can also post using the visual editor and text editor, but eye-catching posts did not work. I've tried various things, but I don't think it's a plugin or theme issue.
WordPress worked fine with the " Vivaldi". However, I would be most happy to post using Opera (OperaOne), which I have been using for a long time and am familiar with.
panagiotispa75 last edited by
Now more problems are coming up. It's been a few days since the last update of Opera One and now when I login on my web banking i cannot interact with the website or see anything. It's so frustrating. I am using Opera for so many years but i had never had such problems. If i login with Google Chrome or Edge everything works fine....... I don't want to change my favorite browser...... Where are the devs? Isn't anybody going to give an answer on this forum?
vr51 last edited by vr51
@tentiuzyou I reported the issue to WP Trac and to the Gutenberg issues tracker on GitHub.
WordPress 6.3.0 had a bug in the editor that prevented people using Gutenberg. Version 6.3.1 fixed that bug. It looks like the bug is might still be present but shows only when Opera One used and then only when a non private window is used (Private windows work fine).
Apparently the bug is not caused by Opera extensions or WordPress plugins. Maybe it is purely down to the way Opera One handles script errors.
The WP issue posts about this are here:
- GitHub: https://github.com/WordPress/gutenberg/issues/53579
- Trac: https://core.trac.wordpress.org/ticket/59038
Those two issues were thought to be resolved. I added to them about the conflict with Opera today.
The bug affects the Customizer screen as well.
tentiuzyou last edited by
I verified it, and it works fine with Japanese banks and PayPal. I think you should file a bug report.
I think that way it will be communicated to the development team.
You can go to the form to report a bug from the URL below.
nawkrzy last edited by
Today I updated Opera to the version 102.0.4880.51 and there is still a problem. I've been using Opera for years and this is the first time I want to remove it from my drive. I can't manage my site because they broke something
hsikorski Opera last edited by
We've investigated the issue at Opera and found that it was caused by the Opera Wallet extension (v1.17) being incompatible with some WordPress plugins (Gutenberg, more specifically). We've recently addressed this and released Opera Wallet v1.18 to resolve the issue. The extension should be automatically updated once you reopen your browser. If you want to update it manually, go to opera://extensions, turn on Developer Mode, and press Update.
Thank you for your patience, and have a great day!
vr51 last edited by
@hsikorski Thank you so much. I will test this update over the weekend. Hopefully the issue is resolved.
Can you and the Opera dev team do me a favour and add a comment to the Gutenberg GitHub issue tracker about this bug just to let the Gutenberg developers know a few of the technical reasons for the bug. It may help the Gutenberg devs to locate bugs and oversights in Gutenberg, and prevent a code reversion that could bring bugs back.
The GitHub issue tracker is here https://github.com/WordPress/gutenberg/issues/53579
tentiuzyou last edited by
Sincerely, I appreciate your post. And I would like to express my deepest gratitude to the entire Opera team and everyone involved in the Opera development team.
I am happy to continue using the Opera (Opera One) browser as my best web browser.