gj |

How to use Amazon Cloud Drive with Owncloud

PAJ — Wed, 10 May 2017 17:05:52 +0000

Amazon offer cloud drive storage for photos free for Amazon Prime customers. For less that 10 yoyos per month you can upgrade to an unlimited cloud drive storage plan.

Yes, I did just say unlimited storage.

This is pretty neat, but I already use an open source cloud storage system on my own cloud server – called er, Owncloud. Wouldn’t it be really nifty if I could attach the unlimited Amazon Cloud drive storage to my Owncloud.

Here is how to do it in 5 easy steps:

Sign up for an unlimited Amazon Cloud Drive storage plan at https://www.amazon.de/clouddrive
Install and configure acd_cli
1. pip3 install –upgrade –pre acdcli
2. acd_cli -v init
  1. authenticate with Amazon and save the generated oauth_data file to ~/.cache/acd_cli/oauth_data
Sync acd_cli
1. acd_cli -v sync
Mount acd with fuse
1. acd_cli mount –allow-other -i 0 /home/acd/
Create a new external storage folder in Owncloud
Owncloud External ACD

That’s it, Amazon cloud drive will now appear as an ACD folder in Owncloud.

Is it really unlimited? In their license agreement it says that your service will terminate if your usage “substantially exceeds or differs from normal use by other users”. Be sure to check out the fine print. A quick Google around shows users already at hundreds of terabytes which sounds good to me.

Magento, Poodle and Paypal – Disable SSL v3 Before December 3rd

PAJ — Thu, 27 Nov 2014 16:58:15 +0000

The so called Poodle security vulnerability was announced by Google last Month (October 14 2014).

The vulnerability effects SSL v3.0 a transport protocol which has been around for over 18 years and is used to secure various TCP/IP protocols the most common of which being HTTPS so it is present in a lot of client and server software.

The workaround fix to mitigate this vulnerability is to simply disable SSL v3 support and fallback (or upgrade) to using the newer TLS 1.x protocol.

The vulnerability seems to be a real cause for concern for a lot of companies especially Paypal who announced recently that the will disable SSL v3 support on the 3rd of December 2014.

How does this affect Magento

In respect to Paypal payments from your Magento store using either the Standard or the Express payment model Magento behaves like a client communicating with the Paypal API over SSL to complete the Payment / Checkout transaction.

When Paypal removes support for SSL v3 your Magento store will no longer be able to communicate with Paypal unless you disable the support for SSL v3.0

Simply put this means you will not be able to process any orders with the Paypal payment system. Not the best news at this time of year when many businesses are in the middle of their busiest time of year on the run up to Christmas.

HOW TO Fix Poodle for MAgento

Fortunately the fix is pretty straight forward and actually doesn’t really have anything to do with Magento at all but rather the configuration of your web server software on your Magento host.

First you need to determine if the host your Magento shop is running on is using the SSL v3 protocol.

If you have command line access to your host, login and run nmap with the following command :

nmap –script ssl-enum-ciphers -p 443 localhost

If your host is NOT vulnerable you will see

SSLv3: No supported ciphers found

If you don’t have command line access run an external scan from a reputable site such as Symantec, The scan should clearly show you if your server supports SSL v3 or not.

How to Disable SSL v3 on Ubuntu Server

To upgrade to TLS 1.x and disable SSL v3 support on Ubuntu server, and many other servers running Apache locate the configuration file responsible for defining the SSL protocols supported by Apache. On Ubuntu it is

/etc/apache2/mods-available/ssl.conf

You can search for it with this grep command:

grep -i -r “SSLProtocol” /etc/apache2

Edit the file, find the SSLProtocol line and change it to

SSLProtocol all -SSLv2 -SSLv3

Restart Apache (service apache2 restart) and SSL v3 will be disabled.

Confirm this by running the scans again.

How to test Paypal

The best way to prepare for Paypal disabling SSL v3 is to test your Dev Magento install against the Paypal Sandbox site – http://sandbox.paypal.com

For peace of mind you should do this before December 3rd 2014.

Another simple test is to just do a simple PHP curl request to the Paypal sandbox servers. You can try this with a simple PHP script. Create a file paypal-tls-test.php in the root folder of your Magento shop and paste the following script into it.

$url = “ssl://www.sandbox.paypal.com”;
$fp = fsockopen ($url, 443);
if (is_resource ($fp)) {
echo “not affected”;
}
else {
echo “affected”;
}
?>

