Since I have been approached but more often on this point, I write a very short “How-To” for the subject “Eigenes Template / Own design”.
All files, the shop or. Magento site can look like, as it looks, can be found in two main folders:
/app / design / frontend /
and
/skin/frontend/
From there it goes into the differences.
Each custom template will be distributed to these two folders. General superficial and can tell you, that stuck in the APP folder, the recipes and the ingredients in the SKIN folder. The ingredients are in this case e.g.. Pictures and the recipes, the files, the report, where the images and structures are shown.
As an example,: We have a template “Nature” bought this and upload to our Shop. By default, it would look in the folders you as:
/app/design/frontend/default/Natur/
and
/skin/frontend/default/Natur
Now it is important to know, that there is a separate standard Magento template or rather a number of standard templates, which build on each other. The first standard template can be found in
/app/design/frontend/base/default/
and
/skin/frontend/base/default/
The second default template in the folders
/app/design/frontend/default/default/
and
/skin/frontend/default/default/
So, and now comes the important point:
If a file in your own template “Nature” not addressed, but which is needed, Magento looks, whether this file 1. in the default / default / directory is. Where they do not there, it looks at default / default /. Are these not there, There is an error.
Thus, as long as the base / default / or. default / default / files used, as long as there are NO other information from the custom template “Nature” are.
Is there e.g.. page.xml a file in the folder base / default layout / but not in the other two templates (default / default / default and / nature /) This is used. But if you want to be now “Nature” Template a change to this file will, COULD you push them in the folder base / default / layout make. This would mean, however, that ALL other templates, the access to the page.xml noticed this change. Thus, it is always ADVISABLE, To copy the file to be changed (DO NOT move) and to pack in your own template folder. There will be changes only for your own template and not performed for all other. In our case, this would be Sun:
The file from the folder page.xml
/app/design/frontend/base/default/layout
Copy the folder
/app/design/frontend/default/Natur/layout
change and there.
It is important to always keep the folder structure. In our case, the base replaced by default and the default by natural. The subfolders will always correspond.
Should be run once in the worst case, something completely wrong, can you delete the wrong file in your own template and then quickly picks up the default Magento template by.
1.7.0.2
Unfortunately, the theme is not in the back not at Package / Theme Options with display :0
I think what was an extra in the Package.php verwurstelt!
Magus::getModel(‘core/design_source_design’)->getAllOptions() does not eat all themes 🙁
Hello F.U.T.Z.,
what exactly does "not see"? If you enter the appropriate template folder in the design area (also Design > Paket und Design > Themes)? Then (nach Cache Reload) the template is not displayed in the frontend?
Was in the package.php "messing around" or is the original still?
So there are the backend for example on Catalog / Categories under huh uh DESIGN abeichungen I think the possibility to specify (selection list using select option and it was only my package underneath the default theme). Now I have seen the admin section also only in the admin html fallback themes of attacks . Therefore I also have a Facebook theme / skin etc and it now works for CMS / widget !!
That is probably a thinking error in magento development or stop only be resolved in.
Then I came in because of design.php – Mage_Adminhtml_Block_Cms_Page_Edit_Tab_Design –
Magus::getModel(‘core/design_source_design’)->getAllOptions()
Loading and getAllOptions() in ähh /htdocs/app/code/core/Mage/Core/Model/Design/Package.php liegt, aid has since abated and can be seen in a getSkinBaseDir() I durch var_dump($baseDir), Insert before the return, it's always the URL admin html / default / own theme is tried. Goes well with me now. And Package.php has really built a mistake.
Tja, because you also have to come once on it. Thanks for the solution!
Vielen Dank für diesen Artikel. Ich hatte heute das Problem das mein eigenes Template nach dem Magento update nicht mehr angezeigt wird. Stattdessen kommt das Standard Layout. Werde heute mal deine Tipps ausprobieren. Habe noch ein Backup vor dem update. Einige Bereiche hatte ich ersetzt aber es hat nichts gebracht.