[theme-reviewers] Unregistering default widgets

[Philip M. Hofer (Frumph)]

@konstantine
Regardless of either method, deregistering or just making a new one, neither has any affect on anything other then well those particular widgets.   Sometimes the behavior of certain widgets it could be a good thing, like the archive dropdown, I have one that goes to the first post in the category selected instead of going to the archive page of all in the archive... 

Dunno, really.  This is a don’t care scenario since it doesn’t have a possibility to break anything or conflict.



From: Konstantin Obenland 
Sent: Friday, June 01, 2012 5:08 AM
To: theme-reviewers at lists.wordpress.org 
Subject: Re: [theme-reviewers] Unregistering default widgets

@chipbennett: 
You're referring to Oenology, right? 
Why are you deregistering the core Widgets, rather than just adding your custom ones? :)

@Frumph
What benefit does it have? Why not just add custom widgets to the existing ones?
I think it would affect user experience, as they might expect certain core widgets to be there, and all over sudden they're gone or their behavior changed.

Konstantin


On 01.06.2012, at 14:00, Philip M. Hofer (Frumph) wrote:


  Q. Does it affect any plugins or other stripends if someone did deregister and reregister their custom widgets?  
  A. No? (can’t think of any)



  From: Chip Bennett 
  Sent: Friday, June 01, 2012 4:43 AM
  To: theme-reviewers at lists.wordpress.org 
  Subject: Re: [theme-reviewers] Unregistering default widgets

  Actually, I use this. Mainly due to a lack of a better work-around (though I'm open to ideas). I needed to modify the container markup slightly, to implement the "show/hide" links for the Widgets. Rather than simply forking the core Widgets as *new* Widgets, I deregister the core Widgets, and then re-register my modified versions.  

  I don't mind using a different approach, if anyone has a good suggestion. I mainly just don't want to load jQuery just for such a simple effect.

  Chip


  On Fri, Jun 1, 2012 at 3:19 AM, Emil Uzelac <emil at themeid.com> wrote:

    I am pretty sure that this would be considered as "locking" the core functionalities and not really sure what would be the reason and scenario when author would unregister default widget and replace them with Theme-specific. If this is not in review and I can't find it either, well it should be for sure. Good eye Konstantin! 


    My 2c!



    Emil 


    On Fri, Jun 1, 2012 at 3:08 AM, Konstantin Obenland <konstantin at obenland.it> wrote:

      Hi all,

      I didn't find documentation on whether it is allowed for Theme authors to unregister default widgets.
      Is it?

      Thanks,
      Konstantin
      _______________________________________________
      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/20120601/c5c52f02/attachment-0001.htm>