Run the script from your store – http://storeurl.com/paypal-tls-test.php

If you receive the not affected response, then your host was able to talk to Paypal using TLS and you should also be able to process Paypal payments from Magento.

If you don’t have a dev server this might be the easiest way to test Paypal access from your Live server unless you are prepared to take the shop offline and configure the Paypal payment modules to use the Sandbox.

If you do not have access to the command line you need to talk to your hosting provider ASAP!

A lot of people (like me) may be reacting to this news a bit late but applying these simple changes should avoid any pre Christmas Poodle related Paypal headaches next week.

Javascript only EU Law Cookie Notification Message for WordPress and Magento

PAJ — Wed, 12 Feb 2014 18:49:40 +0000

You know sometimes you just want a quick solution to a problem and wherever you look there are just complex, overpriced scripts that make your simple problem sound like something that needs a lot of code and money to get to work.

I needed to display a cookie notification message on a wordpress and magento site, to avoid compatibility problems I wanted to avoid using jQuery and just do it as simply as possible in javascript.

After looking around at a lot of $10 jQuery solutions I found a free javascript only solution, modified it for Magento and WordPress and implemented it.

Download the code from Github here

Whatever your opinion of the EU Cookie Law which came into effect in 2012, sooner or later if you are in Europe you may need to show that you are doing something about it. Err actually it’s 2014, so I guess we are already a teeny weeny bit late.

From what I understand the law may differ in various countries (certainly outside Europe), so depending on where your website is, and who visits your site the law may or may not apply to you.

This script will let you quickly implement a cookie notification banner with a link to your privacy policy. The notification itself uses cookies and will not be show again when closed.

You can implement this solution on any website by copying the install files to your web server and adding the following code to the footer of your site.

This sets up some variables used by the script, the URL of the privacy info page, the lifetime of the cookie used by the script in days, messages displayed, the option to fade the message automatically and the path to the install folder – used to display the close image.

For wordpress simply paste this into the footer php file of your theme.

For Magento paste this into the footer.phtml template file of your Magento theme. You can translate the messages, and perhaps a good idea, choose to display the message only on non SSL pages – we don’t want this javascript to somehow screw up a sale!

Here I am manually checking the store id and translating the text to German. Remember to refresh your Magento cache after editing and saving the footer template file.

You can see the code working on this WordPress blog below, and also with Magento on my Magento development site.

Tested with Magento 1.8.x, WordPress 3.blah, Chrome, Firefox, IE11. Detects mobile devices and modifies banner size accordingly.

Enable Magento iPhone Theme for Mobile Browsers

PAJ — Mon, 13 May 2013 13:57:27 +0000

Do you know how many of your customers are visiting your site using a mobile device? If you don’t, take a quick look at your Google analytics and check the figures under Audience -> Mobile -> Overview and Devices. If the % of visits from mobile devices is more than 10% of your total site visits then you might want to think about providing specific content for mobile visitors to your Shop otherwise you maybe losing out on sales.

Mobile Device Visitor stats from Google Analytics

Since Magento v1.4.x a built in mobile theme called iPhone is included with the source code.but it is not enabled by default. Here is a quick fix to enable the built in Magento iPhone theme for your Magento store to provide a better browsing experience for visitors using mobile devices.

Login to admin and goto System -> Configuration. Click on General in the left hand menu and then Design. Expand the theme section and then configure the following exceptions under Templates, Skin and Layout.

Matched Expression – iPhone|iPad|iPod|Android|IEMobile

Value – iphone

Configure Exceptions for iPhone Theme

Click Save to save your settings.

Notice the user agents in the matched expressions, these define which mobile browsers identified by User Agent should use the mobile theme. The iPad has a fairly large screen so you might decide to exclude that for example.

If you visit your store now with a mobile device you will see the default iphone theme in action.

Magento Default IPhone theme

Actually – its not very good is it, but it’s better than nothing and provides a good place to start building your own mobile theme. Alternatively (and I don’t say this very often) invest some $$ in the Aheadworks Mobile theme because it really is excellent.

Whichever mobile theme you decide to use make sure you test it thoroughly on your staging server, especially if you have a lot of extension modules installed. You may need to customise the mobile theme to achieve the same functionality as you have from your desktop version. Remember to include an option switch from desktop to mobile versions on both sites so that visitors can also decide which theme they want to use.

