Version: EE 2.0.0b02 20091016 Reporter: angstmann —
This is an archived bug report. If you are experiencing a similar issue, upgrade to the latest release and if that does not solve the problem, submit a new bug report
After following the instructions to upgrade my old 1.6.8 site to 2.0beta, I moved my old template files on my server to their new location system/expressionengine/templates/ before running the update.
After what was reported as a successful update, I found that my templates (stored as files) were being ignored, and the templates in the database were being used instead. I was expecting EE to to find my old template groups and files on my server and to use those. I used the Synchronise feature and no errors were reported, yet my old templates were still not being picked up.
All paths were checked and double-checked and found to be correct. All permissions were correct also.
A final related point was that brand new templates that I created in the CP and chose to save as a file on the server were NOT being created, despite all paths and permissions being correct.
Further details can be viewed in this forum thread:
ExpressionEngine implements Markdown Extra and BBCode. Please see the Markdown Extra docs and the BBCode Wikipedia article for a full reference.
**bold**, __bold__, *italics*, _italics_, ~strike/del~, `code()`
bold, italics, strike/del, code()
Link: [link title](https://example.com)
Image: 
[blockquote]...[/blockquote], [quote]...[/quote], and Markdown style:
> Some quoted text. > > This is all one quote.
[code]...[/code], and you can also specify the language for syntax highlighting, [code=php]...[/code]
GitHub flavored Markdown code fences are also supported:
```
public function decoderRing($str)
{
return str_rot13($str);
}
```