There's two directories in the Github respositories:
magmi
magmi-0.8
Which one should I use?
I had this question as well. After sniffing around, it looks like the magmi-0.8 folder may be reserved for the future releases of Magmi 0.8. The current stable is 0.7.19
I tried to run the magmi-0.8 version but got a bunch of errors, so I am now running the app from the base magmi folder. Fingers crossed this version plays nicely with Magento CE 1.8
This post provides more info:
https://github.com/dweeves/magmi-git/issues/12
This is not something standard for GitHub.
You're rather referring to Magento Mass Importer project hosted on GitHub.
As you're starting now, you should use the magmi directory, as it has the most updated code.
Related
It's really weird what i am really dealing with here, in all the books that i read about learning and developing themes for Magento it points out to the directroy app/design/frontend/base/default/ and that it should contain three folders (etc. layout, template)**but when i go and search for it i only come up with **app/design/frontend/Magento and the Magento folder is empty,reinstalled Magento many times so i am sure it's a clearn installation, what is going on here, why i can't see those directories?
app/design/frontend/base/default , this path restricted to before and till magento version 1.9.x. You shall be downloading and using magento 2.0. For this you have to download magento version 1.9.x
I am trying to move some code into a bower package, and my code depends on prototypejs. Prototypejs is not in the bower registry (or it wasn't-- actually I just added it incorrectly, so this question is a bit like asking how to avoid spilling milk after it is already running off the table). What is the proper way to go about getting it there?
I thought I could just point the registry to the prototypejs repo on github, but that resulted in a checkout of files which did not include a built prototype.js file, and it seems it can't be built with the latest version of ruby/rake. So, one option would be to create a new github repo with the built version (downloaded from the website) and a bower.json file. Development on prototypejs seems to have stalled (according to github), so it is unlikely the author(s) would be doing that anytime soon.
DISCLAIMER
I'm beating my own drum but this should help
My PrototypeJS repo has updates in it as well as can be built using grunt and has the actual finished build files in it. Please take a look and see if it works for you.
https://github.com/jwestbrook/prototype
I would create a repo with as you suggested for now, but still try to submit a PR on the upstream repo.
I am upgrading magento version 1.5 store to magento version 1.7. Current store has more than 1000 products, more than 100 categories, more than 20 attribute sets, more than 500 customers,more than 500 orders and Database size is more than 600MB.
Above details are mentioned in order to have the idea of store size. Furthermore, I am trying it on local machine with wamp server installed.
Here are the steps involved to upgrade:
Export Current Database (Imported it in gzipped format with option "Disable foreign key checks" checked). As I was unable to export it in normal sql formate due to large size of database.
Created new database and imported the Database exported.
Downloaded fresh 1.7 stable version from magentocommerce.com
Tried to install this fresh magento 1.7 in newly created Database, in which exported database was recently imported.
Next steps were to install theme, copy extensions and copy media folders.
But when I tried to install magento 1.7, it always give me this error :
"This webpage has a redirect loop
The webpage at http://localhost/magento17/index.php/install/ has resulted in too many redirects. "
Here is the link to which I was following:
Link I followed
Note that my main focus is upgrading from 1.5 to 1.7, so much focus must be on that rather then resolving this issue if it is not the right way to do.
And If there is any better and proven way to upgrade to 1.7 from 1.5, kindly share it.
If you want to upgrade you dont need to install and move DB and theme.
Refer this link.
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/upgrading_magento
Note: If you followed best practices in Magento and didn't modify core code then upgrade should run smoothly.
Expected issues are that your Local and Community folder modules might need some fixes.
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.
i have magento 1.6.2 running on a dedicated server (ubuntu 10.04 lts)
I have tried various ways to upgrade magento to 1.7.0.2, but with no success.
Now i am thinking of installing a fresh magento 1.7.0.2 and rebuilding the shop.
This way i don't have the litter anymore of old deleted extensions.
But i want all my current data like products, orders, customers, mailinglist etc. imported in my new fresh installation.
How can i do this? Or isn't this a good idea?
I hope someone can help me ...
Try the Magento database repair tool:
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/db-repair-tool
I would install over what you have got after removing tables/keys that don't need to be there. The above tool will enable you to identify what is to be deleted. It will also give you confidence in your db build.
Not upgrading to latest version rather having a free install is doesn't seem to be a good idea because you can import all the products & Customers but there is no direct way to import the orders and other information on the fresh Installation.
I would personally suggest that you should once more try to upgrade to the latest version as I have upgraded several projects from Magento ver 1.6.2 to the latest and no such big issue occurred while upgrading.
Basic things you just need to keep in mind like keeping the back-up before upgrade and all..
Use the latest connect20 key for the upgrade i.e.
http://connect20.magentocommerce.com/community/Mage_All_Latest
Hope this helps or you can tell the errors that you are facing during the upgrade.
I have found it ...
A new installation will work in the following way ...
copy your db-base
copy your media folder to a new folder
than copy the fresh files downloaded from magento OS commerce to the server
install magento and fill in your db base credentials from point 1 ...
now you have a fresh installation, but with all your data (orders, customers, products, newsletters etc.)