For testing (if you don’t have a mobile device) set the user agent in your browser to a mobile browser i.e. iPhone. This is possible in Safari by enabling Developer Mode and clicking Develop -> User Agent and selecting a mobile version of Safari from the drop down list. If you are a Mac user you can also use Xcode to run up an iPhone simulator as used for the screenshots above.

If your desktop site uses Flash, now is the time to start replacing it with HTML5

Cannot log into Magento Admin? Magento Admin not loading? Magento Cache Refresh Script

PAJ — Mon, 22 Apr 2013 15:22:00 +0000

It is possible to lock yourself out of the Magento back end admin interface simply by disabling a module which affects html rendering and stops you from logging back into the admin interface – which you need to do to re-enable the module – DOH! Its a real catch 22 situation.

If you are locked out of Magento admin, or your admin pages are not rendering correctly due to an admin change this post may just save your bacon.

If you have disabled an extension and need to re-enable it but the admin interface is not working, load up PHPMyAdmin and browse to your Magento database. Find the core_config_data table and then page through all the config options until you find the advanced/modules_disable_output rows. Find your disabled module – it will have a value of 1, and change the value back to 0 to enable it.

Paste the following code into a new .php file and save it to the root folder of your Magento store and run it in your browser. It will refresh the Magento cache, and re-enable the disabled module. Hopefully you should then be able to access admin again.

Depending on what has gone wrong with your configuration this may not always work, but if you have modified an admin config that for whatever reason has locked you out of admin then this method may work for you. It certainly is less painless than a full DB restore which is perhaps your other option.

Here is the cache refresh code.

 setUserId( 0 );
Mage :: getSingleton( 'admin/session' ) -> setUser( $userModel );
echo "Refreshing cache...\n";
Mage :: app() -> cleanCache();
$enable = array();
foreach ( Mage :: helper( 'core' ) -> getCacheTypes() as $type => $label ) {
$enable[$type] = 1;
} 
Mage :: app() -> saveUseCache( $enable );
echo "Cache refreshed";

Facebook Magento Store Front Shop Tab Application

PAJ — Sun, 28 Oct 2012 09:30:06 +0000

I saw an email last week from a company offering a Facebook store front tab application service for Magento that imports your Magento products and creates a basic Magento store front presence in a Facebook tab application. I thought this was a pretty neat idea especially if you are using Facebook as a marketing tool for your Magento e-commerce site. What I did not find so neat was the price, they want upwards of $1000.00 per year for a fully dynamic storefront with up to date products and support.

Having recently done some work both with Facebook tab apps and exporting Magento product collections in PHP I thought that this is actually a pretty easy task to achieve and coded up an example Facebook Magento Store Front running in a Facebook tab that presents a simple view of your products, product information and a direct link to the product on your Magento web for customers to place orders.

The app talks directly to your Magento database so it will always be up to date. It supports multi language stores and will detect the customers browser language and switch languages accordingly.

This is really a quick win app, integrating quickly with your Magento installation and takes about 30mins to setup and get up and running in Facebook.

Check out my demo Facebook storefront / shop tab app here.

Update

This app has been replaced by version 2. You can see it working here.

DOWNLOAD

Download the latest version of the application source code here.

Basic installation and usage instructions below.

12.11.2012 – v0.97 – bug fixes and changes to user configuration setup, user config now held in .ini file.
22.11.2012 – v1.0.1 – first public release

Magento Facebook Store Front Tab

Magento Facebook Store Front Tab Application

Introduction
Prerequisites
Installation
Configuration
Usage
Languages

Introduction

Magento Facebook Store Front Tab is an object oriented PHP script that integrates with a Magento installation to render product HTML designed to be displayed within a Facebook Tab. The application is able to render various product views, all products, new products, categories etc. with a simple product description and link to your actual Magento web store for purchases.

The application supports normal desktop clients.

Prerequisites

This application requires a configured Facebook Account, Facebook Page and a configured Facebook application. A good knowledge of your Magento installation and Operating System is assumed as well as some experience with Facebook applications and PHP.

Installation

Extract the source files ideally to a sub folder of your Magento installation. e.g. /home/www/magento/facebook

A new folder ‘magentotab’ will be created. Feel free to rename this folder if required.

The application will then be accessible from your browser via the following url

http://www.YOURSHOP.com/facebook/magentotab

Where www.YOURSHOP.com is the url to your Magento shop frontend. If you install the application somewhere other than your Magento installation folder then you will need to browse to the application via your configured web server path.

