gmane.comp.web.wordpress.testers

Re: 2.7 bleeding auto update to 2.7 bleeding?

Frank Bueltge — 2008-10-07T06:50:45

yes, my install is in root - "/"

Re: 2.7 bleeding auto update to 2.7 bleeding?

DD32 — 2008-10-07T06:36:35

Ok, Those Defines shouldnt affect it at all. When you access your site VIA FTP, I assume the WordPress directory is found at / ? Ie. You can see /wp-config.php ? On Tue, 07 Oct 2008 17:31:13 +1100, Frank Bueltge public.gmane.org> wrote:

Re: 2.7 bleeding auto update to 2.7 bleeding?

Frank Bueltge — 2008-10-07T06:31:13

Thanks. I have define: define('WP_HOME', 'http://bueltge.de'); define('WP_SITEURL', 'http://bueltge.de'); only this two constants, not Abspath or WP_CONTENT_URL etc. My blog is install in the root of the webspace, not in a subdir.

Re: 2.7 bleeding auto update to 2.7 bleeding?

DD32 — 2008-10-07T06:22:15

Can you give an example of the paths? What is ABSPATH set to?, What paths have you defined in wp-config.php?, What folder do you have access to via the FTP account(I presume) that you're using?

Re: 2.7 bleeding auto update to 2.7 bleeding?

Frank Bueltge — 2008-10-07T06:06:05

Hello, in a other testblog i have this answer as error: Unable to locate WordPress directory. Install and wordpress-adress are define via constants in wp-config.php Anyone have a idea? Thanks and best wishes. Frank

AW: Preview not always working

Holly Doyne — 2008-10-07T05:03:51

thanks - I just missed it on the list. -Holly www.proseknitic.de ----- Ursprüngliche Mail ---- Von: Andrew Ozz laptoptips.ca> An: wp-testers-sGP8xfnoDwYkvSXg/V30/FaTQe2KTcn/< at >public.gmane.org Gesendet: Montag, den 6. Oktober 2008, 21:39:39 Uhr Betreff: Re: [wp-testers] Preview not always working Holly Doyne wrote: There's a ticket for that: http://trac.wordpress.org/ticket/7816 It's being fixed. _______________________________________________ wp-testers mailing list wp-testers-sGP8xfnoDwYkvSXg/V30/FaTQe2KTcn/< at >public.gmane.org http://lists.automattic.com/mailman/listinfo/wp-testers

Re: 2.7 bleeding auto update to 2.7 bleeding?

Ryan Boren — 2008-10-06T23:05:26

http://trac.wordpress.org/ticket/5560#comment:60

Re: Preview not always working

Andrew Ozz — 2008-10-06T20:39:39

There's a ticket for that: http://trac.wordpress.org/ticket/7816 It's being fixed.

Re: Preview not always working

Brent Logan — 2008-10-06T20:37:03

I've had this happen to me a few times. Every time, it's happened when I didn't save the draft first. On Mon, Oct 6, 2008 at 1:34 PM, Holly Doyne public.gmane.org> wrote:

Preview not always working

Holly Doyne — 2008-10-06T20:34:06

On 2.7 and have had few issues to this point. Today, I tried previewing an unnamed post. It had autosaved, but I had not directly saved it nor added categories. Instead of getting a preview, a new tab opened up with a blank post. Repeated this with a couple of other attempts. Adding categories didn't make a difference. Adding a name, then hitting preview worked after doing a manual save. No clue as to why this happened. Can anyone else reproduce this? Rates right up there with uploading media, it appearing in the post but the gallery window at the next upload saying Gallery (0) -Holly www.proseknitic.de

Automatic Core Update and rights?

Frank Bueltge — 2008-10-05T18:33:40

Hello. What for right are necessary for the files? The Update works great in my test-glog on local install under XAMPP; a dont work on a live blog on webspace. Liebe Grüsse Frank ______________________________ Mein Buch: WordPress - Weblogs einrichten und administrieren | ISBN 978-3-937514-33-8 bueltge.de kvfl.com _______________________________________________ wp-testers mailing list wp-testers-sGP8xfnoDwYkvSXg/V30/FaTQe2KTcn/< at >public.gmane.org http://lists.automattic.com/mailman/listinfo/wp-testers

Re: Re: Latest 2.7 trunk(9802?) widgetspagenon-functional

Kirk M — 2008-10-05T12:07:58

Should have mentioned that I did this also (sorry, it was late) along with disabling Gears in Chrome. Gears was enabled for the site when using IE 8.0 beta 2 by the way, with no problems. I also tested this in my local Sandbox (the latest XAMPP on Windows XP SP3) with no plugins installed at all with the exception of "WP Widget Cache" and of course, the Amazing Grace theme...same problem as described below. All browsers are running "Shockwave Flash 10.0 r12" and Java(TM) Platform SE 6 U10 (required for Chrome). I was thinking along the lines that both of these are pre-release and might be causing these anamolies (leaning more towards the Java version causing the widgets glitch) but I really can't quite fathom why it would manifest on Firefox and Chrome and not on the others and why only with this one plugin and theme? I did contact both authors last night to see if they could shed some light on this. Oh yeah...despite minor rendering glitches at 1024x768, I'm lovin' the new Admin UI. On 10/4/

