unsubscribe!
On Thu, Mar 25, 2010 at 5:00 AM, <[email protected]> wrote: > Send wp-testers mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.automattic.com/mailman/listinfo/wp-testers > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of wp-testers digest..." > > > Today's Topics: > > 1. Re: "Menus" broken with today's build (03-23-10) (Kirk M) > 2. Re: "Menus" broken with today's build (03-23-10) (Kirk M) > 3. Add Option and uninstall (due chiacchiere) > 4. Re: Add Option and uninstall (Andrew Nacin) > 5. Re: Add Option and uninstall (due chiacchiere) > 6. Re: Add Option and uninstall (Peter Westwood) > 7. Re: "Menus" broken with today's build (03-23-10) (Andrew Nacin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 24 Mar 2010 10:24:35 -0400 > From: Kirk M <[email protected]> > Subject: Re: [wp-testers] "Menus" broken with today's build (03-23-10) > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > To all, > > Please disregard problem #3 in my original post. Clicking on "Save Menu" > at the top of the sidebar after changes are made does save the new menu > configuration. Just by habit I expect either a "Save Changes" type > button at the bottom of the page or, like the Widgets page, have any > changes save automatically as soon as there made. I realize that's a > mistake on my part and I should have checked more closely > > Numbers 1 and 2 are still valid although I was able to clear the board > so to speak and redo my menus as before. > > Happy bug hunting. > > On 03/23/2010 10:08 PM, Paul Robinson wrote: >> No problems for me so far with the latest build. Sorry. :( >> >> Just out of curiosity are there any docs or anything (basic or >> detailed) on how to develop using the new menu system? I kinda got >> there by trial and error (and reading the comments above the >> functions). >> >> On 24 March 2010 00:28, Kirk M<[email protected]> wrote: >>> Hi all, >>> >>> In my "Main" menu bar in the 2010 theme, I had 2 pages (About and Contact) >>> and 2 drop down menus ("Ye Olde Blogroll" and "Categories") set up via the >>> new (Woo) "Menus" which has been working real well until today's build which >>> did two things: >>> >>> 1. It took every single item in my "Main" menu bar regardless of >>> classification meaning pages, drop down menu titles and drop down menu items >>> and made each one it's own individual entry in the Main menu bar. This put >>> 15 separate items in the Main menu bar instead of the instead the normal 4. >>> >>> 2. It removed all internal links (About and Contact pages) and external urls >>> (blogroll) associated with each item in the Main menu bar. >>> >>> 3. Changing menus and menu items in the "Appearances/Menus" admin page no >>> longer saves the changes. For example, deleting every page, menu and menu >>> item in "Menus" (leaving it with only the "Main" entry) changes nothing in >>> the front end meaning the site itslelf. If I navigate away from the >>> "Appearances/Menus" admin page and then back again, all the original >>> (incorrect) entries are still there even though I deleted all of them >>> previously. In essence, "Woo Menus" no longer functions. >>> >>> Unfortunately, there's no entries in any error logs so it's difficult for me >>> to carry this any firther as I wouldn't know where to begin looking. >>> >>> Can anyone else verify this please? (I just love testing, don't you?) ;-) >>> _______________________________________________ >>> wp-testers mailing list >>> [email protected] >>> http://lists.automattic.com/mailman/listinfo/wp-testers >>> >> _______________________________________________ >> wp-testers mailing list >> [email protected] >> http://lists.automattic.com/mailman/listinfo/wp-testers > > > ------------------------------ > > Message: 2 > Date: Wed, 24 Mar 2010 10:42:38 -0400 > From: Kirk M <[email protected]> > Subject: Re: [wp-testers] "Menus" broken with today's build (03-23-10) > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > "Please though, no "it just doesn't work" tickets" > > Wouldn't think of it. ;-) > > The problem I was referring to (please disregard #3--mistake on my part) > probably wouldn't be worth a ticket anyway since it was just the act of > updating to the latest nightly that caused it with no errors in the > logs. Pretty scanty info to go on. > > I think one of the problems is that in order to setup up say, Categories > and Blogroll type drop down menus on the main menu bar is that there's > no way to set a top menu title under which the drop down menu items > reside (Top level menu title = "Categories" and "Blogroll" in this case). > > I know that sounds kind of obvious but as it stands now, for categories > I have to create an new empty category called (surprisingly enough) > "Categories", add that to my "Main" menu and then list (drag) all my > "real" categories under it. With the "Blogroll" I've been creating an > empty page called...er..."Blogroll", added the page to the "Main" menu > and then adding my actual blog roll links via the "Custom Links" section > in the "Menus" sidebar and then dragging and dropping them onto the > "Blogroll" page. This, of course, lists them under "Blogroll" in the > "Main" menu bar under the header image in the 2010 theme. > > I'm probably doing this all wrong but I'm not seeing another way to do > it at the moment but as you said, Menus are very much a work in progress > right now. > > And sorry about the long post here. I'm real wordy that way. :D > > On 03/24/2010 12:27 AM, Andrew Nacin wrote: >> That patch was committed on March 22. >> http://core.trac.wordpress.org/changeset/13802 >> >> Menus remain a work in progress. I encourage the submission of >> specific bug reports with full steps to reproduce (do a screencast if >> you find that best). Head over to Trac and use the Menus component and >> 3.0 milestone. >> >> Please though, no "it just doesn't work" tickets. Let us know exactly >> what is buggy and we will work to fix it. :-) >> >> >> On 3/24/10, Will Anderson<[email protected]> wrote: >>> Yeah, the menu manager has been screwed up for about a week now. I think >>> Ptah Dunbar submitted a new patch (he's been the main dev on menus), but I >>> don't remember seeing an SVN commit for it yet. >>> >>> Here's the patch: >>> http://core.trac.wordpress.org/attachment/ticket/11817/menus_awesomesauce_patch.diff >>> >>> Haven't looked at it too closely, but it'll hopefully fix menus. >>> _______________________________________________ >>> wp-testers mailing list >>> [email protected] >>> http://lists.automattic.com/mailman/listinfo/wp-testers >>> >> _______________________________________________ >> wp-testers mailing list >> [email protected] >> http://lists.automattic.com/mailman/listinfo/wp-testers > > > ------------------------------ > > Message: 3 > Date: Wed, 24 Mar 2010 14:17:49 -0400 > From: due chiacchiere <[email protected]> > Subject: [wp-testers] Add Option and uninstall > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi all, > > I'm working on a plugin which needs to store some data in the table > "wp_options", and to create some new tables as well. I have two questions: > > 1) Why calling add_option('myoption', array(), 'no') creates a new entry > that has the 'autoload' field set to YES in the database? Am I doing > something wrong? > > 2) Since I want to be a 'good developer', I added the uninstall function > to be executed whenever the user decides to remove this plugin from his > WP box. So I have this method inside my class: > > public function uninstall() { > global $wpdb; > > // Goodbye data... > $wpdb->query("DROP TABLE IF EXISTS `tablename`"); > > // Goodbye options... > delete_option('myoption'); > } > > And then it's hooked like this > > register_uninstall_hook( __FILE__, array( &$myclass, 'uninstall' ) ); > > I've tried both with 2.9 and 3.0alpha, and the table is still there > after I uninstall the plugin via the admin interface. > > Thanks for your time, > dino. > > > ------------------------------ > > Message: 4 > Date: Wed, 24 Mar 2010 14:52:20 -0400 > From: Andrew Nacin <[email protected]> > Subject: Re: [wp-testers] Add Option and uninstall > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Your post here is probably more suited for the wp-hackers list or, more so, > the support forums. wp-testers is for announcements regarding alpha/beta > releases and what we need tested (and discussions over whether something is > a bug before actually posting it to Trac). > > Briefly, one of your questions: > > >> Why calling add_option('myoption', array(), 'no') creates a new entry that >> has the 'autoload' field set to YES in the database? Am I doing something >> wrong? > > > Autoload for add_option() is the fourth argument, not the third. The third > doesn't do anything. Turn on WP_DEBUG and you'll get a notice that you're > using a deprecated argument. > > > ------------------------------ > > Message: 5 > Date: Wed, 24 Mar 2010 15:13:15 -0400 > From: due chiacchiere <[email protected]> > Subject: Re: [wp-testers] Add Option and uninstall > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Thank you, that solved the issue. I'll post my question about the > uninstall thing on the wp-hackers list, even if I managed to make it > work using the uninstall.php file, instead of the hook ;) > > On 3/24/2010 2:52 PM, Andrew Nacin wrote: >> Your post here is probably more suited for the wp-hackers list or, more so, >> the support forums. wp-testers is for announcements regarding alpha/beta >> releases and what we need tested (and discussions over whether something is >> a bug before actually posting it to Trac). >> >> Briefly, one of your questions: >> >> >> >>> Why calling add_option('myoption', array(), 'no') creates a new entry that >>> has the 'autoload' field set to YES in the database? Am I doing something >>> wrong? >>> >> >> Autoload for add_option() is the fourth argument, not the third. The third >> doesn't do anything. Turn on WP_DEBUG and you'll get a notice that you're >> using a deprecated argument. >> _______________________________________________ >> wp-testers mailing list >> [email protected] >> http://lists.automattic.com/mailman/listinfo/wp-testers >> > > > ------------------------------ > > Message: 6 > Date: Wed, 24 Mar 2010 22:11:02 +0000 > From: Peter Westwood <[email protected]> > Subject: Re: [wp-testers] Add Option and uninstall > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > > On 24 Mar 2010, at 18:17, due chiacchiere wrote: > >> Hi all, >> >> I'm working on a plugin which needs to store some data in the table >> "wp_options", and to create some new tables as well. I have two questions: >> >> 1) Why calling add_option('myoption', array(), 'no') creates a new entry >> that has the 'autoload' field set to YES in the database? Am I doing >> something wrong? >> >> 2) Since I want to be a 'good developer', I added the uninstall function to >> be executed whenever the user decides to remove this plugin from his WP box. >> So I have this method inside my class: >> >> public function uninstall() { >> global $wpdb; >> >> // Goodbye data... >> $wpdb->query("DROP TABLE IF EXISTS `tablename`"); >> >> // Goodbye options... >> delete_option('myoption'); >> } >> >> And then it's hooked like this >> >> register_uninstall_hook( __FILE__, array( &$myclass, 'uninstall' ) ); >> >> I've tried both with 2.9 and 3.0alpha, and the table is still there after I >> uninstall the plugin via the admin interface. >> > > Without looking at the code I suspect this will be due to using a class > function for this hook when it is likely that when the hook is called the > class does not exist. > > From memory the activation/uninstall hooks can only work with functions not > class functions. > > Cheers > > Peter > -- > Peter Westwood > http://blog.ftwr.co.uk | http://westi.wordpress.com > C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5 > > > > ------------------------------ > > Message: 7 > Date: Wed, 24 Mar 2010 23:51:07 -0400 > From: Andrew Nacin <[email protected]> > Subject: Re: [wp-testers] "Menus" broken with today's build (03-23-10) > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > >> >> After updating my worpress installation, the frontend menu won't work >> anymore. While the hover effect still works as expected, the links won't. I >> went to the admin panel, to the menu page and found that in the one menu I'd >> created so far, the type of the menu items changed from 'page' to 'custom' >> (see the attached pic). I deleted the menu and created a new one. Back to >> the frontend of my website, I found everything was back to normal. The menu >> was now working as expected. Hope this helps. >> > > We changed around (a little) how menus were stored. It sounds like the > upgrade path probably mucked up a few things unfortunately. The alternative > would have been to clear out all menus on upgrade, but that didn't seem like > a very good idea. > > > ------------------------------ > > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > > > End of wp-testers Digest, Vol 61, Issue 28 > ****************************************** > _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
