<div dir="ltr">Perhaps, if the theme utilizes the contact form functionality to other matters such as widgets and custom pages (contact us page) it can be also presented via a shortcode?<div><div><br></div><div><br><br><div class="gmail_quote">
On Sat, Dec 31, 2011 at 5:06 AM, Daniel Fenn <span dir="ltr"><<a href="mailto:danielx386@gmail.com">danielx386@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+1 Chip<br>
<div class="im"><br>
On 31/12/2011, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> What happens to that *content* when the user switches Themes? Buh-bye<br>
> contact form, Google chart, etc.<br>
><br>
> Those shortcodes really belong in Plugins. They are content creation, not<br>
> content presentation.<br>
><br>
> Chip<br>
><br>
> On Fri, Dec 30, 2011 at 8:48 PM, Emil Uzelac <<a href="mailto:emil@themeid.com">emil@themeid.com</a>> wrote:<br>
><br>
>> Not sure, this was a quick scan-over that's all. I personally don't see<br>
>> anything wrong with the usage itself if they were error-free.<br>
>><br>
>> Emil<br>
>><br>
>><br>
</div>>> *----*<br>
>> *Emil Uzelac* | ThemeID | T: <a href="tel:224-444-0006" value="+12244440006">224-444-0006</a> | Twitter: @EmilUzelac | E:<br>
<div class="im">>> <a href="mailto:emil@themeid.com">emil@themeid.com</a> | <a href="http://themeid.com" target="_blank">http://themeid.com</a><br>
>> Make everything as simple as possible, but not simpler. - Albert Einstein<br>
>><br>
>><br>
>><br>
>> On Fri, Dec 30, 2011 at 7:44 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>>wrote:<br>
>><br>
>>> Why is a Google Chart shortcode included in a *Theme*, rather than in a<br>
>>> Plugin?<br>
>>><br>
>>> Chip<br>
>>><br>
>>> On Fri, Dec 30, 2011 at 12:27 AM, Emil Uzelac <<a href="mailto:emil@themeid.com">emil@themeid.com</a>> wrote:<br>
>>><br>
>>>> Reviewers,<br>
>>>><br>
>>>> In regards to:<br>
>>>> <a href="http://make.wordpress.org/themes/2011/12/15/getting-the-review-queue-back-on-track/and" target="_blank">http://make.wordpress.org/themes/2011/12/15/getting-the-review-queue-back-on-track/and</a><br>
>>>> <a href="http://codex.wordpress.org/Theme_Review#Code_Quality" target="_blank">http://codex.wordpress.org/Theme_Review#Code_Quality</a> as well, can we<br>
>>>> also make sure that<br>
</div>>>>> Shortcodes<<a href="http://codex.wordpress.org/Shortcode_API" target="_blank">http://codex.wordpress.org/Shortcode_API</a>>are checked as well?<br>
>>>> Shortcodes can produce undefined<br>
>>>> errors <<a href="http://php.net/manual/en/function.isset.php" target="_blank">http://php.net/manual/en/function.isset.php</a>> and i.e. Theme<br>
>>>> Check <<a href="http://wordpress.org/extend/plugins/theme-check/" target="_blank">http://wordpress.org/extend/plugins/theme-check/</a>> will find<br>
<div class="im">>>>> them, however only if you actually use the shortcodes on any given<br>
>>>> page/post. Good example is <a href="http://pastebin.com/FEGz56vu" target="_blank">http://pastebin.com/FEGz56vu</a> (Google Chart)<br>
>>>> all* Themes in repository using this or similar code will have undefined<br>
>>>> error(s). This is only an example. Some will say that this is harmless,<br>
>>>> however we still need error free Themes :)<br>
>>>><br>
>>>> Thank you all for your help and Happy Holidays!<br>
>>>><br>
>>>> Emil<br>
>>>><br>
</div>>>>> *----*<br>
>>>> *Emil Uzelac* | ThemeID | T: <a href="tel:224-444-0006" value="+12244440006">224-444-0006</a> | Twitter: @EmilUzelac | E:<br>
<div class="im HOEnZb">>>>> <a href="mailto:emil@themeid.com">emil@themeid.com</a> | <a href="http://themeid.com" target="_blank">http://themeid.com</a><br>
>>>> Make everything as simple as possible, but not simpler. - Albert<br>
>>>> Einstein<br>
>>>><br>
>>>><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>
>>>><br>
>>><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>
>>><br>
>><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>
>><br>
><br>
<br>
<br>
</div><span class="HOEnZb"><font color="#888888">--<br>
Regards,<br>
Daniel Fenn<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div></div></div>