[wp-testers] Hosts that require setting FS_CHMOD_FILE and FS_CHMOD_DIR
Now that we have a fix for this - http://trac.wordpress.org/ticket/8478 I want to get some good documentation on the codex about this and also would like to build a list of hosts that we know require this to be setup. Could people feed back to me off-list a list of hosts they know need these setup and what they need setting to and then I will build up some documentation and publicity for this. thanks in advance westi -- Peter Westwood http://blog.ftwr.co.uk | http://westi.wordpress.com C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5 ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
[wp-testers] Version Bump
I'm seeing the version bump in 10096 in trac, but after upgrading I am still seeing 10073. -- Jim bRight Early -- http://brightandearlyblog.com Reclaim Conservatism -- http://reclaimconservatism.com/blog/ FloridImagine -- http://floridimagine.com/blog/ 4bauer.com (Blogs.4Bauer.com Forums.4Bauer.com Wiki.4Bauer.com) Need a gmail invite? Let me know! ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Version Bump
Same here - still seeing rev10073 on 2 different installs after updating
this AM. Database is showing the following for update_core:
O:8:stdClass:3:{s:7:updates;a:1:{i:0;O:8:stdClass:5:{s:8:response;s:11:development;s:3:url;s:34:http://wordpress.org/download/svn/;s:7:package;s:56:http://wordpress.org/nightly-builds/wordpress-latest.zip;s:7:current;s:5:2.6.5;s:6:locale;s:5:en_US;}}s:12:last_checked;i:1228651001;s:15:version_checked;s:13:2.7-RC1-10073;}
Kim
-
Jim Lynch wrote:
I'm seeing the version bump in 10096 in trac, but after upgrading I am still
seeing 10073.
___
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers
[wp-testers] bugs in wp27rc1 and newer
Hi, wp-testers. founded bugs in wp27rc1 and newer 1. if upload file in quick press (in DASHBOARD) - code of picture|file not added to post text and gallery not contain files too. in beta3 all wordk fine! 2. then useng pretty permalinks (example /%year%/%monthnum%/%postname%/) - url for attachments not converting - example http://site.com/?attachment_id=10 3. then pressing PREVIEW button in post editor - next tab in browser reloaded and replaced to preview page. IN wp2.6.* creates new tab in browser 4. in dialog adding new uploaded picture - words Large and Full size not gettexted (in beta3 all works fine ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Hosts that require setting FS_CHMOD_FILE andFS_CHMOD_DIR
From: Peter Westwood [EMAIL PROTECTED] Subject: [wp-testers] Hosts that require setting FS_CHMOD_FILE andFS_CHMOD_DIR Now that we have a fix for this - http://trac.wordpress.org/ticket/8478 I want to get some good documentation on the codex about this and also would like to build a list of hosts that we know require this to be setup. Could people feed back to me off-list a list of hosts they know need these setup and what they need setting to and then I will build up some documentation and publicity for this. Not sure where you will place the info but updated Editing wp-config.php earlier today. http://codex.wordpress.org/Editing_wp-config.php#Override_of_default_file_permissions MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Version Bump
Probably means there hasn't been a nightly build burned from the latest trunk yet. On 12/7/2008 8:19 AM, Jim Lynch wrote: I'm seeing the version bump in 10096 in trac, but after upgrading I am still seeing 10073. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Does auto update deactivate plugins?
Then for most if not all .# updates, deactivating plugins should not be neccessary at all. However, for major milestones it's probably a very good idea to deactivate all active plugins beforehand. Then again, it's probably a very good idea not to use the core auto-upgrade feature at all when upgrading to the next major milestone anyway. On 12/7/2008 12:37 AM, Ryan Boren wrote: On Sat, Dec 6, 2008 at 6:41 AM, Kirk M[EMAIL PROTECTED] wrote: I know this was asked before but I've forgotten. In the past I've always deactivated all my plugins manually before updating the core. Now I find myself using 2.7's auto-update feature the same way--the second thing I do before updating is to bulk deactivate all my plugins (first is to backup DB). So... Does running 2.7's new core auto update automatically deactivate plugins before updating and reactivate them after it's finished or does that still have to be done manually? During the upgrade, your blog is put in maintenance mode and loading is halted at the beginning of wp-settings.php. Nothing really runs, including plugins. The only thing allowed to run is the DB upgrade, which takes care of making sure plugins are not loaded. You don't need to deactivate plugins unless you like turning them back on one-by-one after upgrading to isolate any breakage they might cause. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Does auto update deactivate plugins?
From: Kirk M [EMAIL PROTECTED] snip Then again, it's probably a very good idea not to use the core auto-upgrade feature at all when upgrading to the next major milestone anyway. /snip I can't imagine why the core upgrade wouldn't be used for ALL updates. Isn't that the point of the whole thing to make it easier to upgrade, to encourage upgrades, to leaving users with more secure blogs? MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
[wp-testers] Verifying core update works for the real 2.7 to 2.7.1
I'm guessing that developers have this covered, but, are we sure that the core update works with the state of things set as if 2.7 is already released and installed? Meaning, the core update really won't do anything until a 2.7.1 is released, right? After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Right now the upgrade 'does an upgrade' even if the installation is already at the latest version... Just anticipating a Forum deluge. Thanks, MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Does auto update deactivate plugins?
Ideally, that would be true but with all the various combination of server set ups/WordPress configurations this is not often the case. In my experience in helping out other WP bloggers when their upgrades go bad, I'd have to say that close to 90% of the problems in upgrading (milestone releases) were caused by attempting to overwrite the wp-admin and wp-includes directories (with all their respective sub-directories) rather than deleting these directories first and then uploading the new ones from the next version. And nearly 100% of those problems were fixed by going back in and deleting the wp-admin and wp-includes directories and re-uploading them. Ideally overwriting these directories should work with no problem but in practice, it seldom does (even the instructions for upgrading at Wordpress.org says to delete those two directories first). I could be wrong but if I remember correctly, the auto-update feature overwrites any files/directories that need updating. For the minor in between security/bug fix releases, this is fine. But with major milestones, whole directories/sub-directories are replaced and if overwriting during the core auto-update is the current way of doing things then I would definitely do this type of upgrade manually. But to answer your question directly, since the larger portion of WP upgrades are those minor .# security/bug fix updates that come out between milestones, encouraging upgrading and promoting a more secure blog is exactly what the new auto-upgrade feature accomplishes. But I think it's important for all WP bloggers to realize that it's still very necessary to know how to work/manually upgrade their install via FTP because there are many times when that's all they'll have to rely on. The new core auto-updater is not a replacement for FTP, it's a supplement. Dissenting views welcome. (and sorry for the long reply...I'm a wordy bast***) On 12/7/2008 12:04 PM, Michael E. Hancock wrote: From: Kirk M [EMAIL PROTECTED] snip Then again, it's probably a very good idea not to use the core auto-upgrade feature at all when upgrading to the next major milestone anyway. /snip I can't imagine why the core upgrade wouldn't be used for ALL updates. Isn't that the point of the whole thing to make it easier to upgrade, to encourage upgrades, to leaving users with more secure blogs? MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? -- Xavier Borderie ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Ah, something I want to know as well. Since a few of my clients had requested to be updated to 2.7 RC1+ it would be nice to know if I'll be doing the update to 2.7-final automatically or manually (auto-updating to the final should be fine as I can't imagine there's any major changes from the current trunk to the final version). On 12/7/2008 1:40 PM, Xavier Borderie wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Does auto update deactivate plugins?
From: Kirk M [EMAIL PROTECTED] snip I could be wrong but if I remember correctly, the auto-update feature overwrites any files/directories that need updating. For the minor in between security/bug fix releases, this is fine. But with major milestones, whole directories/sub-directories are replaced and if overwriting during the core auto-update is the current way of doing things then I would definitely do this type of upgrade manually. /snip I've asked this is a different thread, but it seems that any upgrade, minor or major, will do the same thing--they'll replace all core files. The old argument of deleting before uploading vs. overwriting files with FTP becomes obsolete, thank goodness! MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
On Sun, 7 Dec 2008 19:40:47 +0100, Xavier Borderie [EMAIL PROTECTED] wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? I suppose it works like warning about new version works now, if you use a nightly build on the admin footer it show a message inviting you to kepp updated, if you use a release version it show a message on the top of the admin screens when and only when a new version is available. As actual version know if there is an update or not i suppose the automatic update use same method (plus the selection of the correct locale if available) for allow update or not. -- Stefano Aglietti - StallonIt on IRCnet - ICQ#: 2078431 Email: [EMAIL PROTECTED] [EMAIL PROTECTED] Sites: http://www.40annibuttati.it (personal blog) http://www.wordpress-it.it (WordPress Italia) ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Interesting question and I too would like to know the answer. I don't think it would be very practical if normal end users had the ability to upgrade WordPress continuously even if their wasn't an official update available. Michael E. Hancock wrote: I'm guessing that developers have this covered, but, are we sure that the core update works with the state of things set as if 2.7 is already released and installed? Meaning, the core update really won't do anything until a 2.7.1 is released, right? After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Right now the upgrade 'does an upgrade' even if the installation is already at the latest version... Just anticipating a Forum deluge. Thanks, MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
I was more worried that Matt and the guys would implement a Authorized Beta only system, where if you didn't have some sort of a code you wouldn't be able to Beta test Wordpress... Thereby getting rid of ppl like me. :( -Paleo Pat http://www.politicalbyline.com On Sun, Dec 7, 2008 at 2:34 PM, Jeff Chandler [EMAIL PROTECTED] wrote: Interesting question and I too would like to know the answer. I don't think it would be very practical if normal end users had the ability to upgrade WordPress continuously even if their wasn't an official update available. Michael E. Hancock wrote: I'm guessing that developers have this covered, but, are we sure that the core update works with the state of things set as if 2.7 is already released and installed? Meaning, the core update really won't do anything until a 2.7.1 is released, right? After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Right now the upgrade 'does an upgrade' even if the installation is already at the latest version... Just anticipating a Forum deluge. Thanks, MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
In message [EMAIL PROTECTED], Jeff Chandler [EMAIL PROTECTED] writes Interesting question and I too would like to know the answer. I don't think it would be very practical if normal end users had the ability to upgrade WordPress continuously even if their wasn't an official update available. Only admins have the ability to launch the update. -- mrmist ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
To be honest, I was thinking of getting rid of you. Kidding aside, I don't believe there are any wrong inquiries when it comes to testing. It is better to have someone stand up and be heard about a problem than have that problem go unnoticed and be broken for multiple versions. That is in my humble opinion. The more testers the better. That answer is a tricky one. If you update right when 2.7 comes out, if you are using RC1, then you should be fine. When WordPress goes back to being bleeding-edge then you will back on the nightlies. So I mean, the only ones affected will be the ones that update too late and update to bleeding-edge. However, you won't receive a notice to upgrade until 2.8 comes out. It will just be up to you on whether you want to or not. You know that is interesting. In the past, if you have one version say 2.5.1, it will tell you that 2.6.0 came out. Then if you want to upgrade to 2.5.2, it would still say 2.6. I wonder if they are going to fix that on the server side. Jacob Santos Paleo Pat wrote: I was more worried that Matt and the guys would implement a Authorized Beta only system, where if you didn't have some sort of a code you wouldn't be able to Beta test Wordpress... Thereby getting rid of ppl like me. :( -Paleo Pat http://www.politicalbyline.com On Sun, Dec 7, 2008 at 2:34 PM, Jeff Chandler [EMAIL PROTECTED] wrote: Interesting question and I too would like to know the answer. I don't think it would be very practical if normal end users had the ability to upgrade WordPress continuously even if their wasn't an official update available. Michael E. Hancock wrote: I'm guessing that developers have this covered, but, are we sure that the core update works with the state of things set as if 2.7 is already released and installed? Meaning, the core update really won't do anything until a 2.7.1 is released, right? After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Right now the upgrade 'does an upgrade' even if the installation is already at the latest version... Just anticipating a Forum deluge. Thanks, MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
On Sun, Dec 7, 2008 at 10:40 AM, Xavier Borderie [EMAIL PROTECTED] wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Version Bump
I just did an auto-upgrade myself about 15 minutes ago (4:15 pm EST) and the Admin footer now shows (2.7-RC1-10119) On 12/7/2008 3:43 PM, Kim Parsell wrote: Ryan just bumped the version again up to 10119. Auto upgrade was successful and dashboard still showing rev10073. I've upgraded right after a version bump and was shown the latest revision number right away. Any ideas on what's up today? Kim - Kirk M wrote: Probably means there hasn't been a nightly build burned from the latest trunk yet. On 12/7/2008 8:19 AM, Jim Lynch wrote: I'm seeing the version bump in 10096 in trac, but after upgrading I am still seeing 10073. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
[wp-testers] About NONCE_KEY
Last-minute addendum from Ryan:
define('NONCE_KEY', 'put your unique phrase here');
http://trac.wordpress.org/changeset/10120
I suppose we'll see http://api.wordpress.org/secret-key/1.2/ very soon?
Or will it still be http://api.wordpress.org/secret-key/1.1/ (I
seriously doubt it, but that's the URL I give in my soon-to-be-printed
book, so, one might dream...)
--
Xavier Borderie
___
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Thanks Ryan. Just the information that was needed. On 12/7/2008 3:27 PM, Ryan Boren wrote: On Sun, Dec 7, 2008 at 10:40 AM, Xavier Borderie[EMAIL PROTECTED] wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. Excellent thing, thanks for your answer Ryan. -- Xavier Borderie ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
Ryan Boren wrote: On Sun, Dec 7, 2008 at 10:40 AM, Xavier Borderie [EMAIL PROTECTED] wrote: After 2.7 is installed, and before 2.7.1 (yes 2.7.1) is released, what will happen if a user clicks the Upgrade Automatically button? Or will that button be visible? Like wise, an interrogation of mine : if we upgrade blogs to 2.7-rc1 now, they will update to the latest trunk, which is normal and expected. But what will happen once 2.7 is released? Will these users' installs of 2.7 still be fetching files from trunk, or does it stop there and only uses /tags from there on? If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. For the more adventurous of you that want to stay always on the nightly builds I intend on sorting out a plugin based solution although this may not be available before 2.7 goes gold. westi -- Peter Westwood http://blog.ftwr.co.uk | http://westi.wordpress.com C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5 ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Version Bump
Thanks Kirk, I just tried again and it finally updated to rev10119. Kim Kirk M wrote: I just did an auto-upgrade myself about 15 minutes ago (4:15 pm EST) and the Admin footer now shows (2.7-RC1-10119) On 12/7/2008 3:43 PM, Kim Parsell wrote: Ryan just bumped the version again up to 10119. Auto upgrade was successful and dashboard still showing rev10073. I've upgraded right after a version bump and was shown the latest revision number right away. Any ideas on what's up today? Kim - Kirk M wrote: Probably means there hasn't been a nightly build burned from the latest trunk yet. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Verifying core update works for the real 2.7 to 2.7.1
From: Ryan Boren [EMAIL PROTECTED] snip If you are running 2.7-xxx, you will get a notice to upgrade to 2.7 once it is available. From there you will be out of the development release track and onto the regular release track. To get back on the development release track you can change the version in wp-includes/version.php to '2.8-alpha'. /snip Okay, but what about when 2.7 is installed and before 2.7.1 becomes available, what will normal (not testers) users see? Right now it always says There is a new version of WordPress available for upgrade so will normal admin users see that message even though they have 2.7 installed? MichaelH ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] Customize placement of Reply link
that's what CSS is for? On Sun, Dec 7, 2008 at 6:44 PM, Bryan Harley [EMAIL PROTECTED] wrote: When using wp_list_comments, it automatically places the reply link at the end of the comment. Is there anyway to customize the placement of the reply link? ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