Configuration

Edit the file applicationConfig.php in /magentotab/config.

Edit

const PATH_TO_MAGENTO_INSTALLATION = ‘/home/www/dev/magento/’;

With the actual path to your Magento installation.

Edit fbAppID, fbAppSecret and fbUrl with the App ID, Secret and URL from your configured Facebook app.

To display a menu on the product page set the showMenu constant to true. Depending on traffic and your hosting etc. the application may run faster when the menu is disabled.

To exclude categories from being shown in the product menu, configure the excludedProductCategories constant with a list of category id’s separated by a comma, e.g.

const excludedProductCategories=’4,5,16,17,18,19,22,23,25,27,28,29,30,31,32,33,34,35,37′;

For google UTM tagging configure the googleUTMTag constant with a valid Google UTM URI.

The bannerImage constant holds the name of the graphic file used as the banner at the top of the Facebook Tab page.

Set the productLimit constant to define the number of products that will appear per page. This should be divisible by 9.

Set the defaultCollectionType constant. This defines the default product view that will be shown. Options are

newfromdate – Products set with the NEW FROM attribute – i.e. New Products.

allproducts – All Products

categoryproducts – Products from a category.

Determine which product description will be shown for the product

useShortDescription=true – Use short description

useLongDescription=true – Use long description

Configure language options

const storesConfigured=’1,2,3′;

const storesLanguage=’de,en,fr’;

const storeDefaultLanguage=’en’;

In this example there are three stores configured with the id’s 1, 2 and 3. The store languages for store 1,2,3 are de, en, fr – German, English, French. And the default language is ‘en’ – English.

The showContact and showAbout constants enable a Contact and About button on the menu when set to true. This is currently in development.

The allowStandAlone constant lets the application run in a standalone browser when set to true. When set to false the application will redirect to the Facebook URL of the app. Set to true for debugging the app standalone outside of Facebook.

Set the pageLikeRequired constant to true if visitors must first Like the Facebook page the tab is running in before they can access the application.

Set the URIToApp value to the URI path of the app on your server.

Save the configuration file.

Usage

To run the script for the first time browse to the URL of the script as defined above

i.e. http://www.YOURSHOP.com/facebook/magentotab

If the Magento configuration path is correct you should see a list of products displayed, with or without menu options as specified in the configuration.

If the application works correctly standalone then you are ready to integrate it with Facebook.

To install the application as a Facebook Tab ensure that your Facebook application has been created and configured with the correct canvas URL’s to the application and then goto the following link

http://www.YOURSHOP.com/facebook/magentotab?fbtab=true

This will return a link that will start the Tab installation process via Facebook. Select the Facebook page to install the Tab on.

When the Tab is installed goto your Facebook page to confirm that the app is working.

Languages

To translate some of the interface text used in the application to your language, simply create a new language file in the php/locale folder named XX.txt where XX is your two letter language code. Use an existing language file as a template and add your translations to the file in the format

Text=TranslatedText.

Make sure your language settings are configured correctly in the application. You can force the application to the language you want using the storeid variable in the url

i.e. http://www.YOURSHOP/facebook/magentotab/?storeid=2

Will force the application to the language configured for store id 2.

Generate EAN Barcodes for All Magento Products – Magento EAN Barcode Generator

PAJ — Wed, 10 Oct 2012 13:09:07 +0000

Generate EAN Barcodes for All Magento Products

Following on from my post about mass exporting Magento data, I had the requirement to also mass generate EAN13 barcodes from scratch for all Magento products in a store.

The barcode graphic functionality came courtesy of Folke Ashberg and I simply added the functionality to my basic export php script.

The script creates the EAN code and checksum (currently programmed for EAN13) using the a 5 digit product number derived from the Magento product id and your registered manufacturer code. The barcode image is generated on the fly and cached locally.

My requirement was to generate the EAN code and not the barcode image so I am not 100% if the image is to the EAN standard, I think the font may need to be changed, however if you require EAN numbers and images, e.g. for Amazon etc. then this is a good place to start!

Magento EAN Generator

You can download a standalone version of my Magento EAN Generator from GitHub here. Install the code in a web accessible folder, or in your Magento installation folder. Open the application config file and configure the correct path to your Magento installation. Also configure your EAN prefix code.

Run the script by browsing to http://www.yoursite/eaninstallfolder/ean.php?export, this will generate a delimited txt file containing SKU and EAN13 code for all visible products in your store.

