Thread

I have all my new sites on EE2.1.3, but my old dog was never updated due to the sheer size and my fear of stewing things up—but I’m ready to move it over to EEv2 as well.

I understand the conversion process will convert my EE1.x templates to EE2.x templates, but I’m not sure how to go about making them “flat files.” I enabled the export to file option as direct din the User Guide, and all the various templates were saved as PHP files. ??? I ran the update wizard, and I got an error stating the templates weren’t readable text files.

So…

1. I went back to my templates and used the Export Templates option, and all the templates were saved as TXT files, so I assume that’s what I need. Is this correct?

2. The directions say to save the templates to “system/expressionengine/templates/<site_short_name>,” but it seems that you specify a short name when you’re using the Multiple Site Manager? What’s my site_short_name supposed to be?

2a. Another part in the directions says to move them into “system/expressionengine/templates/”—no “short name.” Which is correct?

3. The exported templates from item 1 are organized like so: “search_tmpl,” “site_tmpl,” and so forth. Do you put those directories into the directory from item 2? Do I keep the folder names as exported?

Thanks!

I went through this recently as well - basically it looks easiest to me if you bring the external templates back into the database and don’t have the upgrade process worry about the flat file templates.

In other words, if you don’t have your templates saved as flat files don’t do that for the upgrade, it’ll be more straightforward if you just leave them in the database.

I went through this recently as well - basically it looks easiest to me if you bring the external templates back into the database and don’t have the upgrade process worry about the flat file templates.

In other words, if you don’t have your templates saved as flat files don’t do that for the upgrade, it’ll be more straightforward if you just leave them in the database.

This will show my ignorance—but I haven’t a clue what you’re talking about when you say to “bring the external templates back into the database” or “leave them in the database.”

???

Did you develop the site?

How do you edit templates now?

Did you develop the site?

How do you edit templates now?

Yes, it’s my site. I edit templates in the CP and template manager. When I read database, I think of the SQL database, etc.

If you edit & save templates via the CP, then they are saved in the ExpressionEngine database along with your content.

Some developers prefer to edit templates in a text editor, so they save the files outside the EE database to the file system as “flat files”.

If your templates are all in the database you can ignore the part of the upgrade docs that talks about what to do with them if they are flat files.

If you edit & save templates via the CP, then they are saved in the ExpressionEngine database along with your content.

Some developers prefer to edit templates in a text editor, so they save the files outside the EE database to the file system as “flat files”.

If your templates are all in the database you can ignore the part of the upgrade docs that talks about what to do with them if they are flat files.

Gotcha. So I need to go back into the EE1.x CP and remove the entry that points to the directory of the exported files then, first, right?

I’d do that, turn off “allow templates to be saved as files”, and go into each template to ensure that it’s showing as being saved to the database.

Upgrading flawlessly!

After remove the template reference, it still threw an error about the files—so what I had to do was go to each and resubmit it, then everything upgraded like a charm.

Thanks!

maury.mccown,

Brilliant! Thanks Mike. Closing this one out. Feel free to start a new thread if you have any more questions