A merchant must think first before going ahead with Paypal Express or Paypal Standard. I would suggest to go with Paypal Express that is found as one of the option by Paypal survey which can increase sales by 14% on average. Below is the difference between these two and may help you bit to decide best for your store…
If you use PayPal Express Checkout, when your customers check out, they will be taken to a page that requires them to log into their PayPal account or create a new one. Therefore, this is the best option if you think that most of your customers either have a PayPal account or will sign up for an account on checkout.
If you use PayPal Website Payments standard, when your customers check out, they will be directed to a page that allows them to log into their PayPal account or pay by credit card without having to sign up for a PayPal account. This is the best option if you think that most of your customers will not want to sign up for a PayPal account.
Today while designing a database for a system called LMS I was attacked by an strange error that was “MySQL Error Number 1005 Can’t create table {DBNAME}.{TABLENAME}.frm (errno: 150). On googling about the problem I found following may be the reasons causing the problem:
#1)- The two key fields type and/or size doesn’t match exactly. For example, if one is INT(10) the key field needs to be INT(10) as well and not INT(11) or TINYINT. You must confirm this by running the query “SHOW CREATE TABLE;” because sometime GUI tools like SQLYog & Query Browser show INT(10) as just INTEGER so may confuse you. Also confirm that both the fields are signed or unsigned. So I mean the fields should be exactly same, no mismatch at all at any level.
#2)- One of the key field that you are trying to reference does not have an index and/or is not a primary key. If one of the fields in the relationship is not a primary key, you must create an index for that field.
#3)- The foreign key name is a duplicate of an already existing key. Check that the name of your foreign key is unique within your database. Just add a few random characters to the end of your key name to test for this.
#4)- One or both of your tables is a MyISAM table. In order to use foreign keys, the tables must both be InnoDB. (Actually, if both tables are MyISAM then you won’t get an error message – it just won’t create the key.) While creating the table you can specify the Engine.
#5)- You have specified a CASCADE ON DELETE SET NULL, but the relevant key field is set to NOT NULL. So for this change either CASCADE to not to set NULL value or the field to accept the NULL values.
#6)- If you face the problem like your script is running perfectly on one server but not on another then collate or charset options may be different and may be causing the problem.
#7)- You have a default value (ie default=0) on your foreign key column.
#8)- One of the fields in the relationship is part of a combination (composite) key and does not have it’s own individual index. Even though the field has an index as part of the composite key, you must create a separate index for only that key field in order to use it in a constraint.
#9)- The name of your foreign key exceeds the max length of 64 chars.
I believe above are main causes behind the error if anyone run into this error and find that it’s caused by something else then please leave a comment, I’ll add this cause as well into the above list.
This is for the merchants using Payflow Pro and Website Payments Pro Payflow Edition as one of the payment option. PayPal is updating Payflow Pro and Website Payments Pro (Payflow Edition) . Due to various technical requirements, PayPal is upgrading the Payflow system to do away with the naming of the Verisign roots from which the Payflow service was derived.
This alert applies to:
- Payflow Pro gateway merchants (US, UK, and other parts of the world)
- PayPal UK merchants using Express Checkout and/or Website Payments Pro 2.0 Payflow Edition
If you are using one of these payment methods, you will need to update the URL’s in your Magento Administrator Panel in order to process transactions after September 1, 2009.
You can update the URL‘s prior to September 1 and it is suggested that you update as soon as possible.
No changes are necessary in the Magento code, only the URL‘s need to be changed in the System → Configuration Section of the Magento administrator section.
For merchants using Payflow Pro, these updates are inputted in System → Configuration → Payment Methods → Payflow Pro.
For UK merchants using Website Payments Pro (Payflow Edition) these changes are inputted in System → Configuration → PayPal Accounts → Website Payments Pro (Payflow Edition).
This is my very first post related with the Magento, an amazing E-Commerce platform, and I thought it would be good idea to start with the magento installation
Usually guys follow the long and tedious way to insall it like below-
1)- First download the zip/tar archive from the Magento Download — First time taking step takes around 15-20 minutes.
2)- Upload the archive via FTP (FileZila or FireFTP) to the server at appropriate location. — Second time taking step, another 15-20 minutes
3)- Unzip the archive and runs the installation process from the browser that doesn’t take much but still let’s count it and say 10 mins.
So if we count the total time then it is around 40-50 mins, isn’t it too much ? Now let’s see the smart way but you must have SSH enabled in your server, if it is not then you can ask from yours host provider to enable it.
1)- Login into the server using putty (Windows users) or SSH command ( Linux users )
2)- Go to the directory where you want to install the magento, if doesn’t exist then create it
3)- Run ( without double quotes ) “wget http://www.magentocommerce.com/downloads/assets/1.3.2.3/magento-1.3.2.3.tar.gz” – this will download the tar file to the current directory. I have used here magento current latest version, you can change version as per yours need.
4)- Run “tar -zxvf magento-1.3.2.3.tar.gz” – This will extract archived files within the magento directory.
5)- Run “mv magento/* ./” – This will move all the files from the magento directory to current directory. This command may not move the .htaccess file so please make sure that you shoot the following command also
6)- Run “mv magento/.htaccess ./” – This will move the .htaccess file to the current directory.
7)- Run “rm -rf magento” – This will delete the magento directory from which we have moved the complete content to current directory.
8)- Once we have located all the directories and files to the right place now we must set the appropriate permissions for the directories and files (777 to directories and 644 to files)
find . -type d -exec chmod 777 {} \;
find . -type f -exec chmod 644 {} \;
9)- Now all is set and can run the further installation process from the browser by typing the correct store location.
I am sure that one will compare the non-smart vs smart way with the number of steps i.e. 3 vs 9, yeah there is big difference in the number of steps but believe me it is going to take just 20 minutes and this makes the real difference. You can copy the commands from here and can paste into the shell (you may need to change the version as per yours need).
I hope this post will help magento developers to save some bits of their valuable time, if face any problem then post the problem as comment or drop me an email at anil[DOT]gupta[AT]treewalker[DOT].in.
