i updated a magento store from 1.6 to 1.9. I got some problems with the one page checkout. At first i cant order anything. I resolved this with adding the formkey. The 2nd problem is that this:
<?php echo $this->getChildHtml('checkout_progress_wrapper');?>
does not show anything. I am using my own theme and checkt out the old xml with the new one but there seem to be no changes. The div isn't even parsed empty it's juzst not shown. Hope someone can help me.
Here are some step for upgrading magento
Take a backup of current database and current 1.6 code. place maintenance.flag file inside 1.6 code folder to put website offline.
Download latest magento from the http://www.magentocommerce.com/download
Remove all folders and files from your 1.6 code except maintenance.flag (but you should have backup somewhere) and place all folders and files from the 1.9.x
Now from your 1.6 merge your following custom folders into the 1.9.x
Community app/code/community
Local app/code/local
Media
your theme or package (app/design/frontend/default/<your theme> or app/design/frontend/<your package>)
custom folders from Skin (both for adminhtml and frontend).
copy your custom xml files from app/etc/modules/ to current app/etc/modules/
any custom admin theme folder from adminhtml/default/yourtheme.
copy your custom folders from adminhtml/default/default/ (1.6) to adminhtml/default/default/ (1.9.x).
custom js files if any from app/js/.
Now go to app/etc/local.xml.Edit database details their.put your database username and password and database name.
Remove maintenance.flag file and check the site in the browser. it is done.
Related
I recently updated my dev magento site with a new theme, configured it and selected it as the theme in the admin panel. However when i go to the front end it is still using all of the old pages for the main content but the header and footer are the new theme.
Image of theme selection
please have a look at your theme folder path. If it is app/design/frontend/intenso/default/
Then you have to use Current Package Name Under Package as intensio(your-theme-name) & Under Themes use Default as default
For more detail, check screenshot:
Screenshot explainig solution for showing old theme
Hope it helps
Steps to reproduce
Installed Magento 2.0.4 on WAMP server 3.0 , Windows 10 Pro - 32bit, PHP 5.6.15, MySQL 5.7.9
Created a child theme themeparent of Magento_blank in app\design\frontend\Vendor1\themeparent with several layout xml files for extending, along with template .phtml files. Activated from admin. Working Fine.
theme.xml => <parent>Magento/blank</parent>
Created another child theme themechild of above theme themeparent (which is itself the child of magento blank). This childtheme is created in different vendor folder, i.e. Vendor2
This theme path is app\design\frontend\Vendor2\themechild . Created layout .xml file inside to extend its parent theme layout. Activated this second level child theme from admin. The .xml files not even processed. Not working.
theme.xml => <parent>Vendor1/themeparent</parent>
3b. Although template .phtml files or .css files existing in childtheme are working fine if corresponding layout containers/blocks called in from the Vendor1\themeparent layout files.
If for a test, the same child theme childtheme put inside same vendor of its parent i.e. Vendor1 , the theme path becomes app\design\frontend\Vendor1\themechild and then the same layout .xml files works fine.
Already tried with clearing public/static and var folders of magento. Also, tried after running with cli commands
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex
php bin/magento setup:upgrade
But nothing solved it.
Expected result
The required theme inheritance is in this way:
Magento_blank => Vendor1_themeparent => Vendor2_childtheme . (note vendor differ)
Result: Layout .xml fail to load in childtheme.
But if for a test, inheritance made this way:
Magento_blank => Vendor1_themeparent => Vendor1_childtheme . (note vendor same)
Result: Layout .xml load properly and work fine in childtheme.
As per Magento 2 guidelines on http://devdocs.magento.com/guides/v2.0/frontend-dev-guide/themes/theme-inherit.html#set-a-parent-theme it is clearly mentioned that "A parent and a child theme can belong to different vendors. For example, your custom theme can inherit from the Magento Blank theme." . So, if I am creating a second level child theme (in vendor 2) from a parent theme (in vendor 1) which is a child of Magento_blank (vendor: Magento), this should ideally work fine. But its not happening. None of the layout .xml files processed to output if they are under different vendors. If I put both themes in same vendor, they are working fine.
Actual result
Extending layout .xml files in the 2nd level child theme in different vendor folder is not working.
Why Magento 2.0.4 not working properly for 2 level theme inheritance with different vendor names?
This is a serious issue, as if you suppose purchased a paid theme from somewhere (which they have created by inheriting Magento_blank), and now you want to create your child theme of that paid theme but in different vendorname folder (obviously under your companyname), you will not able to do so!
You have only two choices left, either make your child theme inside their vendor name; or edit their theme .xml files to call your child theme template files or .css/.js (if in ur vendorname); the second case will obviously loose updates, weird way and not recommended.
Then what is the solution??
Giving it more time to find the reason, I created different set of parent and child theme with different vendornames, and checked it on same installation and it worked!
I was amazed, matched the way to what I have done earlier in my themes; old and new both exactly same. Again activated my childtheme, and surprisingly it not worked. More surprised and fedup. :(
Then I digged into the magento database, and I found out one amazing thing. In the 'theme' mysql table of magento database, somehow the 'type' column corresponding to my childtheme had value set as '1' and all others were set '0'. Under suspicion, I tried to find what it means by comment in table column name which shows..
0 => Physical
1 => Virtual
2 => Staging
I guessed it may be a reason, and manually set the 'type' column value to 0 corresponding to my childtheme. Cleared var and public/static folders. Re-tested, and voila! it worked!!
This small issue has wasted my 4-5 days, with no solution. Even deactivation-activation or switching themes from admin was not resetting its value to 0 (it always remained 1) and so it never worked.
For a cross check to confirm, I deleted that row from database theme table, and reinstalled the theme, ran php bin/magento setup:upgrade, and now its setting the value to 0, which is perfect and working automatically.
Don't know how it was set to 1 and when. It should be 0.
Anyways, the issue is solved now, and
I found a very tiny thing but a VERY BIG thing
, which can waste every developers time if not known.
But, surprisingly this silly point is no where mentioned on the internet and not even on the magento documentation, which must be there.
Hope this explanation and solution will help more people later who are getting frustrated with the same issue. :)
This issue is also raised and explained on https://github.com/magento/magento2/issues/4330
Thanks.
I can't for the life of me manage to override the main shop page.
My understanding is that it's archive-product.php
I've attempted to copy it into the Woocommerce directory I created in my theme's root directory and modify it. No dice.
I've also attempted to modify it directly in the Woocommerce plugin directory. No dice there either.
I've even gone as far as adding an underscore before the archive-product.php file name in both locations (woocommerce directory and my theme template directory) in an attempt to hopefully BREAK it - just to see if I could impact SOME change - and that doesn't seem to have any effect either.
I'm not running any cache plugins and every other Woocommerce template file I've attempted to modify up until this point has worked fine.
Any ideas?
You are doing this correctly. You'll have to double check the locations as per:
Shop template is in
plugins/woocommerce/templates/archive-product.php
You can copy to my-themes/woocommerce/archive-product.php to
override the core woocommerce file.
I just had the same issue,
What worked for me, is removing the woocommerce.php file, because before, it applied the template woocommerce.php to the shop, and not the archive-product.
The answer is that when you updated to the newest version of WooCommerce, you have to "reinstall" the WooCommerce pages because the old system did not use the wc_get_page_id() function, which looks for the shop page.
Luckily this is super easy! Go to your admin, then to WooCommerce, then to System Status, then click on the Tools tab. Then click the button to the right of Install WooCommerce Pages. This will only install the missing WooCommerce pages and, get this, will reinstall the shop page with the proper wc_get_page_id.
NOTE: if you have content in the original WordPress shop page, although it didn't erase it for me, you might just want to copy the content first just in case.
I was able to fix this by using the suggestion here - Changes on archive-product.php doesn't work
but, it seems like a bug to me. WooCommerce claims that you need that root woocommerce.php page in order to incorporate the plugin into your custom theme - http://docs.woothemes.com/document/third-party-custom-theme-compatibility/ - but, this does work.
I'd love to know the reasoning behind this.
Switching to the twentyeleve/twentytwelve theme's and trying to override the archive-product.php file in the same fashion worked great, but they don't include a native woocommerce.php file in their root directory either. What gives?
i've created a new website under a working Magento install. The old website works fine, but the new one doesn't load the theme css. I can see it loads the .phtml files when enabling Template Path Hints.
I've already checked basic things 100 of times, so...
set theme to desired one
refresh Magento cache
check source code to see whats the css path
use i.e. firebug to see what css is being loaded
can you show your file structure?
whats the theme name?
In Interspire I copy a template & paste it then rename it & I customize it according to my theme but when i go into admin & in admin when i click on design mode then there should be site open for making changes but in my new template it is not open in proper way & I am not be able make changes in this mode please tell me why it is happening in my new template only. in standard template it is working properly. Please tell me the region why this is happening when i select my own template in design mode then there is an error in error-console error is :--- undefined xt/javascript">
After you paste the template, make sure the file is readable by the web server. Insufficient right is the main reason you are not able to modify it.
I'm not 100% sure what you mean about the copy and paste. But the best way to create an Interspire theme is to use the default folder or one of the other ready made templates and do the following:.
Let's say you decide to use the "default" theme. Copy the entire folder somewhere on your computer and rename the folder to the name you'd like your theme to have.
If you are changing specific files, copy those files from _master to the correct directories in your new theme folder.
Upload to your server and activate.
Your theme file names have to remain the same. i.e. you can't rename the files themselves, only the top level theme folder they are in.
Then you can open up the files and make your changes inside of them.
Even though it's possible. I stopped using the built in theme editor once we took the step to create our own theme. For one, doing so kept removing our custom panels when we hit the "save" button.