[theme-reviewers] WordPress Shortcodes

[Edward Caissie]

Although I understand and can relate to the ideas being put forward by
Chip, Emil's 2 cents make as much or more sense in the vein of the end-user
should be responsible for their own content which includes letting them
retain the option and responsibility of using shortcodes. As noted by
Robert, there are benefits to having custom widgets in a theme as they will
generally be properly tested for, or at least should be held accountable
to, adhering to the theme's overall aesthetics.

I would only further this by saying to allow the custom widget
functionality but also include sufficient (hello subjectivity *grin*)
documentation so the end-user understands what may happen if the theme is
changed to one that does not support these custom widgets.


Cais.


On Fri, Dec 30, 2011 at 10:44 PM, Emil Uzelac <emil at themeid.com> wrote:

> I see what you mean Chip, I really do, however we're stepping over user's
> responsibilities here. Same thing will happen with i.e. "Specific
> Templates", not to mention widgets etc. In a perfect world yes, it would be
> nice to separate them, but we should not limited to that, or better yet
> "force" things into plugin. User's responsibility is to manage their sites
> and author's should keep their codes up to date, it can't get easier!
>
> Just my 2¢ that's all,
> Emil
>
>
> *----*
> *Emil Uzelac* | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E:
> emil at themeid.com | http://themeid.com
> Make everything as simple as possible, but not simpler. - Albert Einstein
>
>
>
> On Fri, Dec 30, 2011 at 9:04 PM, Chip Bennett <chip at chipbennett.net>wrote:
>
>> What happens to that *content* when the user switches Themes? Buh-bye
>> contact form, Google chart, etc.
>>
>> Those shortcodes really belong in Plugins. They are content creation, not
>> content presentation.
>>
>> Chip
>>
>>
>> On Fri, Dec 30, 2011 at 8:48 PM, Emil Uzelac <emil at themeid.com> wrote:
>>
>>> Not sure, this was a quick scan-over that's all. I personally don't see
>>> anything wrong with the usage itself if they were error-free.
>>>
>>> Emil
>>>
>>>
>>> *----*
>>> *Emil Uzelac* | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E:
>>> emil at themeid.com | http://themeid.com
>>> Make everything as simple as possible, but not simpler. - Albert Einstein
>>>
>>>
>>>
>>> On Fri, Dec 30, 2011 at 7:44 PM, Chip Bennett <chip at chipbennett.net>wrote:
>>>
>>>> Why is a Google Chart shortcode included in a *Theme*, rather than in a
>>>> Plugin?
>>>>
>>>> Chip
>>>>
>>>> On Fri, Dec 30, 2011 at 12:27 AM, Emil Uzelac <emil at themeid.com> wrote:
>>>>
>>>>> Reviewers,
>>>>>
>>>>> In regards to:
>>>>> http://make.wordpress.org/themes/2011/12/15/getting-the-review-queue-back-on-track/and
>>>>> http://codex.wordpress.org/Theme_Review#Code_Quality as well, can we
>>>>> also make sure that Shortcodes<http://codex.wordpress.org/Shortcode_API>are checked as well? Shortcodes can produce undefined
>>>>> errors <http://php.net/manual/en/function.isset.php> and i.e. Theme
>>>>> Check <http://wordpress.org/extend/plugins/theme-check/> will find
>>>>> them, however only if you actually use the shortcodes on any given
>>>>> page/post. Good example is http://pastebin.com/FEGz56vu (Google
>>>>> Chart) all* Themes in repository using this or similar code will have
>>>>> undefined error(s). This is only an example. Some will say that this is
>>>>> harmless, however we still need error free Themes :)
>>>>>
>>>>> Thank you all for your help and Happy Holidays!
>>>>>
>>>>> Emil
>>>>>
>>>>> *----*
>>>>> *Emil Uzelac* | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E:
>>>>> emil at themeid.com | http://themeid.com
>>>>> Make everything as simple as possible, but not simpler. - Albert
>>>>> Einstein
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20111231/ad7d22e0/attachment.htm>