[theme-reviewers] Shortcodes with the theme

Sat Mar 2 04:38:44 UTC 2013

Hey cant we generate shortcode from the theme itself despite using third
party plugin?

On Sat, Mar 2, 2013 at 2:22 AM, <theme-reviewers-request at lists.wordpress.org
> wrote:

> Send theme-reviewers mailing list submissions to
>         theme-reviewers at lists.wordpress.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> or, via email, send a message with subject or body 'help' to
>         theme-reviewers-request at lists.wordpress.org
>
> You can reach the person managing the list at
>         theme-reviewers-owner at lists.wordpress.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of theme-reviewers digest..."
>
>
> Today's Topics:
>
>    1. Re: Is my theme correctly submitted? (Chip Bennett)
>    2. Re: Theme Vs Plugin Territory (Thomas from ThemeZee)
>    3. Re: Theme Vs Plugin Territory (Chip Bennett)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 1 Mar 2013 14:30:45 -0500
> From: Chip Bennett <chip at chipbennett.net>
> Subject: Re: [theme-reviewers] Is my theme correctly submitted?
> To: "[theme-reviewers]" <theme-reviewers at lists.wordpress.org>
> Message-ID:
>         <
> CAPdLKqdy-pC3cOaorQz9+cUKG+Xfj72m2ph1zFRePqJmGngfGg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Then I would say that the upload probably did not succeed. On a successful
> upload, you will see a "success" response from the uploader, and you should
> also receive an email indicating that a ticket has been created in
> Theme-Trac for your Theme. Try to upload again, and note the response from
> the uploader.
>
>
> On Fri, Mar 1, 2013 at 2:07 PM, Agentur Strau? <
> agentur.strauss at googlemail.com> wrote:
>
> > No I don't
> >
> > Von meinem iPhone gesendet
> >
> > Am 01.03.2013 um 20:00 schrieb Chip Bennett <chip at chipbennett.net>:
> >
> > Hi Philipp,
> >
> > Did you receive an email regarding creation of a ticket in Theme-Trac?
> >
> >
> > On Fri, Mar 1, 2013 at 1:56 PM, Agentur Strau? <
> > agentur.strauss at googlemail.com> wrote:
> >
> >> Hello @all, for a few Weeks I have submitted The theme named
> >> guenterstrauss. Was this theme correctly submitted? Best Regards
> >>
> >> Philipp
> >>
> >> Von meinem iPhone gesendet
> >>
> >> Am 01.03.2013 um 19:36 schrieb Chip Bennett <chip at chipbennett.net>:
> >>
> >> That's always been the case, whether or not the non-GPL-compatible
> >> Themes/Plugins were distributed via ThemeForest or anywhere else.
> >>
> >> Also, Theme URI should *not* be a TF link. Theme URI cannot be used
> >> solely to link to an Upsell Theme. Theme URI, if linked, must be a
> resource
> >> for the free version being hosted in the Directory.
> >>
> >>
> >> On Fri, Mar 1, 2013 at 1:11 PM, Merci Javier <mercijavier at gmail.com
> >wrote:
> >>
> >>>
> >>>
> >>> On Thu, Feb 28, 2013 at 7:22 PM, Chip Bennett <chip at chipbennett.net
> >wrote:
> >>>
> >>>> I'm going to go ahead and say that, once the 100% GPL license is
> >>>> available, Theme developers who use that license option for all their
> >>>> ThemeForest-hosted Themes/Plugins would be welcome to advertise those
> >>>> ThemeForest-hosted Themes/Plugins.
> >>>>
> >>>> (Consider that an official statement, unless/until it is superseded by
> >>>> someone above the pay
> >>>>
> >>>
> >>> "all their TF hosted themes/plugins"
> >>> - So going forward,. if some of the author's themes are not GPL, they
> >>> cannot use TF theme doc link as Theme URL?
> >>>
> >>> _______________________________________________
> >>> 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/20130301/933ae2c4/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 1 Mar 2013 21:49:39 +0100
> From: Thomas from ThemeZee <contact at themezee.com>
> Subject: Re: [theme-reviewers] Theme Vs Plugin Territory
> To: theme-reviewers at lists.wordpress.org
> Message-ID:
>         <CAHfybZ0PikgT5H7HhgQ0u_Tjo2dAZjs06B3xvzftEUAK9ZQ=
> 0g at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Okay, I always thought Custom Post Types in themes are okay. I think the
> Guidlines should clearly state that CPTs are not allowed.
>
> I'm currently developing a theme with a simple image slideshow and wanted
> to use CPT for that. Since there are some themes in the directory with
> image slideshows, can someone tell me what is the best way to include an
> image slider?
>
> I mean I could use post meta keys or theme options to let users define
> their images, but that would make no difference to CPTs. If the user
> changes the theme he will lose that content. I understand the "generation
> or definition of user content" is forbidden point and it makes totally
> sense, but in my opinion defining a few images within a theme should be
> fine. (that's more presentation than functionality).
>
> And using CPTs for an image slideshow seems to be the most powerful and
> elegant way, or am I wrong??
>
> Best Regards,
> Thomas
>
>
> 2013/3/1 Chip Bennett <chip at chipbennett.net>
>
> > Custom Post Types are, by definition and design, intended for "generation
> > or definition of user content", and as such are explicitly Plugin
> > territory, as per the Guidelines.
> >
> > If a user creates content using a Theme-registered CPT, then when that
> > user switches Themes, that content disappears. (It's there in the
> database,
> > but no longer exposed to the user, either in the WordPress admin, or in
> the
> > site front end; to them, that content is simply gone.) Thus, CPTs
> represent
> > a form of Theme "lock-in" and are not allowed.
> >
> > Special-case Themes that use CPTs can be considered on a case-by-case
> > basis.
> >
> >
> > On Fri, Mar 1, 2013 at 1:43 PM, rabin shrestha <sun_ravi90 at yahoo.com
> >wrote:
> >
> >> Hi,
> >> I am a bit of confused on theme vs plugin territory. Recently my theme
> >> was rejected because of the use of CPT in my theme the reason was that
> it's
> >> plugin territory. I know that CPT is better suited to plugin but I
> didn't
> >> know that it was a required case. I have seen themes on WordPress
> >> repository that have registered multiple CPT and being approved. I am
> not
> >> saying that some X theme was approved, why not Y theme is approved for
> same
> >> case. My question is,It is strictly prohibited to use CPT inside theme.
> Is
> >> it a required case or is it a recommended case. If using CPT is
> completely
> >> prohibited then I think writing it down on Theme review guidelines will
> >> clear out the confusion. Though Prensentation Vs Functionality might
> cover
> >> this but those words are some what vague.
> >>
> >> _______________________________________________
> >> 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/20130301/9291d655/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 3
> Date: Fri, 1 Mar 2013 15:52:02 -0500
> From: Chip Bennett <chip at chipbennett.net>
> Subject: Re: [theme-reviewers] Theme Vs Plugin Territory
> To: "[theme-reviewers]" <theme-reviewers at lists.wordpress.org>
> Message-ID:
>         <
> CAPdLKqcMjCsZFpf-cyH-p9TJ34o64-P-q33Lehg4FbFUQ6R+9g at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I would recommend using post custom meta data for querying specific posts
> to include in featured sliders. That custom post meta is specific to your
> Theme, and if the user switches Themes, both your Theme's slider and the
> custom post meta that your Theme used to query posts for the slider are
> gone - but the original user content is retained.
>
> If you use a CPT to define slider images, then when the user switches
> Themes, the underlying user content - i.e. the images themselves - are
> gone.
>
>
> On Fri, Mar 1, 2013 at 3:49 PM, Thomas from ThemeZee
> <contact at themezee.com>wrote:
>
> > Okay, I always thought Custom Post Types in themes are okay. I think the
> > Guidlines should clearly state that CPTs are not allowed.
> >
> > I'm currently developing a theme with a simple image slideshow and wanted
> > to use CPT for that. Since there are some themes in the directory with
> > image slideshows, can someone tell me what is the best way to include an
> > image slider?
> >
> > I mean I could use post meta keys or theme options to let users define
> > their images, but that would make no difference to CPTs. If the user
> > changes the theme he will lose that content. I understand the "generation
> > or definition of user content" is forbidden point and it makes totally
> > sense, but in my opinion defining a few images within a theme should be
> > fine. (that's more presentation than functionality).
> >
> > And using CPTs for an image slideshow seems to be the most powerful and
> > elegant way, or am I wrong??
> >
> > Best Regards,
> > Thomas
> >
> >
> > 2013/3/1 Chip Bennett <chip at chipbennett.net>
> >
> >> Custom Post Types are, by definition and design, intended for
> "generation
> >> or definition of user content", and as such are explicitly Plugin
> >> territory, as per the Guidelines.
> >>
> >> If a user creates content using a Theme-registered CPT, then when that
> >> user switches Themes, that content disappears. (It's there in the
> database,
> >> but no longer exposed to the user, either in the WordPress admin, or in
> the
> >> site front end; to them, that content is simply gone.) Thus, CPTs
> represent
> >> a form of Theme "lock-in" and are not allowed.
> >>
> >> Special-case Themes that use CPTs can be considered on a case-by-case
> >> basis.
> >>
> >>
> >> On Fri, Mar 1, 2013 at 1:43 PM, rabin shrestha <sun_ravi90 at yahoo.com
> >wrote:
> >>
> >>> Hi,
> >>> I am a bit of confused on theme vs plugin territory. Recently my theme
> >>> was rejected because of the use of CPT in my theme the reason was that
> it's
> >>> plugin territory. I know that CPT is better suited to plugin but I
> didn't
> >>> know that it was a required case. I have seen themes on WordPress
> >>> repository that have registered multiple CPT and being approved. I am
> not
> >>> saying that some X theme was approved, why not Y theme is approved for
> same
> >>> case. My question is,It is strictly prohibited to use CPT inside
> theme. Is
> >>> it a required case or is it a recommended case. If using CPT is
> completely
> >>> prohibited then I think writing it down on Theme review guidelines will
> >>> clear out the confusion. Though Prensentation Vs Functionality might
> cover
> >>> this but those words are some what vague.
> >>>
> >>> _______________________________________________
> >>> 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/20130301/f3485ec8/attachment.htm
> >
>
> ------------------------------
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
> End of theme-reviewers Digest, Vol 34, Issue 18
> ***********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130302/cd78b827/attachment-0001.htm>