[theme-reviewers] Unregistering default widgets

[Chip Bennett]

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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120601/447590f7/attachment.htm>