[theme-reviewers] Plugins and Themes

[Emil Uzelac]

very good :)

Emil

On Sat, Aug 25, 2012 at 8:03 AM, Edward Caissie <edward.caissie at gmail.com>wrote:

> @Emil - Those guidelines have been around for quite some time, but they
> are not the most obvious to find ...
>
> ... there are also a few in there that we might consider for the Theme
> Review guidelines, too.
>
>
> Cais.
>
>
>
> On Fri, Aug 24, 2012 at 9:33 PM, Emil Uzelac <emil at themeid.com> wrote:
>
>> I wasn't aware about the guidelines, great info Cais. @Daniel/Merci I
>> can't agree more. This is something that was raised on my forum and you
>> guys know how easy is to "blame" on Themes when stuff don't work the way
>> they should :)
>>
>> Thanks,
>> Emil
>>
>> On Fri, Aug 24, 2012 at 8:14 PM, Edward Caissie <edward.caissie at gmail.com
>> > wrote:
>>
>>> Interestingly enough, this point came up in a recent Meetup about
>>> plugins I just organized.
>>>
>>> I would likely think that item 7 in the Plugin Guidelines (
>>> http://wordpress.org/extend/plugins/about/guidelines/) would cover
>>> this, but in so doing if the plugin author is using new functionality only
>>> available in a newer version of a core-bundled script I would interpret
>>> item 7 to allow this providing the plugin author also advises the end-user
>>> the plugin is doing so (perhaps in the plugin description).
>>>
>>> Fortunately Theme Guidelines simply do not allow for it at all (*grin*)
>>>
>>>
>>> Cais.
>>>
>>>
>>>
>>> On Fri, Aug 24, 2012 at 8:02 PM, Merci Javier <mercijavier at gmail.com>wrote:
>>>
>>>>
>>>> Hi Emil.
>>>>
>>>> AFAIK, plugins which are hosted in the WP repo shouldn't be
>>>> deregistering core jquery at all.
>>>>
>>>> Best thing to do is report such plugins or inquire at
>>>> plugins at wordpress.org and they can take appropriate action. They
>>>> usually write back and inform you about the action taken on the plugin. I
>>>> reported a plugin which phoned home (and more) and they took it off right
>>>> away and let me know about it.
>>>>
>>>> Mercime
>>>>
>>>>
>>>>
>>>> On Fri, Aug 24, 2012 at 3:20 PM, Emil Uzelac <emil at themeid.com> wrote:
>>>>
>>>>> Right and that's something I like and support all the way :)
>>>>>
>>>>> Question was prompted by this http://pastebin.com/MaVFM1KZ and not
>>>>> just this, there are more plugins just like it where plugin author "kills"
>>>>> the bundled JS library, in this particular case the jQuery and "injects"
>>>>> not only non-bundle, but also higher version as well.
>>>>>
>>>>> I guess they are "allowed" to do this right? and there's nothing we
>>>>> can do from Theme's end to prevent that :(
>>>>>
>>>>> P.S. Higher version is most of the time compatibility issue.
>>>>>
>>>>> Thanks,
>>>>> Emil
>>>>>
>>>>> On Fri, Aug 24, 2012 at 5:10 PM, Chip Bennett <chip at chipbennett.net>wrote:
>>>>>
>>>>>> I'm not sure I understand the question.
>>>>>>
>>>>>>    - If a Theme wants to use jQuery, it should call
>>>>>>    wp_enqueue_script( 'jquery' ), to enqueue the core-bundled jQuery library.
>>>>>>    - If a Plugin wants to use jQuery, it should call
>>>>>>    wp_enqueue_script( 'jquery' ), to enqueue the core-bundled jQuery library.
>>>>>>    - No Theme or Plugin should de-register core-bundled jQuery, in
>>>>>>    order to register any other version of jQuery.
>>>>>>
>>>>>> Out of curiosity: what prompted the question?
>>>>>>
>>>>>> Chip
>>>>>>
>>>>>> On Fri, Aug 24, 2012 at 4:57 PM, Emil Uzelac <emil at themeid.com>wrote:
>>>>>>
>>>>>>>  Guys!
>>>>>>>
>>>>>>> Should plugin check first if the Theme is already "calling" the
>>>>>>> jQuery and if it does, plugin should do nothing and also not to remove wp_enqueue_script
>>>>>>> and "inject" higher version via Google API?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Emil
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> theme-reviewers mailing list
>>>>>>> theme-reviewers at lists.wordpress.org
>>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> theme-reviewers mailing list
>>>>>> theme-reviewers at lists.wordpress.org
>>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> theme-reviewers mailing list
>>>>> theme-reviewers at lists.wordpress.org
>>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> theme-reviewers mailing list
>>>> theme-reviewers at lists.wordpress.org
>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>>
>>>>
>>>
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>
>>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120825/6f53e891/attachment-0001.htm>