Timeline for Remove extra Google Maps script
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2016 at 11:11 | comment | added | Mark Kaplun | So you never had plugins that used CSS style that didn't work well with the theme you were using? plugin that had a function named "my_init" as the init hook? You are so lucky | |
| Mar 9, 2016 at 10:45 | comment | added | majick | You are joking right? If they were coded better like this in the first place I wouldn't have had to fix so many, lol. And as I recall, I have had this exact problem happen with Google Maps once, and simply dequeued one of the scripts so both plugins worked. If code like in these answers was present in either of the plugins there would have been no problem. | |
| Mar 9, 2016 at 10:25 | comment | added | Mark Kaplun | @majick, seems like you never had conflicting plugins and themes. | |
| Mar 9, 2016 at 10:22 | comment | added | majick | If plugins A and B both use shared resource C - as in this question! - there is no need for them to conflict, and simply checking like this helps avoid conflicts, so that the blank screen doesn't happen in the first place, and the site owner doesn't have to decide which is more important because they can just use both. | |
| Mar 9, 2016 at 9:18 | comment | added | Mark Kaplun | @majick, I don't get your point. I have two plugins on my site A and B. When both active the site goes blank. How can anyone which is not the site owner know which plugin is more important to the site? | |
| Mar 9, 2016 at 8:39 | comment | added | majick | how does that help? assuming the site owner can see there is a conflict, it is then left to them to deactivate one plugin or the other, or find a way to fix the conflict themselves. this kind of foresight for a plugin author should be encouraged not written off as "not my problem" = this is why conflicts happen in the first place. | |
| Mar 8, 2016 at 16:33 | comment | added | Mark Kaplun | @majick, it is not your problem as a plugin author. As I said it is hubris to assume your code is more important then the code in other plugins. If there is a collision then the site owner will see it when he activates the plugin and will probably deactivate it. If it is such a small problem that the site owner can not even see it, then there is nothing to fix in the first place | |
| Mar 8, 2016 at 16:26 | comment | added | majick | @Mark but if can help avoid such conflicts in the first place? finding a way to detect and workaround potential conflicts is better than trying to be compatible with X themes/plugins which is basically futile. | |
| Feb 26, 2016 at 20:12 | comment | added | Ignat B. | Thank you for prompt answer. I understand that it's not fair to block other plugins enqueues, due to that my question where asked: want to enqueue in a smooth way to cooperate with plugins, avodigin errors. Looks like i'd let things go and simply test with top-used plugins. | |
| Feb 26, 2016 at 18:49 | history | answered | Mark Kaplun | CC BY-SA 3.0 |