Conflict with Jetpack plugin

Hello @unwantedlife,

Thank you for contacting us!

Can you please share some screenshots or a screen recording that outlines the mentioned issue? It would help us in debugging this.

Looking forward to your reply,

Irinel

all that was there in the link I already provided, but here’s a new link to the folder with images and a video

https://drive.google.com/drive/folders/1TSPcyCFM7CXlE7ifOcEd_Ok2sbQgONLF

I tested my site with all the plugins and themes deactivated, and this problem returned when I activated your plugin

Hello @unwantedlife,

Thank you for providing the screenshots!

Are there any errors visible in the debug log or in the browser’s console? I didn’t manage to replicate the issue on my end.

Best regards,

Irinel

how do I access either of those and what would I be looking for?

Hey @unwantedlife,

You can use a dedicated plugin, such as Query Monitor or directly the Console available in the Inspector tool (right click > Inspect).

Let us know how it goes!

Two things.

One. You didn’t tell me what I’m looking for when right-clicking to get to inspect.

Two. Wouldn’t it be easier for you to visit my site and right-click to inspect as you know what you’re looking for?

Hello @unwantedlife,

You should check if any errors are thrown in the Console, and they can vary when you are logged in to the website as an admin.

Let us know if you find anything!

10 errors, 140 warnings, and 47 breaking changes

145Third-party cookie will be blocked. Learn more in the Issues tab.
26:272 Note: ExactMetrics does not track you as a logged-in site administrator to prevent site owners from accidentally skewing their own Google Analytics data.
If you are testing Google Analytics code, please do so either logged out or in the private browsing/incognito mode of your web browser.
jquery-migrate.min.js?ver=3.4.1:2 JQMIGRATE: Migrate is installed, version 3.4.1
admin-bar-v2.js?ver=13.1.1-202407-lite:1 Missing data from PHP (wpNotesArgs).
(anonymous) @ admin-bar-v2.js?ver=13.1.1-202407-lite:1
vue.js:5 TypeError: Cannot read properties of undefined (reading ‘_modules’)
at s.created (frontend.js?ver=7.24.1:1:11676)
at le (vue.js:5:24707)
at te (vue.js:5:33584)
at e._init (vue.js:5:44003)
at new s (vue.js:5:45253)
at Jo (vue.js:5:37911)
at init (vue.js:5:36760)
at d (vue.js:5:54275)
at p (vue.js:5:53904)
at L.patch (vue.js:5:58650)
Vr @ vue.js:5
vue.js:5 TypeError: Cannot read properties of undefined (reading ‘getters’)
at r. (vuex.js:5:9897)
at e.get (vue.js:5:28142)
at e.evaluate (vue.js:5:29142)
at s.notifications (vue.js:5:42783)
at s.has_notifications (frontend.js?ver=7.24.1:1:12175)
at e.get (vue.js:5:28142)
at e.evaluate (vue.js:5:29142)
at s.has_notifications (vue.js:5:42783)
at s.Dt (frontend.js?ver=7.24.1:1:12704)
at e._render (vue.js:5:21972)
Vr @ vue.js:5
pixel.wp.com/boom.gif?v=0.9&u=https://public-api.wordpress.com/pinghub&json={%22beacons%22:[%22pinghub.conn_close_code.1006.chrome:16626184|ms%22]}:1

   Failed to load resource: net::ERR_NETWORK_IO_SUSPENDED

7Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (”) does not match the recipient window’s origin (‘null’).
content_script.js:25 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://unwantedlife.me’) does not match the recipient window’s origin (‘null’).
(anonymous) @ content_script.js:25
Show 1 more frame
Show less
content_script.js:25 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://unwantedlife.me’) does not match the recipient window’s origin (‘null’).
(anonymous) @ content_script.js:25
Show 1 more frame
Show less
content_script.js:25 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://unwantedlife.me’) does not match the recipient window’s origin (‘null’).
(anonymous) @ content_script.js:25
Show 1 more frame
Show less
content_script.js:25 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://unwantedlife.me’) does not match the recipient window’s origin (‘null’).
(anonymous) @ content_script.js:25
Show 1 more frame
Show less
content_script.js:25 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://unwantedlife.me’) does not match the recipient window’s origin (‘null’).
(anonymous) @ content_script.js:25
Show 1 more frame
Show less
content_script.js:25 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://unwantedlife.me’) does not match the recipient window’s origin (‘null’).
(anonymous) @ content_script.js:25
Show 1 more frame
Show less
content_script.js:25 Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://unwantedlife.me’) does not match the recipient window’s origin (‘null’).
(anonymous) @ content_script.js:25
Show 1 more frame
Show less

Hello @unwantedlife,

I apologize for the delay in our response.

I checked your log, and there seems to be no mention of ROP/Revive Social. Because we were also not able to replicate this issue, and things are working as expected when using both ROP and Jetpack, I suspect it might be a plugin conflict.

You should try deactivating all the other plugins and see if the issue persists. After that, try activating them individually and find the problematic plugin. You should check for an alternative plugin in this case.

Hi, it is a plugin conflict. I already went through deactivating all my plugins and testing them. Yours was the one that triggered the return of the issues, which is why I contacted you about the issue.

The Jetpack ‘like’ button doesn’t load, and if you tap to reply to an existing comment on a post, you’re unable to because of the error that triggers. It’s an issue that occurs between your plugin and the Jetpack plugin.

This is also why I included a link to the forum post on Jetpack so you could see what I’d already done and how we identified it was an issue between yours and Jetpacks plugins.

What alternative plugin to you plugin would you recommend to replace your plugin?

Hello @unwantedlife,

Thank you for reaching out. After reviewing the error log you provided, we couldn’t find any references to ROP. Additionally, we’ve tested the scenario with both plugins activated and everything seems to be functioning as intended without any issues.

Regarding the suggestion about finding another plugin, we meant to explore alternative options that may not generate the output you’re encountering while using ours.

If you have any further questions or if there’s anything else we can assist you with, please don’t hesitate to let us know. We’re here to help.

I’d like a solution to fix the issue

Hey @unwantedlife,

I apologize, but as I mentioned, because the issue is not replicable and the error log has nothing to do with ROP, we cannot provide other solutions.