I have installed a magento website and configured one store.In configuration design i added the package and theme i have created for it in website level, store level as well as default store level
folder structure is like
packagename/default
packagename/mytheme
I have added catalog.xml to packagename/mytheme/layout folder to remove some of my right side elements like compare products.since it was not working i tried it with local.xml also
but it falls back to packagename/default/layout/catalog.xml
Can anybody give some idea what am i doing wrong
Thanks
I remain
Check System > Configuration > GENERAL > Design > Themes > Layout, it should be "default"
and check System > Configuration > GENERAL > Design > Package > Current Package Name it should be "packagename".
If these settings are correct, delete the cache as .suggested by Cags and everything should work fine
I find that normally, if you changed something in xml and it's not working, it's because of cache. My preferred option for purging the cache is with rm -rf var/cache/mage--*.
Related
I've read through some guides and watched a YouTube video on how to create a custom theme for OpenCart. After trying various things it still doesn't seem to be working right.
If I go to 'Extensions > Themes > Edit Store' I can switch the theme directory but this doesn't seem right. The question bubble there says changing the theme directory here is only for legacy support of older themes. Current themes should be available through 'System > Settings > Edit Store > General Tab (Select Theme Dropdown).
Why doesn't this seem to work? The new version is supposed to fall back on the default theme if something isn't available but it can't if I change the theme directory. I've even tried simply copying the whole default folder and renaming it.
Opencart 2.3.0 :
Go to Extestions >> Extestions >> Choose the extension type >> Select Themes >> Edit Your themes >> change default theme. See screenshots:
1 : https://postimg.cc/image/ds02xcmbp/
2 : https://postimg.cc/image/bre4q9fk5/
In file <Your project name>/catalog/controller/event/theme.php
replace row 16 from:
$theme = $this->config->get('config_theme');
to:
$theme = $this->config->get($this->config->get('config_theme') . '_directory');
I know it's bit late to answer but it can be helpful to others.
In OpenCart 2.3.0.2 creating a custom theme is little complex , finally i found this doc here which helped me a lot http://undefined.gr/site/2016/10/09/custom-opencart-2-3-0-2-theme/
To start with copy the default folder found in
upload/catalog/view/theme/default
to a new folder in the same directory. Name it “mytheme“.
Then copy the theme_default.php file in
upload/admin/controller/extension/theme
and place it in same directory. Name it “mytheme.php“.
Rename the class to (line 2):
ControllerExtensionThemeMyTheme
+ Replace all “theme_default” text to “mytheme“. Yes there are a lot (197).
Copy the theme_default.tpl in
upload/admin/view/template/extension/theme
and place it in the same directory. Name it “mytheme.tpl“.
Replace all “theme_default” text to “mytheme“. (48)
Copy theme_default.php in
upload/admin/language/en-gb/extension/theme
and place it in the same directory. Name it “mytheme.php“.
Set the new theme’s title in heading_title (line 3) to “My Theme”.
Finally for the thumnail image to show correctly in store settings rename default.png to mytheme.png in
upload/catalog/view/theme/mytheme/image
Now go into your Administration > Extensions > Extensions and select Themes in “Choose the extension type”. You should be seeing your new theme. Install it with the green (+) button and edit it to enable it. Also ensure you set the correct theme directory whilst editing the theme!
Then in System > Settings edit your store to use your new theme.
That should do it. You can now go ahead and start chopping and changing the default theme
I have installed a cookie bar extension via Magento Connect and it works just fine. I want now to change the text inside the that says "Close".
I have written it in the translation files, cleaned my cache and nothing happened.
I have also read this and tried to find the button on the extension's files, but I can't find it.
Anyone has more ideas of how to solve this issue or point me to a solution? Thanks in advance!
UPDATE
I am using this extension
Image of the issue:
To create translate you need to follow below steps :
Place your language package in /app/locale directory.
Now got to Admin c-panel > System > Configuration > General > Locale Options > Locale select you language pack from the Dropdown list.
you can also translate the words through Inline. Go to System > configuration > Developers > Translate Inline. After enabling this you can translate directly through UI
I am trying to use the Guest checkout on Magento 1.7, for some reason when I attempt to use guest checkout option I get the following error (the page doesn't change)
// on line 114
TypeError: sectionElement is null
sectionElement.addClassName('allow');
that actual block in that js files looks like as follows:
gotoSection: function(section)
{
var sectionElement = $('opc-'+section);
sectionElement.addClassName('allow');
this.accordion.openSection('opc-'+section);
this.reloadProgressBlock(section);
}
Can anyone suggest any reason for the error - our theme has been modified recently obviously however I am sure where is best to check to debug this problem.
UPDATE:
Having used the debugger tools in Firefox I can see within this function the section variable is set to 'org' - this page has since been removed and will no longer be required within the checkout process. Can anyone suggest where this 'org' value is being set in the code?
I believe that 'opcheckout.js' is looking for the element 'opc' and it cannot be found for the guest checkout steps. I would first check the file:
app/design/frontend/default/YOURTHEME/template/checkout/onepage.phtml
as a starting point to troubleshoot the problem.
Double check you do not have any extensions, modules, etc. conflicting with your checkout process.
You can enable System > Configuration > Advanced > Developer > Debug > Template Path Hints, set to Yes and Add Block Names to Hints, set to Yes. This will help you identify which module/block is outputting the code block which is incorrect on the checkout page. If you can identify the main content area template path, you can then inspect the template file using FTP.
Try disabling modules in the System > Configuration > Advanced > Advanced > Disable Modules Output > Disable any Modules which may be in conflict, flush magento caches and retest guest checkout.
Fixed - for anyone else that may find this useful I had references as follows within the opcheckout.js
this.gotoSection('org');
As this section had been removed it needed to be removed from the same js file.. magento never simple :)
Hi my theme just updated to a new file organization that uses sub custom themes so that I can update the theme without overwriting the files I changed myself.
I downloaded the new theme and set up the new file path, but the site still reads from
skin/frontend/default/shopper/css/styles.css
when it should read from
skin/frontend/shopper/default/css/styles.css
I set the current package name to “shopper” and set default (under Design/Themes) to custom. I know I want my custom files of the theme to go under shopper/custom, and then magento should check for files at shopper/default and finally check for files at base. For some reason its ignoring the shopper directory and still referencing from the old default directory.
And saved everything. I also disabled and flushed all the caches.
The two images attached show how I have it set up in magento via the admin and the ftp. I haven't been able to solve this for months.
FIXED IT!
The issue was not in System > Configuration > Design but in fact System > Design I discovered that System > Design had it set up for Default/Shopper and there wasn't a time frame for it. The following link helped me reach my conclusion.
http://www.magentocommerce.com/boards/viewthread/197908/
You are supposed to System > Design for temporary theme changes, but my site had it set with no time frame thus always overwriting my settings in System > Configuration > Design
This is my first time working with Magento and here is what happend: I spent two days reading the documentation and tweaking the settings to fit my needs. I then installed this theme:
http://themeforest.net/item/decostore-magento-theme/1876494?WT.ac=category_thumb&WT.seg_1=category_thumb&WT.z_author=8theme
The problem is that the theme didn't work the way I was expecting and now I'd like to rollback to the default theme and completely remove everything added by this theme to my installation.
Unfortunately, I didn't backup the installation and database before I installed the new theme and I have no idea where to start.
Thanks in advance.
1. Switching back to default theme
Go to the admin area and then system > configuration > design
Change "Current Package Name" to 'default' and make sure all inputs under the "Themes" section are empty. This will return you to the default theme.
2. Completely remove everything added by this theme
I take it from your question that you are not using any form of source control. Might be an idea to look into this for the future :)
Magento 1.7 has introduced backup and rollback features so you may also want to check that out.
If this is the case, backup everything before you start removing files and directories as described below
Anyway, to completely remove all files and directories added when you installed the module, unfortunately it will simply be a case of manually finding the files and directories deleting.
The easiest way to do this will be to find the original source code you received when you purchased the theme and removing the corresponding files from your site. When removing directories be careful to only remove those specific to the theme - It will have been sent to you structured so that you can easily drag straight in to your web root - so will contain some other directories required by Magento, simply to give it the correct hierarchy.
At the very least there will be files and folders specific to the theme located in the following directories:
app/design/frontend
skin/frontend
js
and also most likely some more in the following:
app/etc/modules
app/design/adminhtml
app/locale
I know the result for this can be different for everyone, but in case someone else comes across my specific case, it was the N98 folder under app/code/community/N98 that caused the problem. Particularly their CustomerGroupCheckout plugin as shown here: https://github.com/amenk/N98_CustomerGroupCheckout
Removing the N98 folder brought back the configuration page.