<p>Ty</p>
<p><a href="http://www.google.com/chromebeta/what">www.google.com/chromebeta/what</a> a browser</p>
<p><blockquote type="cite">On Apr 23, 2010 8:56 AM, <<a href="mailto:wp-trac-request@lists.automattic.com">wp-trac-request@lists.automattic.com</a>> wrote:<br><br>Send wp-trac mailing list submissions to<br>
<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-trac" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-trac</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:wp-trac-request@lists.automattic.com">wp-trac-request@lists.automattic.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:wp-trac-owner@lists.automattic.com">wp-trac-owner@lists.automattic.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of wp-trac digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [WordPress Trac] #12994: Threaded Comments Breaks Layout<br>
in Twenty Ten Theme (WordPress Trac)<br>
2. Re: [WordPress Trac] #13088: update_usermeta() and<br>
update_user_meta() behave differently (WordPress Trac)<br>
3. Re: [WordPress Trac] #13045: Login: Add Classes for better<br>
plugin-support and change from <p> to <div> for more flexibility<br>
(WordPress Trac)<br>
4. Re: [WordPress Trac] #13088: update_usermeta() and<br>
update_user_meta() behave differently (WordPress Trac)<br>
5. Re: [WordPress Trac] #13045: Login: Add Classes for better<br>
plugin-support and change from <p> to <div> for more flexibility<br>
(WordPress Trac)<br>
6. [WordPress Trac] #13094: Super admins should be able to view<br>
spam, archived, deleted, etc. blogs. (WordPress Trac)<br>
7. Re: [WordPress Trac] #13094: Super admins should be able to<br>
view spam, archived, deleted, etc. blogs. (WordPress Trac)<br>
8. Re: [WordPress Trac] #13094: Super admins should be able to<br>
view spam, archived, deleted, etc. blogs. (WordPress Trac)<br>
9. Re: [WordPress Trac] #12008: OperationalError: database is<br>
locked (WordPress Trac)<br>
10. Re: [WordPress Trac] #12334: A series of typos/thinkos that<br>
should be fixed (WordPress Trac)<br>
11. April Discount #75894 (USA VIAGRA ®)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 23 Apr 2010 15:28:42 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #12994: Threaded Comments<br>
Breaks Layout in Twenty Ten Theme<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:057.bb54701516c97ac3ac800c29d071527e@lists.automattic.com">057.bb54701516c97ac3ac800c29d071527e@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#12994: Threaded Comments Breaks Layout in Twenty Ten Theme<br>
--------------------------+-------------------------------------------------<br>
Reporter: mrgtb | Owner: iammattthomas<br>
Type: defect (bug) | Status: assigned<br>
Priority: normal | Milestone: 3.0<br>
Component: Themes | Version: 3.0<br>
Severity: normal | Keywords:<br>
--------------------------+-------------------------------------------------<br>
<br>
Comment(by nacin):<br>
<br>
Replying to [comment:12 markmcwilliams]:<br>
> So we're good to be closed now, or still waiting for MT to review?<br>
I'll wait for MT here.<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/12994#comment:13" target="_blank">http://core.trac.wordpress.org/ticket/12994#comment:13</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 23 Apr 2010 15:29:19 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #13088: update_usermeta() and<br>
update_user_meta() behave differently<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:060.3ae8921aa2f641fa99740b893e364433@lists.automattic.com">060.3ae8921aa2f641fa99740b893e364433@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#13088: update_usermeta() and update_user_meta() behave differently<br>
--------------------------+-------------------------------------------------<br>
Reporter: mdawaffe | Owner:<br>
Type: defect (bug) | Status: closed<br>
Priority: normal | Milestone: 3.0<br>
Component: Users | Version: 3.0<br>
Severity: major | Resolution: fixed<br>
Keywords: meta |<br>
--------------------------+-------------------------------------------------<br>
<br>
Comment(by TobiasBg):<br>
<br>
{{{<br>
// For backward compatibility. See differences between update_user_meta()<br>
and deprecated update_user_meta().<br>
}}}<br>
<br>
I don't get this one :-) Is there a typo in one of the functions' names?<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/13088#comment:8" target="_blank">http://core.trac.wordpress.org/ticket/13088#comment:8</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 23 Apr 2010 15:31:02 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #13045: Login: Add Classes for<br>
better plugin-support and change from <p> to <div> for more<br>
flexibility<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:062.b381d0714a21bc2f233df36276adb421@lists.automattic.com">062.b381d0714a21bc2f233df36276adb421@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#13045: Login: Add Classes for better plugin-support and change from <p> to <div><br>
for more flexibility<br>
----------------------------+-----------------------------------------------<br>
Reporter: F J Kaiser | Owner:<br>
Type: enhancement | Status: new<br>
Priority: normal | Milestone: Unassigned<br>
Component: Administration | Version: 2.9.2<br>
Severity: minor | Keywords: dev-feedback 2nd-opinion<br>
----------------------------+-----------------------------------------------<br>
<br>
Comment(by F J Kaiser):<br>
<br>
Hi nacin and markmcwilliams and thanks for the help & feedback. To make it<br>
easier to take a look at the changes, i added comments (search for<br>
"change") in the next "patch" (file taken from 3.0-nightly build). It's<br>
just to give you a faster & easier overview about the changes (i really<br>
can't login to svn. It works with <a href="http://wp.org" target="_blank">wp.org</a> and the plugin-rep, but not for<br>
core - sry 'bout this, i'll find out another day).<br>
<br>
In general i just try to unbind the admin-color-scheme from the login-page<br>
as described in the other ticket.<br>
<br>
In detail i just changed a) stop calling admin-color-scheme b) login<br>
messages. But nothing inside the <form>, so wp_login_form() won't be<br>
affected (no need for changes) by login.css or wp-login.php. When you're<br>
talking about semantic value then the provided patch should do it. If you<br>
think it's not, then i'd suggest to not house the error-messages in a<br>
paragraph, but an <ul>. (And yes, i was talking about child-block-elements<br>
added by f/ex a plugin-author or later wp-versions).<br>
<br>
My only *real* goal is to get rid of the admin-color-scheme and the<br>
id="login_error" (should be class in my humble opinion), because it makes<br>
things a little bit hard for plugin-authors or people who try to style the<br>
login in their theme. The other changes are just additions i thought that<br>
could be useful.<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/13045#comment:7" target="_blank">http://core.trac.wordpress.org/ticket/13045#comment:7</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 23 Apr 2010 15:32:34 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #13088: update_usermeta() and<br>
update_user_meta() behave differently<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:060.ee61a16ecbbc4a951d000a20c5d7081d@lists.automattic.com">060.ee61a16ecbbc4a951d000a20c5d7081d@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#13088: update_usermeta() and update_user_meta() behave differently<br>
--------------------------+-------------------------------------------------<br>
Reporter: mdawaffe | Owner:<br>
Type: defect (bug) | Status: closed<br>
Priority: normal | Milestone: 3.0<br>
Component: Users | Version: 3.0<br>
Severity: major | Resolution: fixed<br>
Keywords: meta |<br>
--------------------------+-------------------------------------------------<br>
<br>
Comment(by nacin):<br>
<br>
(In [14196]) Fix typo in inline docs. props TobiasBg. see #13088<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/13088#comment:9" target="_blank">http://core.trac.wordpress.org/ticket/13088#comment:9</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 23 Apr 2010 15:40:01 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #13045: Login: Add Classes for<br>
better plugin-support and change from <p> to <div> for more<br>
flexibility<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:062.349a203602dbd085659d635f12f9bb9f@lists.automattic.com">062.349a203602dbd085659d635f12f9bb9f@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#13045: Login: Add Classes for better plugin-support and change from <p> to <div><br>
for more flexibility<br>
----------------------------+-----------------------------------------------<br>
Reporter: F J Kaiser | Owner:<br>
Type: enhancement | Status: new<br>
Priority: normal | Milestone: Unassigned<br>
Component: Administration | Version: 2.9.2<br>
Severity: minor | Keywords: dev-feedback 2nd-opinion<br>
----------------------------+-----------------------------------------------<br>
<br>
Comment(by nacin):<br>
<br>
> It's just to give you a faster & easier overview about the changes (i<br>
really can't login to svn. It works with <a href="http://wp.org" target="_blank">wp.org</a> and the plugin-rep, but<br>
not for core - sry 'bout this, i'll find out another day).<br>
You don't log in. Simply check out the repository.<br>
<br>
I diff'ed the changes, though I really don't see a point in the changes.<br>
Not to mention that it would break all existing styling by plugins.<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/13045#comment:8" target="_blank">http://core.trac.wordpress.org/ticket/13045#comment:8</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Fri, 23 Apr 2010 15:43:19 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: [wp-trac] [WordPress Trac] #13094: Super admins should be<br>
able to view spam, archived, deleted, etc. blogs.<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:047.9d60f598586f32caeb382e141adbffab@lists.automattic.com">047.9d60f598586f32caeb382e141adbffab@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#13094: Super admins should be able to view spam, archived, deleted, etc. blogs.<br>
--------------------------+-------------------------------------------------<br>
Reporter: ryan | Owner:<br>
Type: defect (bug) | Status: new<br>
Priority: normal | Milestone: 3.0<br>
Component: Multisite | Version:<br>
Severity: normal | Keywords:<br>
--------------------------+-------------------------------------------------<br>
ms_site_check() should allow super admins to view blogs marked as spammed,<br>
deleted, archived, etc. Adding an is_super_admin() check to<br>
ms_site_check() would require moving ms_site_check() lower in wp-<br>
settings.php until after init is fired. This would also allow adding<br>
actions/filters to ms_site_check(). The cost is that all of WP would be<br>
loaded before dying for these blogs.<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/13094" target="_blank">http://core.trac.wordpress.org/ticket/13094</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Fri, 23 Apr 2010 15:45:40 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #13094: Super admins should be<br>
able to view spam, archived, deleted, etc. blogs.<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:056.b85b0a1e022aca9cc1ce653463a6234b@lists.automattic.com">056.b85b0a1e022aca9cc1ce653463a6234b@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#13094: Super admins should be able to view spam, archived, deleted, etc. blogs.<br>
--------------------------+-------------------------------------------------<br>
Reporter: ryan | Owner:<br>
Type: defect (bug) | Status: new<br>
Priority: normal | Milestone: 3.0<br>
Component: Multisite | Version:<br>
Severity: normal | Keywords:<br>
--------------------------+-------------------------------------------------<br>
<br>
Comment(by nacin):<br>
<br>
> The cost is that all of WP would be loaded before dying for these blogs.<br>
<br>
I don't see that as much of an issue. It's not harming the performance of<br>
anything but the speed of a die message.<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/13094#comment:1" target="_blank">http://core.trac.wordpress.org/ticket/13094#comment:1</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Fri, 23 Apr 2010 15:47:56 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #13094: Super admins should be<br>
able to view spam, archived, deleted, etc. blogs.<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:056.73bd70f8d2ae106f33e07da52add8c67@lists.automattic.com">056.73bd70f8d2ae106f33e07da52add8c67@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#13094: Super admins should be able to view spam, archived, deleted, etc. blogs.<br>
--------------------------+-------------------------------------------------<br>
Reporter: ryan | Owner:<br>
Type: defect (bug) | Status: new<br>
Priority: normal | Milestone: 3.0<br>
Component: Multisite | Version:<br>
Severity: normal | Keywords:<br>
--------------------------+-------------------------------------------------<br>
<br>
Comment(by donncha):<br>
<br>
We definitely need to do this. It means that inactive blogs will load more<br>
of WP before dying but it's worth it for the convenience of<br>
administrators.<br>
<br>
The only issue with performance is when a blog is being DOSed but it'll be<br>
fast enough.<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/13094#comment:2" target="_blank">http://core.trac.wordpress.org/ticket/13094#comment:2</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Fri, 23 Apr 2010 15:49:53 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #12008: OperationalError:<br>
database is locked<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:060.a8f15c7fa8340fde1b90a916f54dd2b5@lists.automattic.com">060.a8f15c7fa8340fde1b90a916f54dd2b5@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#12008: OperationalError: database is locked<br>
---------------------------+------------------------------------------------<br>
Reporter: rfair404 | Owner: ryan<br>
Type: defect (bug) | Status: closed<br>
Priority: normal | Milestone:<br>
Component: WordPress.org | Version:<br>
Severity: normal | Resolution: fixed<br>
Keywords: |<br>
---------------------------+------------------------------------------------<br>
<br>
Comment(by nacin):<br>
<br>
Servers have been shifted, but we're still on sqlite, not mysql. It'll<br>
happen eventually though. No problems closing this.<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/12008#comment:4" target="_blank">http://core.trac.wordpress.org/ticket/12008#comment:4</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Fri, 23 Apr 2010 15:50:41 -0000<br>
From: "WordPress Trac" <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: Re: [wp-trac] [WordPress Trac] #12334: A series of<br>
typos/thinkos that should be fixed<br>
Cc: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID:<br>
<<a href="mailto:060.415439c3b58646dd7c7597a288ae0e67@lists.automattic.com">060.415439c3b58646dd7c7597a288ae0e67@lists.automattic.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
#12334: A series of typos/thinkos that should be fixed<br>
--------------------------+-------------------------------------------------<br>
Reporter: rlerdorf | Owner: nacin<br>
Type: defect (bug) | Status: accepted<br>
Priority: low | Milestone: 3.0<br>
Component: General | Version:<br>
Severity: normal | Keywords:<br>
--------------------------+-------------------------------------------------<br>
<br>
Comment(by nacin):<br>
<br>
No, still haven't gone through default_password_nag_edit_user.<br>
<br>
--<br>
Ticket URL: <<a href="http://core.trac.wordpress.org/ticket/12334#comment:6" target="_blank">http://core.trac.wordpress.org/ticket/12334#comment:6</a>><br>
WordPress Trac <<a href="http://core.trac.wordpress.org/" target="_blank">http://core.trac.wordpress.org/</a>><br>
WordPress blogging software<br>
<br>
<br>
------------------------------<br>
<br>
Message: 11<br>
Date: Fri, 23 Apr 2010 19:23:54 +0400<br>
From: USA VIAGRA ® <<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a>><br>
Subject: [wp-trac] April Discount #75894<br>
To: <a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
Message-ID: <20100424005611.2594.qmail@xp-150410449d38><br>
Content-Type: text/plain<br>
<br>
<a href="http://jqibyemc.ru?6440355560=wp-trac@lists.automattic.com" target="_blank">http://jqibyemc.ru?6440355560=wp-trac@lists.automattic.com</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
wp-trac mailing list<br>
<a href="mailto:wp-trac@lists.automattic.com">wp-trac@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-trac" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-trac</a><br>
<br>
<br>
End of wp-trac Digest, Vol 51, Issue 239<br>
****************************************<br>
</blockquote></p>