UPDATE:
I spoke to the plugin owner of ‘amr shortcode any widget’ plugin. I said:
I’ve been using ‘amr shortcode any widget’ for well over a year. It’s pretty good until just recently where it is now Interfering with another plugin ‘Another WordPress Classifieds Plugin (AWPCP)’ when I installed the addon: AWPCP BuddyPress Module which connects the classifieds posts to their buddypress profiles.
The conflict:
1. Stops you logging in my site with Safari.
2. Deleted many of my ‘amr shortcode any widget’ widgets.
3. Made classified posts from go AWPCP go invisible.
Raising it with AWPCP, they state: “In general, we can’t really fix issues with other plugins if they are doing something that violates WordPress standards. You’ll need to get in touch with the plugin developer and ask them to fix it.”
From my post, I’m hoping there’s at least a sign of what’s going on with amr shortcode any widget, and what exactly is this interference.
If there anything I can try to add to overcome this interference issue? I really love this plugin.
++In the next post was his reply:
This plugin is EXTREMELY simple really. It has no js of it’s own.
Literally all it does is provide a sidebar to setup the settings of the widgets and then when the shortcode filter is run, ‘catch’ the immediate output of the widgets so the output can be returned via the shortcode (widgets echo text, but shortcodes return the text.
Hi @kristianngve,
Sorry that you ran into issues here!
I’m not sure who you spoke with from AWPCP that said (since I’m the owner): “In general, we can’t really fix issues with other plugins if they are doing something that violates WordPress standards. You’ll need to get in touch with the plugin developer and ask them to fix it” This is the first I’ve heard of this particular issue being raised. I’ll check with my staff and see if they were spoken to and discuss how that could have been better handled for this particular case.
Regarding the developer’s comments above–just because something is simple doesn’t mean that it may not be the source of the issue. We will have to investigate to know for sure.
But in this case we can investigate further. I’ve asked my developer to take a look and I’ll report back when I hear more.