I want to add extension - All Category Product Carousel in my Magento Website and it has RWD theme.The components of the extension are by default installing in:
app/design/frontend/default/default/layout
app/design/frontend/default/default/template
skin/frontend/default/default
I have moved the components in my theme folder i.e. RWD, and components are now in the following folders:
app/design/frontend/rwd/default/layout
app/design/frontend/rwd/default/template
skin/frontend/rwd/default
But after this also the extension is not working. I am new to Magento so does not know much things about it. Does anything else be done?
The products are there but css and js is not getting applied on them. The data is showing like: Please View Here
You can paste your extension key here. Now you can check if you have copied all the files to RWD.
The extension tell to insert below block in cms page. Include it in your cms->home page.
{{block type="pcarousel/pcarousel" pcarousel_id="carousel id" template="pcarousel/pcarousel.phtml"}}
After that navigate to system->permission->blocks->Add new block and add the type pcarousel/pcarousel there and allow it.
The css and js files were not loading in the main page, have added them externally. Now working
Related
I am trying to update cart page in Magento, and more specifically files from web/template/cart. I copied all these files to my custom theme, but somehow all changes are ignored and Magento still using files from vendor. It only happens to html file - phtml are updating correctly.
Tried to clear cache etc. but without any success.
Any ideas?
What file are you editing? Put some example for the name and directory. If the changes not applied so don´t rewritting the files.
Hi I want to create custom theme using default-bootstrap so I copied whole folder, rename and then I made all changes in CSS.
I install my theme via backend, deleted all cache files and theme seems to working but there is issue with top navbar - it isn't look like as in default-bootstrap, check this:
Default's nav: http://i.imgur.com/MiRnM42.png
My nav: http://i.imgur.com/MrWZeFm.png
Any ideas why nav isn't lok like default?
did you check your css + code for typos? That might be the case :)
try this:
https://validator.w3.org/#validate_by_uri+with_options
I want to install new theme in magento and I have also followed step of this link (https://www.siteground.com/tutorials/magento/magento_themes.htm) but I am not abling to get theme in magento. Please suggest me how can I install theme in magento ?
Thanks
If you already have the pre-built theme, then in magento project folder navigate to
app/design/frontend/default
Place your theme folder here.
Now to activate your theme. Log in to your admin panel.
Navigate to
system->configuration
Click in the design tab in the left hand side
Under the "Pakage Name" put you package name i.e "default" in this case and under you theme In the "Template" put your theme name "Your_theme_name" i.e your theme folder name that you copied inside default directory.
If you are creating a new theme, just create a new folder inside default directory and follow the step as described above.
In this way you can install a new theme.
Hope this will help.
It depends how theme you want to use is distributed. If it is a package, just extract it to your root folder and you should get proper folders in skin and app/design dirs and what you need to do then is to set correct package and / or theme in backend (Configuration > Web > Design). For full package theme name would probably always be default. Although if you are only adding new theme, you should pick its name app/design/frontend/default/{theme_name} and same in skin folder (if it includes some additional css, images and / or javascript).
I have a problem with magento 1.7 (WYSIWYG).
My problem is that I can't have a proper description of the product when I use the WYSIWYG.
For example if I write in the WYSIWYG my product description, on site web site I will have a presentation which isn't the same.
The WYSIWYG puts html tags for each line return.
Thank you for your help
I've found in the past that with some themes the description is run through the nl2br function first. This will replace all new lines with <br> tags. Look in your view.phtml template file for this and remove the nl2br function.
It could be that you have custom css on the front causing it to appair different, view source both the admin (WYSIWYG) and on the website to see if the html are the same. If they are the same then check your custom css
In the file description.phtml in the template/easytabs folder, I removed the nl2br.
And then it works fine.
Can someone verify what I think is what's happening with Magento's fallback theme hierarchy.
The final fall-back point is the /base/default/ theme.
Within your interface/package (they are the same things right?), your default theme is selected at, from the Magento admin page, System->Configuration->General->Design->Themes->"B" ("B" is an example name of the theme).
On top of your default package theme, you can select an active theme from System->Design->"A".
So with this setup, Magento will look into "A" first, then in "B", then finally resort to base/default if neither A or B has files it needs.
Correct or no? TIA!
Sorta.
The fall-back hierarchy in Magento CE v1.4+ and EE v1.8+ is as follows.
Look for requested file in:
app/design/frontend/custom_package/custom_theme/
skin/frontend/custom_ package/custom_theme
If not found, look for requested file in:
app/design/frontend/custom_package/default
skin/frontend/custom_package/default
If not found, look for requested file in:
app/design/frontend/base/default
skin/frontend/base/default
If not found, a rendering error will occur.
Source: Magento's Theme Hierarchy - Changes in CEv1.4 and EEv1.8
I will do my best to clarify some points for you.
If you are not using a child theme, magneto will use /base/, however if you have a child theme active, magneto will use your custom theme files.
For example, If your new theme file has a header.phtml file but not footer.phtml, Magento will automatically fall back to the base. this is why its never smart to edit core files