customizing theme in 2.7 - what happens when upgrading to 2.8? (4 posts)

  1. nikky_hack
    Posted 6 years ago #

    I really want to use WP 2.7 as the base for a brick/mortar store's website. I will need to customize the CSS and all the files (obviously). The index.php will be the main page of the site - (eg. http://www.some-stores-site.com/index.php) showing the WP blog. But I will be adding other pages with links from the index page's sidebar. (eg. http://www.some-stores-site.com/about.php or /products.php or /workshops.php ...) thus creating a site with lots of pages outside of a basic WP install.

    Question: having never customized WP, or in this case upgraded before... what happens when WP 2.8 comes out? Can I just auto upgrade one click, or will all my custom code be wiped out? Am I essentially playing around styling a theme that won't be affected by an upgrade, or by changing the code in index.php, sidebar.php, header.php... and so on - asking for a nightmare in the future? Any ideas/suggestions?

    Thanks in advance,

  2. evilbeet
    Posted 6 years ago #

    You should generally be okay with the one-click upgrade, with some caveats.

    You need to make sure that you save your modified theme as something other than the Classic and Default themes that come with WordPress. If you are basing it on one of those themes, you need to change its name and put it in a folder with a unique name. Otherwise it WILL get overwritten in the one-click upgrade. But as long as you do that, your changes should not be affected by a one-click upgrade.

  3. nikky_hack
    Posted 6 years ago #

    great news,

  4. yorokobi
    Posted 6 years ago #

    Also, don't modify the core code of WordPress. Or if you do, take notes so you can do it again (much better to leave it be).

    For instance, there was a point where Post IDs stopped being displayed in the admin section. I could have added that back in by editing the right php file in the wordpress code, but I knew that would be wiped out later. Fortunately there was already a plug-in to put it back, otherwise I'd have to have written one myself.

Topic Closed

This topic has been closed to new replies.

About this Topic