I copied attributes.phtml file from base into my custom theme to change the way the attributes table is displayed.
When I make changes to it keeping it in the base, it works fine.
Copying it into custom theme removes the entire tab entirely beside description tab.
Since it is working fine in the base version but not in my custom theme folders, is there something particular about attributes.phtml that I need to keep in mind before copying into my custom theme folder?
This is probably a case of permissions. Just check and ensure you have the correct permissions as the rest of the files.
Related
I'm using Magento Ver. 1.8.1.0 and I'm trying to make a child theme of a free theme I've downloaded. I already try to create the following folders copying all files I need from the original theme
public_html/atacadomiranda.com/app/design/frontend/my-pack/my-theme
public_html/atacadomiranda.com/skin/frontend/my-pack/my-theme
Also tried to make a folder called 'custom' inside of the main theme folder where is 'default' folder. Make all changes in DESIGN section of CONFIG ADMIN SESSION. I tried to do some changes to footer.phtml (just for be sure it's working), and no changes are made at all.
What I'm doing wrong?
It worked by changing the System->Config to 'custom' folder inside of parent theme folder.
I'm new to Prestashop development. The first thing I've tried is to create a new theme copying the default theme directory in Prestashop 1.6. The problem I have is that, once created, the theme is not detected by Prestashop: is like the directory wasn't there.
If I create a new theme from the admin panel and replace the directory content with the same files, it works ok.
What should I do to make Prestashop detect my theme? I haven't found any information about it.
Thanks a lot.
I already answered on similar question here, there are two ways to solve your issue through backoffice
Copy default theme in Preferences -> Theme press Add new theme
button and then at the bottom Create new theme + choosing Copy missing files from existing theme.
OR if you already copied theme dir/files by FTP
Same steps, but without copy missed files (of course if you have no
missed files) and just put correct new dir name in Name of the theme's directory
This is actually the way it is done - Copying the default theme.
There could be several reasons for that:
Have you changed the name of the copied folder?
Did you use only a single lowercase word as a name?
Did you copy it to the /themes folder?
Here is additonaly info after the copying to do some cleanup: http://doc.prestashop.com/display/PS15/Creating+your+own+theme
Also it is perfectly fine to create a copy of the default theme from the backend. You can find instructions here: http://doc.prestashop.com/display/PS16/Laying+the+Theme's+Foundations#LayingtheTheme'sFoundations-Standingontheshouldersofgiants:copyingthedefaulttheme
For people who are using Prestashop 1.7 or higher and is facing the same problem when copying the Starter Theme, I recommend you to check if you actually have a themes/your_theme/config/theme.yml configuration file because the one that is loaded by default is a theme.dist.yml so Prestashop won't recognize it.
just a quick developer question in regards to Magento Extension/Theme Packaging, more specifically, when packaging, would I place the template files, layout files, skin folders etc in the base folder (see path below)(and not overriding any core files either)
app/design/frontend/base/default/template
app/design/frontend/base/default/layout
skin/frontend/base/default/css
and so on? I see this would be most suitable as alot of platform users would have custom themes with maybe custom namespaces for the theme folders. As users would have to stuff around to rename/move files/folders to work with their platform if packaged the default way I have seen in the past (ie in the default/default folder paths).
cheers for any feedback
This is the only way to package extension to use base/default or default/default location for template, layout and skin folders. Because if custom theme is used, then also this will work due to Magento's fallback mechanism. And if user want to add those files in custom theme location, then he/she should manually copy or move files in theme's respective location as you have said. And it is obvious that we can not predict custom theme path while packaging extension.
I'm fairly new to Magento and am having trouble uploading the Aheadworks blog extension to the correct directories. I am using a custom theme for my site, let's call it "themex". The directions state "Navigate inside step_1 directory. If you use a different from default theme - be sure to rename step_1/app/design/frontend/default/default and step_1/skin/frontend/default/default folders to your store's values."
I've located the 'step_1' directory but I'm not quite understanding the latter part of the directions. Am I renaming the 'step_1' directory to "themex" and uploading it to the root directory? Please be as descriptive as possible in your response.
Their instructions are badly phrased, but I'm pretty sure it means that you need to upload the files to app/design/frontend/default/themex
Magento theme files appear in the app/design/frontend/ folder.
The "base" folder here contains the core layout files, and the "default" folder contains the file overrides for other themes. As such, your theme's layout files will appear under app/design/frontend/default/themex (possibly app/design/frontend/themex/default depending on how the theme works)
Magento will first look for design files here first, and then look under app/design/frontend/base if the override does not exist.
Make sure you back-up any files, and if their files over-write any of your theme files then run a comparison on them to make sure they are not over-writing any of your theme's functionality.
I am making some changes to a purchased magento theme. Is there any simpler way to backup my work other than by copying the relevant folders inside app skin and media and their directory structures.
What I recommend that you do is to have your purchased theme as your default theme, i.e. in the "default" folder under your package. You can then declare another theme, e.g. "custom", and copy the path/files to there that you wish to override. You just need to set the "Default" value to "custom" in Admin > System > Configuration > Design > Theme.
Just thought I'd answer this for anyone coming along - as far as i can make out the answer to the question is no, not really - unless I'm doing it the wrong way - ( and I think not ) then the best method of backing up a custom theme is to first compress the entire app, skin and media ( if relevant) directories into one archive file, move this and expand it in an empty directory, then carefully delete all the other theme folders, leaving just the files which you are using and the directory trees which you have created - this preserves any files you have in your custom theme and also the necessary directory structure. If anyone has a better method maybe they'd share it.