Normally upgrading from Magento 1.0.19870 to 1.3.1 should be no problem, as Magento takes care of all the required table changes. I mostly faced script timeouts on the server in the past, which broke the upgrade process and turned the installation unusable.
I have switched to upgrading customer databases on a local installation, as that allows me to workaround timeouts and prepare databases for the upgrade.
Before upgrading an installation, you should also delete any content that can be recreated by Magento again. Logs, price rule caches …. can all be deleted, as the system can generate those again.
Really sad how everyone needs to piece those things together, as the Magento Community Knowledge Base is mostly outdated and many hints are buried deep inside the forums.
Currently working my way through a huge Magento 1.0.19870 database and will comment on my success once everything works.
Once you have done the export / import multiple times, it gets really easy :)
Here are some things that made things alot easier for me
Just check your old setup and update those tables by hand.
You can run queries by activating and deactivating the foreign key check like this:
SET FOREIGN_KEY_CHECKS=0;
INSERT INTO magento_core_website (website_id, code, name, sort_order, default_group_id, is_default) VALUES
(0, ‘admin’, ‘Admin’, 0, 0, 0),
(1, ‘base’, ‘Main Website’, 0, 1, 1);
SET FOREIGN_KEY_CHECKS=1;
You can choose which updates to list, when running the Magento Connect Manager. You can allow alpha, beta or only stable releases to be listed.
When saving your settings, the following file needs to be writable:
magento/downloader/config.ini
When it comes to permissions Magento Commerce is very picky, especially as pear requires full write permissions.
The following permissions should be used during install:
find . -type d -exec chmod 777 {} ;
find . -type f -exec chmod 777 {} ;
This will reset all permissions after you are done and secure your setup again:
find . -type f -exec chmod 644 {} ;
find . -type d -exec chmod 755 {} ;
chmod o+w var var/.htaccess app/etc
chmod 550 pear
chmod -R o+w media
When it comes to my development environment I have always been really picky. I need a clean and structured interface, not to cluttered, but still adjustable to my needs. I have tested countless IDE solutions in the past, but always seem to come back to Komodo from ActiveState.
When it comes to my development environment I have always been really picky. I need a clean and structured interface, not to cluttered, but still adjustable to my needs. I have tested countless IDE solutions in the past, but always seem to come back to Komodo from ActiveState.
“MetaNote intends to be the most versatile editor imaginable. Right
click on features in the editor and edit the code behind them. Don’t
like the way ‘Find’ works? — right click on it, and edit the code.
Need a new button in the toolbar? So add it already, with a single
click. Share packs of extensions and macros with other users.
Everything in MetaNote is under your control, effortlessly, at runtime.”
The project is still in its alpha stages, but a really unique approach. The developer is looking for people that like to jump in and help out making it as versatile as possible.
MySQLDumper is a backup programm for MySQL-Databases, written in PHP and Perl. You can dump your data into a backup file
and if needed, restore it. Especially on shared hostings without access to shell-commands, MySQLDumper is a sensefull
option.
MySQLDumper uses a proprietary technique to avoid execution
interruption. It only reads and saves a certain amount of commands and
then calls itself via JavaScript and memorizes how far in the process
it was and resumes its action from its last standby.
MySQLDumper restores a backup file by using the same process. Unlike
other tools splitting and splicing of large files is no longer
necessary.