<p dir="ltr">Got it, thank you very much! :)</p>
<p dir="ltr">Mattia Migliorini</p>
<div class="gmail_quote">On Aug 7, 2013 7:05 PM, "Justin Tadlock" <<a href="mailto:justin@justintadlock.com">justin@justintadlock.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    Why has this guideline not already been added?<br>
    <br>
    "Themes may OPTIONALLY unregister core Widgets. 
    If unregistered, Themes are REQUIRED to replace these Widgets with
    their own (extended) version."<br>
    <br>
    This has already been discussed and agreed on twice now.  Original
    threads:<br>
    <a href="http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/thread.html#9425" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/thread.html#9425</a><br>
    <a href="http://lists.wordpress.org/pipermail/theme-reviewers/2013-March/thread.html#12031" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/2013-March/thread.html#12031</a><br>
    <br>
    <div>On 8/7/2013 7:14 AM, Chip Bennett
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">I think we should recommend *not* replacing core
        Widgets in general. But I think other than the Text Widget, none
        represent generation - or potential loss - of user data. (Most
        are lists of Posts or Terms, in various contexts.) So IMHO the
        Text Widget would factor into presentation-vs-functionality,
        because if a user creates text content in a Text Widget, if that
        Widget is registered by the Theme (whether it replaces the core
        Text Widget or not), that user-created text data would be lost
        when the Theme is deactivated.
        <div>
          <br>
        </div>
        <div>Note: I have the same concern with some other
          Theme-registered Widgets, such as Ad Widgets; if the user adds
          an ad image or text, that content is then lost (well, buried
          in theme_mods).</div>
      </div>
      <div class="gmail_extra">
        <br>
        <br>
        <div class="gmail_quote">On Wed, Aug 7, 2013 at 3:49 AM, Philip
          M. Hofer (Frumph) <span dir="ltr"><<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</a>></span> wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            .. Isn't this the same as having shortcodes though?  since
            the new theme wouldn't have the ability to use it so the
            data is as said lost .. as the people who want shortcodes to
            be gone made a point as being the reason; just wondering if
            that's not pretty much the same.<br>
            <br>
            Not rehashing, just curious; because it's an interesting
            thought.<br>
            <br>
            <br>
            <br>
            -----Original Message----- From: Paul Appleyard<br>
            Sent: Wednesday, August 07, 2013 12:43 AM<br>
            To: Discussion list for WordPress theme reviewers.<br>
            Subject: Re: [theme-reviewers] Unregister core plugins
            <div>
              <div><br>
                <br>
                I would think that as long as the core widget
                functionality is<br>
                unaffected, it wouldn't be an issue; that is, if they
                change themes<br>
                there's no visible affect.<br>
                <br>
                Paul Appleyard<br>
                <br>
                On 7/08/2013 3:38 AM, Otto wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  I would say that it's generally a bad idea, because
                  people might get<br>
                  confused when their widgets disappear after changing
                  themes.<br>
                  <br>
                  Instead of replacing the core widgets, create your own
                  with the theme<br>
                  name in them. So instead of "Text" widget, you could
                  add one that says<br>
                  "Themename - Text" to show that it's specific to the
                  theme. Then<br>
                  people won't be surprised when it disappears on theme
                  changing.<br>
                  <br>
                  -Otto<br>
                  <br>
                  <br>
                  On Tue, Aug 6, 2013 at 11:55 AM, Mattia Migliorini
                  <<a href="mailto:deshack@ubuntu.com" target="_blank">deshack@ubuntu.com</a>>
                  wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    Hi all,<br>
                    In my theme (which is now under reviewing) I
                    unregistered a pair of core<br>
                    widgets in order to substitute them with my own
                    ones, because I needed to<br>
                    integrate them with Bootstrap.<br>
                    <br>
                    Is it allowed to unregister core plugins or not?<br>
                    <br>
                    Thank you,<br>
                    <br>
                    Mattia Migliorini<br>
                    <br>
                    <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>
                  _______________________________________________<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>
                </blockquote>
                <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>
                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>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
    </blockquote>
    <br>
  </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>