Is there any difference between creation new theme package in magento community and enterprise version? I see in /design/frontend new folder "enterprise" available now. I wonder where I have to create my own theme - in or out this folder?
Enterprise Edition comes with additional functionality not found in community. Because of this instead of creating a new blank package you must duplicate the enterprise package. Rename it to whatever you want and keep the default theme and files inside that package. This will overwrite the standard Magento files with the Enterprise version. You then create a theme variant in this folder so that the default folder copied from Enterprise can be used as a fallback.
It's a bit messy and apparently will be fixed in a future release but as of EEv1.8 this is the recommended method.
You can read more about it on the Magento Site under the FAQ 'What About default/default?', and then '2nd Exception to Rule 6' and also read more in the Magento Design Guide PDF at the very end of Chapter 3.
Actually No, Enterprise edition have one extra package called enterprise and have default and iphone theme.
I you check System->Configuration->GENERAL->Design you will found that package name is set to enterprise.
So you can create your own Package and Theme in the same way as in Magento Community. for reference you can use this link.
Related
I want to create Prestashop theme quickstart package, But I did not found any way.
For more details..
I want to deliver to my client the template, that I have designed on my localhost.
And client can install theme's quickstart package same as prestashop 1.7 installation with theme's sample data like products, categories, banner, images all.
Small help will be highly appricaited.
Thank you.
You can create your own custom Prestashop distribution by following those guidelines.
This would allow to include custom modules and automatically enable them during install steps.
However I am not sure if there is a way to force also custom theme installation without tweaking the installer, so why not just packing the theme the standard way and include your theme modules as dependencies (with also a "import demo data tool" if needed ?). This is how almost all Prestashop third party themes are distributed.
Another option, if you'd like to provide your customers a ready to use environment with custom themes / already hooked modules, is providing him a ready-to-use ZIP package with already installed environment + SQL database dump.
I´m having problems understanding how to install a new theme in my magento 2.2 and i was hopping someone could help me understand what it is, what i did was:
I installed magento 2.2 from here. and then choose "Full release with sample data" community edition 2.2.0. The installation went well and i can access to my admin panel adn everything else.
Next i found this template and downloaded the package Bizkick v1.0.3, unzipped it and then i have two directories, which are "app" and "pub". After this i dragged these to my magento root, overwrite the ones that were there and now, i CANNOT access anything, not my initial page nor my admin, i have tried with other themes and the same thing keeps happening. I also have disabled my cache in the admin like the instructions said and them perform the above but with no luck.
Can anyone enligh me?
Regards.
I've spent a week trying to understand how Hybris installer works and I thought I could create any type of application with recipes. However my teammate said that those recipes are useless for dev or production setup. But why installer folder is a top folder in Hybris installation? Only for demo?
Your teammate correct, installer used for creating demo system.
In the Hybris WIKI are two sites that explain this one:
Installing Hybris Using Installer Recipes
Installing SAP Hybris Commerce
But you can also just have a look into the install recipes. There is no big magic behind it. Just browse to:
hybris\installer\recipes\b2c_acc\build.gradle
(for example) and have a look into it. First it sets some properties, than it defines which extensions should be used and at last it install addons on other extensions (normally on the storefront).
I'm trying to test my liferay-theme with liferay EE 6.1.20. This theme worked on my current liferay instalation. I can deploy my Theme without any errors on liferay EE 1.2.0 server. Than if go to control panel and try to switch the current theme to my theme - nothing happens and I see only liferay default theme on my page. I don't found any errors in the server log - I can't post any logs or errors hier, because I have no output with errors...
Can anybody help ?
I wouldn't expect too many differences between the two. However, the easiest way to make sure a theme can be deployed correctly is to use the matching SDK (e.g. 6.1.20), copy your _diffs folder to that one and compile the theme.
Make sure that Liferay's deployment descriptor /WEB-INF/liferay-plugin-package.properties specifically states that the theme is compatible with your version, otherwise Liferay might assume that it's not - this wouldn't be a technical but a configurational problem.
Also check liferay-look-and-feel.xml - there might be a compatibility field in there as well, I don't know which one takes precedence.
This setting is there because themes are built as a difference to a default theme that is built in to Liferay - and you basically state here which versions you have checked this theme to actually work with. You can specify any number of versions, as well as some wildcards (e.g. 6.1.20+)
I created a theme on my own magento website, and uploaded it to another magento website, but when i go to the frontend of that website i get this
Fatal error: Class \\’Mage_Core_Helper_Cookie\\’ not found in /home/winterwa/public_html/app/Mage.php on line 516
I searched for a solution and tried this one described in this topic:
http://www.magentocommerce.com/boards/viewthread/280318/#t401019
(cookie.php in app/code/core/mage/core/helper) but it didn\\’t help a thing.
Any suggestions/solutions for this??
It sounds like the two different Magento installs are running different versions of Magento. The file in question is only added to Magento in version 1.7. I can only assume that you have taken a fresh install of 1.7 and based your theme off of the default / base theme for this. Therefore when the theme gets added to an older version of Magento it is trying to load Blocks / Templates that you haven't overloaded and that just don't exist in the base template.
Unfortunately this won't be the easiest thing to fix. You will need to go through the layout/template files, removing references that add blocks or use helpers that don't exist for the current version of magento. For the issue you mention, you should be able to find by searching for helper('cookie') in your template files.