[theme-reviewers] Webmaster Tools IDs - plugin territory?

[Chip Bennett]

I don't think a discussion is a waste of anyone's time.

I can understand why some would argue where the presentation-functionality
line is appropriate for post-content shortcodes, or favicons, or other
things that actually get rendered on the site front end. I really don't
understand why there would be much of a debate about where the
content-presentation line is appropriate for things that have absolutely no
front-end impact - such as site analytics or webmaster tools.

That's why discussion is a good thing. :)


On Sun, Jul 14, 2013 at 8:36 PM, Jason Clarke <jgc at jasonclarke.org> wrote:

> Hi Emil,
>
> I apologize if you feel I'm wasting the group's time. My main concern is
> that as a new theme reviewer, I'm reading what appears to be directly
> conflicting answers between yourself and Chip as two admins, and I'm really
> trying to simply sort that out and move on with the theme.
>
> Thank you,
> Jason
>
>
> On Sun, Jul 14, 2013 at 8:31 PM, Emil Uzelac <emil at uzelac.me> wrote:
>
>> We're wasting time.
>>
>> If this does not break the Theme, interferes with the core, it is and
>> should be fine.
>>
>>
>>
>>
>> On Sun, Jul 14, 2013 at 7:26 PM, Srikanth Koneru <tskk79 at gmail.com>wrote:
>>
>>> Agree with Chip, use a plugin, set them once and forget about them,
>>> Switch as many themes as they wish and no adverse effects for them
>>> especially since they are very important tools.
>>>
>>>
>>> On Mon, Jul 15, 2013 at 5:51 AM, Chip Bennett <chip at chipbennett.net>wrote:
>>>
>>>> A Plugin developer not updating a Plugin is not analogous to a user
>>>> switching Themes. Plugin developers may or may not update their Plugins any
>>>> more or less often than Theme developers update their Themes. But end users
>>>> can, do, and will switch Themes - often frequently.
>>>>
>>>> Site analytics, authentication/verification, etc. don't have anything
>>>> to do with presentation of user content, but are quite important for end
>>>> users who choose to use those tools.
>>>>
>>>>
>>>> On Sun, Jul 14, 2013 at 8:13 PM, Emil Uzelac <emil at uzelac.me> wrote:
>>>>
>>>>> Theme author's should be allowed to add this in Theme Options
>>>>> and like Chip says if there's no impact to the Theme in any way
>>>>> it's fine.
>>>>>
>>>>> Now, as far as what happens when user switches the Theme
>>>>> is completely up to user, their responsibility.
>>>>>
>>>>> What happens when plugin author does not update the plugin,
>>>>> it may break right? same thing when they switch the Theme :)
>>>>>
>>>>>
>>>>> On Sun, Jul 14, 2013 at 6:56 PM, Chip Bennett <chip at chipbennett.net>wrote:
>>>>>
>>>>>> Partly rhetorical questions:
>>>>>>
>>>>>> 1) What is the purpose of Google Webmaster Tools and Alexa?
>>>>>> 2) Do those things impact the presentation of user content?
>>>>>> 3) Would the end user be adversely impacted if those things were lost
>>>>>> when switching Themes?
>>>>>>
>>>>>>
>>>>>> On Sun, Jul 14, 2013 at 7:28 PM, Jason Clarke <jgc at jasonclarke.org>wrote:
>>>>>>
>>>>>>> Hi Admins,
>>>>>>>
>>>>>>> Long-time listener, first-time caller here- in reviewing my first
>>>>>>> theme, I remembered a recent list discussion on how Analytics-specific
>>>>>>> fields in themes are not allowed because they're considered plugin
>>>>>>> territory.
>>>>>>>
>>>>>>> On a related note, I'm assuming that other similar fields such as
>>>>>>> "Google Webmaster Tools ID" and "Alexa ID" are also plugin territory- can
>>>>>>> the admins confirm this is the case?
>>>>>>>
>>>>>>> Thank you!
>>>>>>> Jason
>>>>>>>
>>>>>>> PS - As a side/related note, it would be super helpful if the list
>>>>>>> archives where somehow searchable - that might be one more avenue for
>>>>>>> newbies like myself to check before emailing the list (assuming guidelines
>>>>>>> haven't changed).
>>>>>>>
>>>>>>> --
>>>>>>> Jason Clarke
>>>>>>> http://jasonclarke.org
>>>>>>>
>>>>>>> ************************
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>
>>
>
>
> --
> Jason Clarke
> http://jasonclarke.org
>
> ************************
>
> _______________________________________________
> 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/20130714/b25d406a/attachment-0001.html>