little problem with extension setup

Monday 16 June 2008 5:44:39 am

Hi, I've installed many ezpublish 4.0 site, but i must have failed somewhere in one of this, because now as i try to make an override i automatically have an ezodf override.
Now I'll be more accurate on what's going on:
I've gone in setup/classes, created a copy of folder, named it folderplus, (had a little change on the title, the option i needed, trascurable detail done in other sites with success), saved.
Than I've go Design/templates selected /node/view/full.tpl, I clicked New Override, and now i usually select "no extension" on the option menu, I insert the template name, the override class and than save, but now i couldn't select "no extension" because there wasn't the option, even if i see it on other sites, sites that should be very similar, so the override was created automatically in ezodf.
Do you know what I've to do to have back the extension option? It's the first time i create an extension with this site.
Thanks

Wednesday 18 June 2008 3:22:01 am

I'd the same felling of you, but I don't know if I've to check some specific directory, but /extension, /design, and /settings seems configured like the others are, and all other ezpublish options, except this, seem working as intended.

Thursday 19 June 2008 2:02:09 am

I noticed that installing a vanilla ezpublish, without installing the ezwebin extension, I'm in the same situation.
There is not the option to select the extension for the override, so i think this is what i have to look for.
Does someone know what file "and how" I have to modify them to manually insert the ezwebin extension? (it's already installed anyway, but want to check files)
May also this be related to database?

Thursday 19 June 2008 3:29:35 am

I was right! And I solved this with the help of Salgua.
If you don't see the extensions option in the override page it may be due to the following reason, anyway i think a bug generated that, because I never handled those files, but it seems they was corrupted, this probably happened in the migration of the site 3.10-4.0.
Salgua executed a test on the system files, asking if they was modified, the system answered positively, and listed the following files (in my case):

settings/siteaccess/admin/site.ini.append.php
design/admin/override/templates/embed_image.tpl
design/admin/override/templates/tiny_image.tpl
design/admin/templates/content/edit_languages.tpl
design/admin/templates/content/edit_sections.tpl
design/admin/templates/content/urlalias.tpl
design/admin/templates/content/urlalias_wildcard.tpl
design/admin/templates/contentstructuremenu/content_structure_menu_dynamic.tpl
design/admin/templates/page_copyright.tpl
design/admin/templates/parts/setup/menu.tpl
design/admin/templates/rss/edit_export.tpl
design/admin/templates/section/list.tpl
design/admin/templates/setup/datatype_code.tpl
design/admin/templates/setup/extensions.tpl
design/admin/templates/shop/currencylist.tpl
design/admin/templates/shop/productsoverview.tpl
design/admin/templates/visual/templatecreate.tpl

What i did was downloading ez 4.0, and replacing manually one by one the files, a real cache cleaning (/var/cache and /var/ezwebin_site/cache tabula rasa) and than it worked again!
Actually salgua is having lunch, than I'll tell you how to have the system check, to check what file you may have corrupted luke.