Or run the script from the command line using

php php.ean debug

< MAGENTO EAN -> D E B U G >
Exporting EAN data for 64 Magento product/s …
Data file created at /home/www/dev/magento/myexport/eanexporttest.csv
Export finished.

Configure a writeable folder for the data file in config.

The CSV file contains the EAN data

sku,ean
COOLSAUCE1,1234567001746
Honeypot-1,1234567001739
gaiterjones-1,1234567001715
HTC Touch Diamond,1234567001661
mycomputer,1234567001654
computer_fixed,1234567001647
computer,1234567001630
micronmouse5000,1234567001623
logidinovo,1234567001616
logitechcord,1234567001609
microsoftnatural,1234567001593

You can see an example of the scripts output here.

Auto Generated Magento Product EAN13 Barcode

You might want to validate the generated EAN codes, specifically to validate the 13th checksum code, do this here.

WordPress MultiLanguage Support the Simple Way

PAJ — Fri, 14 Sep 2012 12:43:24 +0000

WordPress is a great multilanguage CMS, for a while I thought of it purely as a blogging tool but now I use it all the time when I need to build a quick and effective marketing site. If you find a theme that you like and is adaptable you can put together a professional, great looking site that is easy for you or your clients to maintain in very little time.

Getting WordPress to work well with multi language content isn’t so straight forward, there are a lot of plugins available that offer multi language solutions but these seemed to be over complex for what I wanted.

My WordPress marketing sites are relatively simple with just a few pages used as marketing landing pages and stepping stones to e-commerce sites. I already created a simple method in PHP of detecting browser language and matching language to content in my pages however the WordPress frontend language remained in the default language of the installation. I did not want to modify core template files within WordPress as this makes upgrading difficult so after wasting time with Plugins I developed a very simple solution that sets the WordPress interface language for each visitor based on their browser language.

The WordPress WP-CONFIG.php file holds the main configuration settings for your WordPress installation, a global PHP constant WPLANG is defined here that sets the admin and frontend interface language using standard country and language codes, the default if WPLANG is not specified is American English en-US.

WordPress language packs come in .mo files that are located in the WordPress wp-content/languages folder, they are named after the language code, i.e. en_US.mo, de_DE.mo etc.

By detecting the browser language of the visitor and then checking if a corresponding .mo file exists in the languages folder we can automatically switch the WordPress interface language to match the visitors browser language – nice!

Decide which languages you want to support and download the corresponding .mo files, you can find all the language files available in the WordPress language file repository here http://svn.automattic.com/wordpress-i18n/ e.g. here are the German language files http://svn.automattic.com/wordpress-i18n/de_DE/branches/2.8/messages/

If your WordPress site does not have a wp-content/languages folder, create a new one and copy your language files into it. Note you should copy your default language file too.

Now edit the WP-CONFIG.php file in the root folder of your WordPress installation and find the WP-LANG constant definition and comment it out:

#define (‘WPLANG’, ”);

and below it paste in the following code

/**
 * Set language and load language files
 */
function detectlanguage() {
    $langcode = explode(";", $_SERVER['HTTP_ACCEPT_LANGUAGE']);
    $langcode = explode(",", $langcode['0']);
    return $langcode['0'];
    }

function fileExists($fileName, $caseSensitive = true) {

    if(file_exists($fileName)) {
        return $fileName;
    }
    if($caseSensitive) return false;

    // Handle case insensitive requests            
    $directoryName = dirname($fileName);
    $fileArray = glob($directoryName . '/*', GLOB_NOSORT);
    $fileNameLowerCase = strtolower($fileName);
    foreach($fileArray as $file) {
        if(strtolower($file) == $fileNameLowerCase) {
            return $file;
        }
    }
    return false;
}	

$languageDefault='en_US';
$language = detectlanguage();

if (isset($_GET['set_lang'])) { $language = $_GET['set_lang']; }

$languageFile= 'wp-content/languages/'. str_replace('-','_',$language). '.mo';
$wpLanguageFile=fileExists($languageFile,false);

// check if WP language file exists for browser language
if ($wpLanguageFile) {
	$wpLanguageFile = basename($wpLanguageFile, '.mo');
	// language supported
	define ('WPLANG', $wpLanguageFile);
    //echo "Language - $language detected. Language file exists and is supported."; 
} else {
	// language not supported default to EN
    //echo "Language - $language detected. Language file does not exist - defaulting to $languageDefault."; 
	define ('WPLANG', $languageDefault);
}

