Define Pages using classic template and overide system

[FishySteve]

Hi Guys,
I've been beating my head against the wall for days searching for a simple answer but the search results in some way or another aren't that simple or isn't quite what I want to do. I don't want to use the ezpages because the pages don't show up in the site map and don't contain the keywords in the URL.
That said, what I'm trying to figure out is to add some additional pages with links that will appear in the information side box that will also be safe during an upgrade.
I'd like to use the classic template because it seems the most likely template to be maintained being part of the zen download.
I've seen the threads that say it's safe to add a custom folder (custom being the name if the template) in all the directories that contain the "classic" folder to store the overide files, at this stage I only want to add new defined pages such as "Our Mission Statement" for example.
The problem I'm having trouble understanding is the threads talk about other templates when I'm I like the classic template.
If someone has a spare moment I'd really appreciate a step by step on creating additional pages using the define pages editor that will not be overridden in future upgrades.
I may not be the brightest candle on the cake but from the amount of threads I've read through it's obvious many others are having issues here also.

With all my confusion I do hope this is a clear question and Haven't left anything out.

Kindest Regards
Steve

I'm going to put some ice on my head now.......

The version I have is 1.3.7

[FishySteve]

Oh 1 more thing,
I may later decide to change the template for whatever reason so it would be nice to know if this would cause a problem down the track.
Thanks again
Steve

[gjh42]

If you use the /classic/ template files/folders to customize, they WILL be erased during an upgrade. (Ok, many of them will be safe because classic now has only a stylesheet to achieve its look... it's still not a good idea because you will lose your stylesheet.)

If you like the Classic look and want to base your design on that, copy all the /classic/ files/folders to /[your_template]/, change the info in template_info.php, select your new template in admin > Tools > Template Selector, reset in the layout boxes controller and you're good to go.

[FishySteve]

Hi Glenn thanks for your reply mate,
It seems Like a catch 22 situation..
Keep the zen template and risk new pages being erased in a zen upgrade
or
Use a custom template and risk new pages being erased in a template upgrade

I honestly thought the overide system was there to protect changes?

Now the brick wall is hitting my head.
Cheers

[gjh42]

The override system protects changes to files that are not in the stock distribution fileset. The /classic/ files are part of that. THey are intended only as a base to modify from. Also, it is always good to have an untouched classic template you can switch to for troubleshooting. If a problem goes away, you know it is in the custom template; if not, the problem is elsewhere.

[FishySteve]

Hi Glenn,

The override system protects changes to files that are not in the stock distribution fileset. The /classic/ files are part of that.

Do you mean
"The override system protects changes to files that ARE in the stock distribution fileset."
If so buy making a new page name shouldn't it be safe?
I understand uploading a new version over an existing installation would replace files that are named the same. What I was thinking was to;
Keep all the stock files
* checkout_success
* conditions
* contact_us
* discount_coupon
* main_page
* page_2
* page_3
* page_4
* page_not_found
* privacy
* shippinginfo
* site_map
Turn them OFF in the define pages status and add files that have slightly different names so they wouldn't be over written such as
* checkout_successful
* conditions_of Use
* Please_contact_us
* discount_coupons
* Our_main_page
* Our_Mission_Statement
* etc_another new_page
* etc
* This_page_not_found
* privacy_Statment
* shippinginformation
* website_map

I don't understand how these "new" files could be over written but would like to use the overide system to be safe seen there is so many issues about this in the forums. And by keeping all the stock files there but turned off, should it all be ok?

THey are intended only as a base to modify from.

I was just going to make another copy these file and rename them.

Also, it is always good to have an untouched classic template you can switch to for troubleshooting. If a problem goes away, you know it is in the custom template; if not, the problem is elsewhere.

I agree 100%.


Sorry to sound like a pain but this just gets more confusing and I honestly don't understand why it has to be so complicated just to add a few extra pages without the worry of being over written in any upgrades.

Thanks again
Steve

[gjh42]

It doesn't have to be complicated. Just make your copy from /classic/ into /your_template/, and keep all the define pages with their original names in the /your_template/ override folders. Anything you store in the /classic/ folders becomes part of the classic template, which makes troubleshooting that much more involved.

Making new page names is actually far more involved than that. Definitions and references have to be created, and a module file and a template file in many cases...


Restatement for clarity:
The override system protects files that are not in the stock distribution fileset locations. Changed stock files in their original locations will be overwritten.

[FishySteve]

Thanks again Glenn,
I might take another look at EZ-Pages even though it isn't going to rank as well in the search engines, it might save a lot of headaches later during upgrades.

Making new page names is actually far more involved than that. Definitions and references have to be created, and a module file and a template file in many cases...

I do hope it is a more simple task to add content to the site safely without the risk of erasing pages during an upgrade with this method.
Cheers
Steve

[gjh42]

EZ-Pages reside in the database, so have no issues with file upgrades.