Re: wp-testers Digest, Vol 44, Issue 5

2008-10-05T09:53:42

Hi, I still can´t upgrade WP automatically. Upgrading and even installing Plugins works fine. I even installed WP completely new, but still getting the same message: "Unable to locate WordPress directory.". I don´t know which information exactly is needed, but what I can tell is: WP is installed in root directory (no specialty here), I use a server on which PHP 5.6.2, Apache and MySQL 5 are running I tried both connection methods: FTP and FTPS, but have the same problem Thx. Message: 5

Re: Re: Latest 2.7 trunk(9802?) widgets pagenon-functional

Matt — 2008-10-05T02:02:27

Are you using Google Gears in Firefox? If you are, try disabling it. On Sat, Oct 4, 2008 at 6:55 PM, Kirk M public.gmane.org> wrote:

Re: Latest 2.7 trunk(9802?) widgets page non-functional

Kirk M — 2008-10-05T01:55:53

On using the core auto upgrade to the latest 2.7 revision (r9082?) I've noticed that the Widgets page is completely non-functional. The widgets page comes up but nothing can be clicked in either the "Available Widgets" column or "Current Widgets" column. Everything outside of these two columns still functions correctly. [removed last line] Anyone else seeing this? *Update*: On further testing (arrgghh!) I've found that the Widgets page functions correctly in IE 8.0 Beta 2 in both "Standards" and "Compatibility" (IE 7.0 emulation) modes and Opera 9.6 beta. The Widgets page does not function as stated originally in Firefox 3.0.3 (fresh profile) and Google Chrome version 0.3.154.0 (Official Build 2776--latest Dev build). The kicker to all this is that it's Vladimir Prelovac's "Amazing Grace" theme and/or Andrew Zhang's "WP Widget Cache" that's causing this to happen and of course I use both. It doesn't prevent either the theme or the plugin from functioning properly nor does it throw any errors

Latest 2.7 trunk(9802?) widgets page non-functional

Kirk M — 2008-10-04T23:53:42

Admin rendering problems at 1024x768

Kirk M — 2008-10-04T23:30:47

Hi folks, Just upgraded one of my sites to WP 2.7-hemorrhage (all went well by the way). One thing I've noticed right off the bat is that with my rather longish blog title; "Green Mountain Geek" the bread crumb style navigation rendering suffers badly at 1024x768 but more importantly, the "Page Options link that resides on many of the Admin pages is all but inaccessible (and completely inaccessible on a few pages) being severely overlapped by the "content" area of the page and the left hand menu sidebar. In the case of the Comments "Moderate" page, the "Page Options" link is overlapped by the "Show All Comments" link making the "Page Options" completely inaccessible. You can see this in the screenshot of the top of latest 2.7 trunk build" http://farm4.static.flickr.com/3284/2912689585_cf5fd93bde_o.jpg Other than that...great job so far!

Re: 2.7 bleeding auto update to 2.7 bleeding?

Kirk M — 2008-10-04T22:56:06

Alex, Is there a description anywhere of what happens during the upgrade process that you know of? I had bookmarked just such a page previously but unfortunately there was an argument between the my Firefox bookmarks and the Firefox profile manager and my recent bookmarks were a casualty of war. On 10/4/2008 6:15 PM, Alex Hempton-Smith wrote:

Re: 2.7 bleeding auto update to 2.7 bleeding?

Alex Hempton-Smith — 2008-10-04T22:15:58

plugin deactivation was included in the auto-upgrade process. I'm pretty sure plugins are deactivated prior to the auto-upgrade and then reactivated after, I've never had to manually deactivate them before.

Re: 2.7 bleeding auto update to 2.7 bleeding?

Kirk M — 2008-10-04T21:59:07

Thanks for the reply. Just updated one of my sites to an older revision of 2.7 and then auto-upgraded from there. Upgraded with no problems. I did deactivate all plugins beforehand though as I wasn't too sure if plugin deactivation was included in the auto-upgrade process. On 10/2/2008 7:02 PM, DD32 wrote:

Re: WP 2.7 suggestion

Paul Robinson — 2008-10-04T13:15:05

Hi, Thanks for the suggestion, but no it must be cropped I use both the small and medium thumbnails. The small ones already have the crop to square option available but it would be nice to have such an option for the medium thumbnails as well. That way I wouldn't have to hack Wordpress' media.php file to do it. Thanks again though. Paul. 2008/10/3 Musing Minds public.gmane.org>