<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The only problem with such features when switching themes is breaking content not styles, so if after switching themes the content is still visible and accessible, although not styled, I say it's okay. It would be nice to have a fallback plugin though.<div><br></div><div>Daniel</div><div> <br><div><div>On Mar 3, 2013, at 4:03 PM, Ünsal Korkmaz wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Thank you everyone for sparing time. Can you check original question if possible please:<div><br><div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">My theme:</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><a href="http://themes.trac.wordpress.org/ticket/11437" target="_blank" style="color:rgb(17,85,204)">http://themes.trac.wordpress.org/ticket/11437</a></div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Theme is adding custom tinymce button that adds css code for design elements. There is no shortcode or something.. just css code. </div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Its allowed in themes right?</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<br></div><br><div class="gmail_quote">On Sun, Mar 3, 2013 at 3:59 PM, Dane Morgan <span dir="ltr"><<a href="mailto:dane@danemorganmedia.com" target="_blank">dane@danemorganmedia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 2013-03-03 07:52, Daniel Tara wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There are a number of elements which are considered decisive in the rejection of the theme like incorrect Theme URI, Author URI, credit link, screenshot or license. One of the reasons is that it is considered possible intention of the theme author to circumvent <a href="http://WP.org">WP.org</a> policy and use the directory as a resource for cheap traffic and the other is that they are elements which can be very easy to notice. That's why they appear in the ticket's content. Themes can be rejected on this criteria even by skipping priorities. A simple san through the list of open tickets and discarding all that do not comply with one of these guidelines and the queue becomes much cleaner. It's also helpful for the author in that he doesn't waste his time in case he doesn't intend changing any of the above.<br>
</blockquote></div>
I get that.<br>
<br>
My point is a bit more esoteric, and maybe off the mark, so I'll just note that the way we phrase things shapes us and our actions, and the phrasing here seems to set reviewers and authors in an antagonistic relationship, and then I'll let it lie.<div class="HOEnZb">
<div class="h5"><br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</div></div></blockquote></div><br></div></div>
_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<br></blockquote></div><br></div></body></html>