<div dir="ltr"><div><div>So, in other words, I'm forced to screw thousands of my theme users. So be it.<br><br></div>Right now, users with raw html capability can insert whatever they want, including JavaScript, into <head>, the header, and the footer.<br>
<br></div>They've been able to do this since I introduced by theme in 2010, and there are thousands and thousands of users who've been using that capability with no know issues for all that time.<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Mar 6, 2014 at 10:22 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Any arbitrary script/stylesheet that hooks into wp_head or wp_footer (or that can/should do so) is exactly the focus of the guideline change. Allowing a grandfather exception would defeat the purpose.</p>
<p dir="ltr"> If you're talking about markup at template locations, that's possibly worth discussing.</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Mar 6, 2014 12:16 PM, "Bruce Wampler" <<a href="mailto:weavertheme@gmail.com" target="_blank">weavertheme@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>I'm trying to avoid specifics on this general group, but, to generalize...<br><br></div><div>Using the WP Settings API runs all settings through validation checks which often filter the content, possibly deleting part of a particular setting through the filter (think JavaScript). So, my existing validation/filters allow one kind of content to be accepted (for those with raw html capability only). The new guidelines prohibit that kind of content in some places, so to comply with the new guidelines, I would have to simply change the validation filter to remove that content. But that same filter will then also remove that content from any users who had previously had the now prohibited content. So their sites will now be broken just by updating to the new version and opening the admin page - the previously valid settings will be filtered out. <br>
<br></div><div>A plugin (which has been suggested as a way around this requirement) is not a solution in this case because they would have to install the plugin before updating to a new 3.9 compliant version of the theme, and then simply deactivating the plugin would revert to removing the settings which is not very user friendly behavior. So the only solution I can see to not screw my exiting users is to ask to get this one thing grandfathered for my existing themes.<br>
</div><div><br><br></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 6, 2014 at 9:51 AM, Derek Herman <span dir="ltr"><<a href="mailto:derek@valendesigns.com" target="_blank">derek@valendesigns.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hey Bruce,<div><br></div><div>I just read the WordPress 3.9 proposal and didn't see anything about settings being erased - could you please elaborate on what would cause that?<br>
<div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;white-space:normal;font-family:Helvetica;word-spacing:0px"><div>
<span style="font-size:12px"><br>Cheers,</span><br><span style="font-size:12px">Derek Herman</span><br><font style="font-size:medium" color="#144fae"><span style="font-size:12px"><a href="http://valendesigns.com" target="_blank">http://valendesigns.com</a></span></font></div>
</span></div><div><br><br></div><br></div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
</div></div><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>