Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict Between MP3 Audio Player by Sonaar and Rank Math CMB2 #286

Open
alexdeborba opened this issue Jul 25, 2024 · 0 comments
Open

Conflict Between MP3 Audio Player by Sonaar and Rank Math CMB2 #286

alexdeborba opened this issue Jul 25, 2024 · 0 comments

Comments

@alexdeborba
Copy link

Describe the bug
There is a conflict between the MP3 Audio Player by Sonaar plugin [ Free / Pro ] and the Rank Math plugin. Both plugins use the open-source CMB2 project extensively. By default, CMB2 does not support a drag-and-drop feature, so each plugin has developed its own workaround. However, Rank Math is loading its own CMB2 version in priority, preventing the custom script from MP3 Audio Player by Sonaar from being loaded, causing a functionality issue.

To Reproduce
Steps to reproduce the behavior:

  1. Install and activate both the MP3 Audio Player by Sonaar plugin and the Rank Math plugin.
  2. Go to the MP3 Audio Player by Sonaar plugin settings.
  3. Attempt to use the drag-and-drop feature for ordering tracks.
  4. Observe the error where the custom script for drag-and-drop functionality is not loaded.

Expected behavior
The drag-and-drop functionality for ordering tracks in the MP3 Audio Player by Sonaar plugin should work correctly without interference from the Rank Math plugin.

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser: Chrome, Mozilla Developer Edition
  • Version: Latest.

Additional context
The conflict arises because Rank Math loads its own CMB2 version in priority, which prevents the custom script developed by MP3 Audio Player by Sonaar from being loaded. A temporary workaround is to deactivate Rank Math while ordering tracks and then reactivate it afterward. However, a more permanent solution is needed to resolve this conflict without requiring users to deactivate plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant