<div dir="ltr">Why not just release it as a Plugin, and let any user of any Theme make use of such handy shortcodes?</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Mar 16, 2013 at 7:35 PM, Josh Pollock <span dir="ltr"><<a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">So one of the reasons I haven't submitted a theme I'm working on is it has shortcodes that allow for creating responsive columns in the post editor. For instance: [one third]content[/one third] puts that content in a 4 column wide div, as the theme uses a 12 column grid. I agree this type of shortcode shouldn't be allowed, because when the user switches themes they'd be left with all those random shortcodes showing up as plain text.<div>
<br></div><div>But what if I included a function in my theme that was hooked to switch_theme that did made WordPress to a mySQL query that replaced the opening shortcode with <p> and the closing shortcode with </p>.</div>
<div>That could be done with something like UPDATE wp_posts SET post_content = REPLACE ( post_content, '[one third]', '<p>' );</div><div><br></div><div>Hypothetically if I figured out how to get WordPress to do the mySQL the right way, would this scheme make this type of shortcode that is designed to be used in the post editor acceptable?</div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Mar 16, 2013 at 2:57 PM, 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"><div dir="ltr">The determining factor is: where are the shortcodes intended to be used.<div><br></div><div>If the shortcodes are intended to be used in the post content, then they are not allowed.</div>
<div><br></div><div>
If the shortcodes are intended to be used in other places in the template (footer, sidebar, etc.) then they are acceptable.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Sat, Mar 16, 2013 at 2:51 PM, Bruce Wampler <span dir="ltr"><<a href="mailto:weavertheme@gmail.com" target="_blank">weavertheme@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>I'm working on a new theme, and would like to clear up what might or might not be acceptable for shortocodes.<br>
<br>
I know that shortcode are really discouraged because at the least they will leave undefined [theme_shortcode] text if the theme is switched.<br>
<br>But I also got the impression there is room for some theme specific shortcodes. Where is the line? Some specific examples I am struggling with (just using generic 'theme' as a name):<br><br>[theme_info] - shows diagnostic information about the theme - this would seem ok as it serves a possibly useful diagnostic function very theme specific.<br>
<br>[theme_show/hide_if_mobile] - Show or hide content depending on desktop/mobile view. Many users want this capability, and it seems really related to how the theme works on mobile views. It could be done with @media and settings for transition points, I suppose, but it really seems the theme is in control of those decisions.<br>
<br>[theme_show_posts options='xxx'] - Show some posts on a page or sidebar. This capability is also very popular with users. To function correctly, it really need to know how a theme formats posts, so separating it from the theme would lead to showing content that doesn't match the rest of the theme. (Same logic could apply to RSS feeds)<br>
<br>[theme_menu] - display menus in alternate locations in format that matches standard theme menu.<br><br>-----<br>I'm especially having difficulties imagining how to write a plugin version of a [theme_show_posts] shortcode that could work across themes and provide any kind styling consistent with the theme.<br>
<br>So I'm curious if any of the higher ups here have an opinion on what kind of shortcode would be acceptable to include with new themes.<span><font color="#888888"><br><br>Bruce Wampler<br><br><br><br>
<br>
</font></span><br></div></div><div>_______________________________________________<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></div></blockquote></div><br></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><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>