Question to WP plugin developers from WP plugin developer

No “deregister”, no “register”, just the wp_enqueue_script(“jquery”) is enough, I never had a problem with it in any wp version.

DPereyra said
As ichurakov mentioned, just this: wp_enqueue_script("jquery"); No “deregister”, no “register”, just the wp_enqueue_script(“jquery”) is enough, I never had a problem with it in any wp version.

Using plain enqueue will not give an error, but there is a change that the user might end up loading jQuery multiple times if he is using an assortment of plugins.

nCrafts said

DPereyra said
As ichurakov mentioned, just this: wp_enqueue_script("jquery"); No “deregister”, no “register”, just the wp_enqueue_script(“jquery”) is enough, I never had a problem with it in any wp version.

Using plain enqueue will not give an error, but there is a change that the user might end up loading jQuery multiple times if he is using an assortment of plugins.

greenline said
Thanks for the answers… But is there any developer online who used a correct include in a plugin which was accepted on CC? Can he/she please tell us the exact way of doing this? I am still confused how should I include the jquery js at the begiing of my plugin withour breaking other plugins or the theme. Thanks

From your initial post, it appears that you are deregistering jquery to register a custom version of jquery. This can potentially break other plugins and themes. So try not to do that. Limit your deregistrations to scripts that are specific to your plugin. Jquery on the other hand is included by default in wordpress and it’s something that most plugins/themes rely on.

As already suggested, wp_enqueue_script is your friend here.

For the record, jquery not available in versions below 3.5 is not true. You can download one of the older archieves to verify, look in the following path : wp-includes\js. Probably been bundled since wp 2.6. Of course the version number of jquery will vary as the wordpress version gets older, but IMHO that is a problem best solved by the user, i.e. upgrading their version of wordpress.

OriginalEXE said

nCrafts said

DPereyra said
As ichurakov mentioned, just this: wp_enqueue_script("jquery"); No “deregister”, no “register”, just the wp_enqueue_script(“jquery”) is enough, I never had a problem with it in any wp version.

Using plain enqueue will not give an error, but there is a change that the user might end up loading jQuery multiple times if he is using an assortment of plugins.

Wrong, you can have wp_enqueue_script(“jquery”) 1000 times, only once will jQuery be called, that’s the beauty of it

Yes, found out

No de-register, no register, at all. I only used the above piece of code. But from rejection email, I understood that was not the correct way of including jquery, that’s why I asked. But maybe that’s the standard rejection email, so…I think I will not modify my include line.

2greenline. This is correct way of including jQuery. Just resubmit your item saying that you use WP native jQuery and not de- re- register it.

I did that and my item was accepted, thank you!

Warning: you have included the Google Maps API multiple times on this page. This may cause unexpected errors.

Now, how should I check in my plugin if there is a http://maps.googleapis.com/maps/api/... already included?

And what if there is version included by another plugin, but I want to use the latest google map api? How do I do that without breaking another plugins?

One more thing: I want to create a user (in my wordpress live preview website) and I want to give this user the permission to see only a plugin’s settings admin page (without access to editing any other thing in the wordpress admin panel). How do I do that?

The purpose is to allow them to see live the plugin’s back-end settings before buying.