[theme-reviewers] Question about removing default widgets

[Justin Tadlock]

1) It's a new widget, so you'd need to add it to the sidebar.

2) I don't understand.

On 2/28/2013 9:03 PM, Josh Pollock wrote:
> Two clarifying questions:
>
> 1) Do the upgraded widgets need to work automatically? Ie if I ad the 
> archive widget while using twentytwelve and switch to the theme I'm 
> reviewing, which has a custom archive widget, is it OK that I no 
> longer have the archive widget in my sidebar and I have to ad the 
> custom one?
> 2) Do all widgets that are reregistered need to be removed?
>
>
> On Thu, Feb 28, 2013 at 9:15 PM, Emil Uzelac <emil at uzelac.me 
> <mailto:emil at uzelac.me>> wrote:
>
>     If others are good with
>     http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009455.html
>
>     I am as well :)
>
>     Emil
>
>
>     On Thu, Feb 28, 2013 at 8:01 PM, Daniel Fenn <danielx386 at gmail.com
>     <mailto:danielx386 at gmail.com>> wrote:
>
>         Just to check my understanding, it's ok for me to replace the
>         search
>         widget and replace it with a better one?
>
>
>
>
>
>         On Fri, Mar 1, 2013 at 12:56 PM, Justin Tadlock
>         <justin at justintadlock.com <mailto:justin at justintadlock.com>>
>         wrote:
>         > It seemed pretty definitive to me since several us agreed on
>         what was
>         > allowed and wrote up a new guideline.  I thought we had
>         already added it to
>         > the rest of the Theme Review Guidelines.  Otherwise, I
>         would've made a note
>         > that we forgot to add it.
>         >
>         >
>         > On 2/28/2013 7:06 PM, Emil Uzelac wrote:
>         >
>         > Not really sure if this was decided or not, but we talked
>         about this for
>         > sure.
>         > Please see:
>         >
>         http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009455.html
>         >
>         >
>         > On Thu, Feb 28, 2013 at 6:26 PM, Justin Tadlock
>         <justin at justintadlock.com <mailto:justin at justintadlock.com>>
>         > wrote:
>         >>
>         >> It is OK.  This was decided by the theme review team last year:
>         >>
>         http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009450.html
>         >>
>         >>
>         >> On 2/28/2013 6:18 PM, Paul Appleyard wrote:
>         >>>
>         >>> I thought it was OK to extend core functionality - as long
>         as it RETAINED
>         >>> the original functionality; ie didn't break when they
>         switched themes. So,
>         >>> replacing a widget with a custom one of the same name that
>         had the original
>         >>> functionality but with some added powers.
>         >>>
>         >>> Paul
>         >>>
>         >>> On 1/03/2013 9:34 AM, Otto wrote:
>         >>>>
>         >>>> On Thu, Feb 28, 2013 at 5:14 PM, Justin Tadlock
>         >>>> <justin at justintadlock.com
>         <mailto:justin at justintadlock.com>> wrote:
>         >>>>>
>         >>>>> I disagree.  If we don't want developers ...
>         >>>>
>         >>>> There is more than one type of developer.
>         >>>>
>         >>>> Removing widgets makes perfect sense to be available for
>         plugins
>         >>>> territory. Doesn't make sense for themes. Yet another form of
>         >>>> vendor-lock-in.
>         >>>>
>         >>>> -Otto
>         >>>> _______________________________________________
>         >>>> theme-reviewers mailing list
>         >>>> theme-reviewers at lists.wordpress.org
>         <mailto:theme-reviewers at lists.wordpress.org>
>         >>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>         >>>
>         >>>
>         >>> _______________________________________________
>         >>> theme-reviewers mailing list
>         >>> theme-reviewers at lists.wordpress.org
>         <mailto:theme-reviewers at lists.wordpress.org>
>         >>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>         >>
>         >>
>         >> _______________________________________________
>         >> theme-reviewers mailing list
>         >> theme-reviewers at lists.wordpress.org
>         <mailto:theme-reviewers at lists.wordpress.org>
>         >> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>         >
>         >
>         >
>         >
>         > _______________________________________________
>         > theme-reviewers mailing list
>         > theme-reviewers at lists.wordpress.org
>         <mailto:theme-reviewers at lists.wordpress.org>
>         > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>         >
>         >
>         >
>         > _______________________________________________
>         > theme-reviewers mailing list
>         > theme-reviewers at lists.wordpress.org
>         <mailto:theme-reviewers at lists.wordpress.org>
>         > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>         >
>         _______________________________________________
>         theme-reviewers mailing list
>         theme-reviewers at lists.wordpress.org
>         <mailto:theme-reviewers at lists.wordpress.org>
>         http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
>
>     _______________________________________________
>     theme-reviewers mailing list
>     theme-reviewers at lists.wordpress.org
>     <mailto: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/20130228/2f21ca4d/attachment-0001.htm>