| 2:38 pm on Dec 11, 2008 (gmt 0)|
From what I have heard, they'll be needing that auto upgrade feature! I understand that the changes in 2.7 are quite dramatic, which really could crash your plug-ins or have some unusual side effects. It would be REALLY sensible to back up this time round before you upgrade... and maybe wait a few weeks and check to see if anyone is having problems.
I'll just wait until my Fantastico gets it upgraded... I'll feel it's stable by then.
| 3:07 pm on Dec 11, 2008 (gmt 0)|
GREAT NEWS! Upgrading and keeping secure the 100+ WordPress sites we manage was our most-hated task.
| 3:23 pm on Dec 11, 2008 (gmt 0)|
>>Upgrading and keeping secure the 100+ WordPress sites we manage was our most-hated task.
And I pitied myself updating 5 blogs every month or so...
| 3:28 pm on Dec 11, 2008 (gmt 0)|
I'll never use the auto upgrade feature because I have to make some custom changes every upgrade but I'm sure it's going to be useful for many.
A change that isn't mentioned however is that the entire commenting system was moved and is now controlled by a single call instead of being a customizable snippet of code. We're going to see a lot of bland looking comment sections since they are no longer part of a downloadable theme.
Yes, you can pass some $args with the call but none that control appearance. I suppose this was needed to make comments threadable and pageable but in changing this for my own personal use I can say that not many people will be bothered, it's not a small thing to change anymore.
I rate 2.7 a solid B however, it's definitely an improved product, comments template not being easily accessible aside.
[edited by: JS_Harris at 3:29 pm (utc) on Dec. 11, 2008]
| 5:56 pm on Dec 11, 2008 (gmt 0)|
security is my number one concern, everything else can take a backseat
| 9:05 pm on Dec 11, 2008 (gmt 0)|
I getting ready to "re-launch" our WordPress site, so the timing is perfect on this. Great news. Thank you, engine.
| 9:35 am on Dec 12, 2008 (gmt 0)|
Wouldn't auto-upgrade require you to give Wordpress permission to modify its own source code? If you're on a suexec-style server, that might be worth doing (but I wouldn't). If you're on a shared hosting that requires you to chmod 777 things to let Wordpress write to them, then enabling this feature should display a banner "congratulations! Any user on the shared server can now deface your website!"
| 11:47 am on Dec 12, 2008 (gmt 0)|
Slef, the documentation says this about the upgrade process: "All file operations are performed as the user that owns the files, not as the web server's user. All files are set to 0644 and all directories are set to 0755, and writable by only the user and readable by everyone else, including the web server."
| 1:29 pm on Dec 12, 2008 (gmt 0)|
I've one standalone WP site to upgrade. I'll take a look at this "auto-upgrade" more closely when doing that.
| 3:24 pm on Dec 14, 2008 (gmt 0)|
I am really worried about this auto upgrade feature. There's no way that they can do file operations as the user that owns the files for 99% of servers unless they do it via FTP - and if they do it by FTP you are in the position of having your FTP details available to a script which has regularly reported security holes.
| 9:43 pm on Dec 14, 2008 (gmt 0)|
From what I read the auto upgrade feature relies on the server using something like suPHP or FastCGI, which makes PHP run as the owner of the scripts and not some general account like www. If none of those is present, the upgrader will fallback to FTP or SFTP, which requires the user to provide his FTP account details (true horror indeed).
| 11:41 am on Dec 15, 2008 (gmt 0)|
Auto update is fine for some, but I feel that the less there are that have auto access, in any form, to the box, the better.
No thankyou very much Wordpress. We'll just stay the current course and update the old fashioned way ... when loads are minimal and all is quiet on the server.
I hate auto updates. I mean C'mon then. How many of you out there in www land have been working on a major project of some sort only to have it tilt when Symantec decides to run 3 or 4 instances of the LuCom all at once and every 5 minutes, for an hour at a time?
Or those of you on the Windows? Having Microsoft nag you half to death about a reboot in the middle of a support session or something?
Nope. I've come away with a certain distaste over the years with regard to auto updating anything.
Though Wordpress be only a small thing, when compared to bloatware entities like Symantec and Microsoft, the thought of the auto update still raises the hackles around here.
| 2:20 am on Dec 16, 2008 (gmt 0)|
|Upgrading and keeping secure the 100+ WordPress sites we manage was our most-hated task. |
You should really look into running the sites off a single code base. You'll still need to visit all 100 sites and go through the download and upgrade process and then, when necessary run the DB update script. Can't avoid the latter, but you could still save a lot of time.
You might check out this thread as well
I haven't upgraded yet, but I think it works like the old auto-update plugin which means that it isn't "automatic" so much as "push-button".
| 11:03 am on Dec 16, 2008 (gmt 0)|
Has anyone tried to upgrade to 2.7 on their blogs? Any problems faced? I am planning to upgrade my blogs this weekend..
| 4:09 am on Dec 20, 2008 (gmt 0)|
Painstakingly slow in IEX.
The new layout is a bit on the busy/cluttered side, and like with anything new, you'll be lost for a bit trying to figure out where everything is because of the way the menu is set up. It still has the awfull previous version look about it and here's a shocker ... it refuses to display quite correctly in IEX ... Firefox and Opera do alright with it however.
My plugins all appear to be working, and if your IEX seems to just drag when you're tooling around in the admin, try Opera ... it blazes ... even faster than Firefox.
| 1:28 am on Dec 21, 2008 (gmt 0)|
I'm still waiting for 2.7.1 ... or .3
| 7:40 pm on Dec 21, 2008 (gmt 0)|
Not a big fan.
I tried it, and it moves along at about the same pace as Firefox does in my experience.
Don't get me wrong on this then, Google does a bang up job in many cases. It's just there isn't anything really too new or too exciting about rendering engines that have been around for a while.
Google's Chrome isn't exactly ... Cutting Edge.
| 8:13 pm on Dec 21, 2008 (gmt 0)|
Not a fan either (basically, at this point I'm so dependent on Roboform I won't use any browser that doesn't support it), but I was just thinking it might help isolate JS issues from others.