Save the file and test. You can force the language selection by specifying it in the URL, i.e. http://yourwordpresssite.com/?set_lang=de_DE which will force the interface language to German if you have the German language files installed. Uncomment the echo’s and you will see the language selection confirmed.

If all is working well the WordPress interface language will now switch to the browser language of your visitors.

Note that this will only change the language of the built in WordPress interface in the frontend or backend. Your content language will not change, you need to create a translation system for your content using portable object files, or alternatively use the Google translation tool.

Magento – How to remove Quantity input box and Delete button for Free cart items

PAJ — Mon, 08 Aug 2011 13:09:23 +0000

For Magento 1.4.x +

BuyXGetYFree items are added and removed automatically by the extension cartcontroller code. To prevent customers from manually deleting free products from the cart we can change the template to remove the delete button and input qty box for items in the cart with a Zero value.

This code is based on the default Magento theme template.

Remove Delete Button

Open the following template file for editing:

app/design/frontend/base/YOURTHEME/template/checkout/cart/item/default.phtml

Search for “Remove item” in the default theme appears on line 243.

Replace

__('Remove item')?>

With

getCalculationPrice()=='0'): ?>


__('Remove item')?>

Remove Qty input Box

Search for “input-text qty”, in the default theme appears on line 156.

Replace

With

getCalculationPrice()=='0'): ?>
getQty() ?>

Refresh cache, and reload cart to test, free items should no longer have a delete button or input quantity box.

Remove delete button and quantity input box for free cart items

Google Plus One button for Magento Products

PAJ — Fri, 01 Jul 2011 10:18:30 +0000

Google launched their Plus (+) range of products this week, Google + integrates existing products from Google along with some new social products into a new “social networking” service. Obviously Google want to challenge Facebook as a new social networking hub. While Facebook already have a huge user base, it is nothing compared with the number of users interacting with Google on a daily basis.

Interestingly, as Facebook attempts to assimilate the Internet into its own social networking open graph database populated with millions of people, Google , who already have the Internet indexed and cached in its huge databases now want to pull in the millions of people to create a social networking environment built around existing, new products and of course their number one business their search engine.

Enter the Plus One Button

The Google plus one button is to Google searches what the Facebook like button is to web content. Google says “The +1 button is shorthand for “this is pretty cool” or “you should check this out.””. When you or someone in your Google social circle “plus one” something by clicking the plus one button on a site, this information will be used by Google to manipulate/improve Google search results so that when you search for something you will be able to see for example if your friends have already recommended the product returned in the search. If your best buddy likes it, it must be good right? Whether its “pretty cool” or not lets wait and see, no doubt Google Plus will be THE next big thing. The plus one button is a clever way for Google to rewarding good web content and personalise search results, as (in theory) only humans will be able to “Plus One” something.

I am still getting my head around Google plus one and all of its implications but needless to say if there is a new social media marketing opportunity out there, especially one so tightly integrated with Google search then we need to take advantage of it and enable plus one buttons for our Magento products. Content with a large amount of +1s will get higher rankings in Google’s organic search results, create more visibility for your products and drive more traffic to your site. Google says “Think of the +1 button as a way for fans of your business to recommend what you offer, for all their friends and contacts to see. By helping searchers see more personal, relevant ads, we believe you’ll see more qualified traffic.”

Here is a 5 minute fix to add the plus one button to all Magento product pages.

Adding Plus One

For Magento 1.4+ stores:

We can place the Google plus one button next to our Facebook Like button with a few lines of code. Locate view.phtml in your theme, it will be located in the default/template/catalog/product folder of your theme.

If you already have implemented a Facebook Like button, insert the following code below the existing code You can also position the google-plusone DIV wherever you would like the button to appear on the page with CSS.

To translate the locale code correctly add a line to your themes locale file and refresh your cache. For example for a German language store use

“en-GB”,”de”

Google Plus One Button for Magento

For Magento 1.4+ make sure you have canonical URLs enabled in admin (see my Facebook Like button post for more info), we have specifed the URL in the Google API code to ensure Google uses the Magento enabled canonical URL. They say that the code will default to look for the canonical tag but better to be safe than sorry – in my tests it was not always used. The size and appearance of the button can be modified by changing the size and count options. See the Google documentation for more details.