WordPress.org

Support

Support » Requests and Feedback » STOP PACKAGING UPDATES WITH THE DEFAULT THEME

STOP PACKAGING UPDATES WITH THE DEFAULT THEME

  • fireundubh
    Member

    @fireundubh

    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.

Viewing 15 replies - 1 through 15 (of 30 total)
  • …!

    The first step when you upgrade : make a backup.

    http://codex.wordpress.org/Upgrading_WordPress

    The first step when you make a theme : make a backup.

    The first step on a forum : do not shout with CAPS…

    Nobody have to take the blame for the fact that you’re unable to read the instructions…

    S.

    fireundubh
    Member

    @fireundubh

    The first step when you upgrade : make a backup.

    The first step when making upgrades available: make individual upgrades available. The open-source community has been doing that for at least a decade. Proper versioning precludes requiring users to re-download untouched files, such as the default theme.

    The first step on a forum : do not shout with CAPS…

    No, CAPS is “shouting.” And that’s precisely what I was doing.

    Nobody have to take the blame for the fact that you’re unable to read the instructions…

    Whatever that means. I wasn’t blaming anyone else for destroying my theme. I was blaming the developers for poorly designing the upgrade process which led to my theme’s destruction. I normally remove the default theme from the archive prior to extraction. Your insult was completely unnecessary and unwarranted.

    That said, I managed to “recover” the theme that was overwritten by piecing together snippets of code from other unique themes I’ve created. But my criticism of the upgrade process still stands.

    Wow – if you mess with the default theme and don’t save it, you can’t blame the devs, it’s just like changing any other core WordPress file.

    I know – the next release of WordPress shouldn’t update any files, just in-case somebody has made changes to them, wouldn’t want them to lose any changes now would we?

    fireundubh
    Member

    @fireundubh

    Wow – if you mess with the default theme and don’t save it, you can’t blame the devs, it’s just like changing any other core WordPress file.

    I didn’t mess with the default theme. I deleted the default theme and place one of my own themes in a “/default” directory. I’ve ran into problems with past versions where WordPress resets the default theme and breaks the site. Placing your own theme in a “/default” directory ensures that WordPress always uses that theme.

    I know – the next release of WordPress shouldn’t update any files, just in-case somebody has made changes to them, wouldn’t want them to lose any changes now would we?

    Sarcasm is stupid. My criticism is valid. Your assertion is not.

    Sticky: WORDPRESS 2.3.3 IS AVAILABLE!!!!

    The #2 post has this…

    also, if you want just the changed files, in a zip ..Ive made a zip available on my site –whooami

    and

    I was blaming the developers for poorly designing the upgrade process which led to my theme’s destruction.

    I have not seen any upgrade process (eg: an upgreade only file version), just clear instructions on how to upgrade.

    But you can not argue with the upgrade instructions…

    fireundubh
    Member

    @fireundubh

    But you can not argue with the upgrade instructions…

    Instructions are indicative of poor design.

    The fact is that the Kubrick theme is included in every package by default. There should be an installation package and separate upgrade packages. The Kubrick theme should only be included in the installation package for first-time users and initial configuration. The Kubrick theme should not be included in upgrade packages in which only a few files of many have actually been updated.

    fireundubh wrote : I didn’t mess with the default theme. I deleted the default theme and place one of my own themes in a “/default” directory.

    LOL…

    S.

    fireundubh
    Member

    @fireundubh

    LOL…

    Laugh all you want. I’ve designed plenty of unique themes (i.e., themes not based on other themes) and manage at least six different corporate and nonprofit websites that use WordPress as a CMS, not just as a blogging platform. I do things the way I do them for good reasons.

    Clayton James
    Participant

    @claytonjames

    I’ve ran into problems with past versions where WordPress resets the default theme and breaks the site. Placing your own theme in a “/default” directory ensures that WordPress always uses that theme…
    …and manage at least six different corporate and nonprofit websites that use WordPress

    Even so, what sounds counterintuitive to me is spending a lot of time creating a customized theme and then placing it back in the default path without keeping a current backup of all your hard work. I’m not arguing your point, I just think it’s pretty hard to justify “shouting” at anyone other than yourself. Especially if you knew from past experience that this would happen on the next upgrade as well.

    “I” think that maybe if you suggest to the “devs” to make an upgrade package available, you may find that more beneficial for you and us all. This forum is not the most friendly place IMO (esp: for new users (no implication to anyone) with old/dumb/used to death/well documented Q’s (I don’t blame all who help either)), and shouting posts like this just get us all going (warranted/needed), right?

    Maybe there is a reason that there is no upgrade package? I don’t know but maybe it would help the process.

    fireundubh
    Member

    @fireundubh

    I’m not arguing your point, I just think it’s pretty hard to justify “shouting” at anyone other than yourself. Especially if you knew from past experience that this would happen on the next upgrade as well.

    Right. I’m pissed at myself for not remembering to remove the default theme from the upgrade package, and I’m pissed at the lack of better upgrade packages, especially at the frequency WordPress releases upgrades.

    fireundubh
    Member

    @fireundubh

    and shouting posts like this just get us all going (warranted/needed), right?

    Yes, well, I was angry and needed to shout. You’ve all had kneejerk responses in your life, right? Sorry for shouting, but like I said, I stand by my criticism.

    …especially at the frequency WordPress releases upgrades.

    Better to be hacked?

    I was going to stay out of this one, but I cant help but ask why you find downloading the ONE file that was actually the whole reason for the release THAT hard?

    Use wget? Coulda grabbed it.

    Use Fetch? Coulda grabbed it.

    In other words, they did sort of provide what you asked for. Its there, downlodable, one little file. IF you read the post that announced it.

    Trouble is that too many people come here and dont read — the dev blog, the codex, or the forums.

    /me runs back to playing with her treo.

    fireundubh
    Member

    @fireundubh

    I’m not understanding your question, whooami. Do you understand this thread? I don’t think downloading a single upgrade file is difficult. I think downloading a single upgrade file that contains unchanged files, including the Kubrick theme, makes upgrading unnecessarily difficult.

    By the way, I’m not a new forum user.
    http://wordpress.org/support/profile/106036

    Clayton James
    Participant

    @claytonjames

    @whooami

    I got just the updated files from your site, by the way. Thanks for taking the time to Zip ’em up and make them available. Worked out just fine.

Viewing 15 replies - 1 through 15 (of 30 total)
  • The topic ‘STOP PACKAGING UPDATES WITH THE DEFAULT THEME’ is closed to new replies.