i didnt say anything about you being new, did I?
Whats not to understand, the single file I am referring to is called xmlrpc.php and its linked to right inside the post that announces the upgrade:
http://wordpress.org/development/2008/02/wordpress-233/
In other words, your complaining needlessly — they
provided what was essential, and it would not have affected your theme.
You, whether you have been here 2 days, or 2 years, didnt read that post apparently.
Patches should be on this page.
http://wordpress.org/download/
well, you can use words like “should be” all day long — the fact is that matt, et al, can do whatever they like, whenever they like, however they like.
Your opinion is just that.
fireundubh wrote : “I think downloading a single upgrade file that contains unchanged files, including the Kubrick theme, makes upgrading unnecessarily difficult”.
1- Backup your database
2- Backup your wp-content
3- Upload the new release or only the changed files (this is what whooami explain, by the way )
4- Go to example.com/wordpress/wp-admin/upgrade.php
What is so “unnecessarily difficult” in these instructions?
Anyway… I give up. But I srongly encourage the wordpress team to keep the upgrade like this. This is the easyest open source blog/cms to install or upgrade.(did you ever tried to upgrade zencart for instance ?)
I really fear all these so called “automatic upgrade” gizmos.
Make a backup, replace files, put back your backup… It’s almost too so simple to be true…
S.
P.S. The is a BIG NOTE on the upgrade page : NOTE The wp-content folder requires special handling, as do the plugins and themes folders. You must copy over the contents of these folders, not the entire folder. Copying the entire folder overwrites all your customizations and added content.
P.P.S. Default means default…
I agree w/ the original poster. The changed files list and changed files download link must be made available at http://wordpress.org/download/.
Of course, as I am a mere user of WordPress, I don’t have the influence to control anyone into doing this, so treat this as my wish.
I just lost an entirely unique theme updating WordPress. Please either stop packaging the default theme with new versions OR provide just the updated WordPress files in separate archives. The update process is extremely counterintuitive and has pissed me off for a long time.
Why is it counterintuitive? Each new release of WP must be treated as a complete package for the person who may be new to WP and wants to install the software, maybe for the very first time. The download page clearly states what’s included in the distribution.
It seems awful silly to blame WP because you didn’t make a backup of your wp-content folder, or even worse, that you don’t have a backup of your work someplace offline!
Maybe you were too busy thinking about all those themes you’ve designed and all those corporate and non-profit sites you say you’re involved with to remember to make backups?
Why do you have to wag your digital Johnson around and pound your chest and call everyone else stupid everytime someone disagrees with you or points out your obvious mistake?
It really doesn’t help anyone solve anything now does it…
Note from on high: The original poster put forward his/her opinion on the issue at hand. If you feel a need to respond to that and provide your own, you’re free to do so. But let’s tone things down and avoid personal attacks (direct or otherwise), or I’ll feel compelled to tie this thread up.
ok, I’ll keep it calm.
many things could be different but they aren’t so I deal with those.
One, I personally wouldn’t put a custom theme in the same place that anything else could potentially overwrite it.
And I’d have another copy of those files *somewhere* just in case I goofed up.
While it’s definitely important to backup and be careful when upgrading, I can’t help but sympathize with the idea that the (frequent!) upgrade process is made even more tedious by having to download a whole installation file.
Definitely would be nicer if there was a specific “upgrade” package with the new files only, and perhaps some indication of which files are essential.
That said, I would be very wary about automating the process, given how often plugins and mods are broken by even minor upgrades.
Definitely would be nicer if there was a specific “upgrade” package with the new files only, and perhaps some indication of which files are essential.
yes but we’re getting off track. Even with an upgrade package you would have the same problem in this case if for example the changed files included the default theme. Easy fix there would be to name your hard work theme something other than default.
With a decent ftp,scp,etc client you can upload only files that are new. Push button easy.
Standard IT helpdesk scenario:
user: I have spent several hours working on (blah, blah), and it’s corrupted/disappeared. Help me.
operator: revert to your backup copy..
user: Err..
operator: NEXT!
Even with an upgrade package you would have the same problem in this case if for example the changed files included the default theme.
Yes, and this would be where reading is important. There is always a changelog that is linked in every update announcement that lists exactly what is changed in what files. If one is concerned with overwriting old files – that should be what s/he should reference.
Before WP had themes and all that, we were restricted to hacks and I used to keep a txt file on my site that listed every single file I’d altered because I’d so often been lazy and didn’t read what files had been changed and done exactly what the original poster did. It happens, but there are precautions one can take.
Going back to the original post, I find it rather juvenile to come to a public forum and yell at everyone for something that, as I noted above, could have been prevented if some care with reading the announcement had been taken. The /download page always lists the latest stable, it has never been a record of what updates, etc. – that’s why there’s the dev blog. Which, as has been stated by other replies, did link to the single file that needed to be changed, as well as a changelog of all the other minor changes.
If you’re going to have a theme in a folder “default” – it should be you, I think, that should take care to keep a backup. It’s sloppy to store a theme in such a folder anyway, knowing how WP is packaged. And I’ve made several themes from scratch and never had a problem having them recognized – perhaps this is an issue you should research into to help avoid possible theme loss again.
The support forum isn’t really the best way to get you point across to the devs especially when done in a demanding way. Anyway the proper channel to contact the devs would either be the kvetch or use the ideas forum. The support forums are for just that support.
I’m sorry but who on earth besides a MORON modifies a theme that he knows has shipped with WP since the fish walked… then cries foul when his own theme .. which he has SUBSTITUTED in place of the theme that everyone knows ships with WP … gets overridden during an upgrade?
This is just stunning in its audacity.
Put “your theme” in a different theme folder like god intended for you to do and keep on trucking. What is so hard about that?
