<div dir="ltr">Yes, if core can add analytics and site verification id's to settings section, that would be great.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 15, 2013 at 6:25 AM, Azizur Rahman <span dir="ltr"><<a href="mailto:prodevstudio@gmail.com" target="_blank">prodevstudio@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If there is no core api for this kind of option/configuration then how does a developer add those properly? (I am not picking on you Emil so don't take it personally)<div>
<br></div><div>IMO these options are equivalent to robot.txt which is taken care of in core.</div>
<div><br></div><div>In my view these are site configuration and theme should stay out of them. It has nothing to do with presentation.</div><div><br></div><div><font><span style="line-height:normal;background-color:rgba(255,255,255,0)">WPTRT</span></font><span> could</span><span> propose that if a </span><span>theme is going to provide an</span><span> interface to set these value </span><span>they need to be stores such a way that it can transfer from theme to theme and even plugins. WPTRT needs provide those guidelines in where and how these config stored/retrived. so that user/site is not <span></span>impacted adversely when switching themes.</span><br>
</div><div><br></div>I know not everyone will agree to above but it is in the best interest of the end user.<div><br></div><div>Regards,</div><div><br></div><div>Azizur<div><div class="h5"><br><div><br><br>On Monday, 15 July 2013, Emil Uzelac wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Jason,<div><br></div><div>Assuming that we're referring to Theme Options, this should be fine.</div>
<div><br></div><div><i>As long as this is not hardcoded and properly added :)</i></div><div><br></div>
<div>Thanks,</div><div>Emil </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 14, 2013 at 6:28 PM, Jason Clarke <span dir="ltr"><<a>jgc@jasonclarke.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Admins,<div><br></div><div>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.</div>
<div><br></div><div>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?</div>
<div><br></div><div>Thank you!</div><div>Jason</div><div><br></div><div>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).<span><font color="#888888"><br clear="all">
<div><br></div>-- <br>Jason Clarke<br><a href="http://jasonclarke.org" target="_blank">http://jasonclarke.org</a><br><br>************************<br>
</font></span></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a>theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div></div></div><span class="HOEnZb"><font color="#888888"><br><br>-- <br>Sent from Gmail Mobile<br>
</font></span><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>