Easily upload media from Google Picasa Desktop into WordPress.
This is the result of a self test added in v0.7 to detect when the server is configured in a way that prevents required arguments sent by Picasa from being received by the plugin. This test is run anytime an admin screen is displayed. The self test results have also been added to the debug log report when the plugin debugging is enabled.
See next question regarding no files uploaded by Picasa for discussion on the symptom and possible solution.
The most likely cause of this problem is software between Picasa and the plugin that is removing HTTP Request arguments with a long name. When Picasa is sending the upload request, it uses a long argument name like
http://localhost:55995/4cb54313c490d285f54664e018d50799/image/e50b8dc1ae05b682_jpg?size=1024 in the request to the server. In my experience, the arguments used by Picasa have been 93 characters. Some server software like Suhosin (PHP security plugin) and modsecurity (Apache security plugin) can be configured to remove long argument names from the HTTP Request as a security measure. Unfortunately this has the undesirable side effect of breaking this plugin. There may be other security applications that will have a similar affect on the incoming HTTP Request.
Review the server error logs for possible clues. If Suhosin is configured, you might see an error like the following in the server error log:
ALERT - configured request variable name length limit exceeded - dropped variable 'http://localhost:51134/b921a58ec2806ab82f5399515fba226e/image/b0f008e85a4fa153_jpg?size=1024'
Check the Suhosin setting values for
suhosin.request.max_varname_length. A setting of at least 100 is recommended to allow the long argument names that are required by the Picasa engine. You might need to increase it further depending on the length of the dropped argument name observed in the error log.
The Apache plugin mod_security can also be configured to restrict the length of the argument name. The server error log message might look something like this:
ModSecurity: Warning. Operator GT matched 90 at ARGS_NAMES:http://localhost:55995/4cb54313c490d285f54664e018d50799/image/e50b8dc1ae05b682_jpg?size=1024. \[file "...modsecurity_crs_23_request_limits.conf"] \[line "23"] \[id "960209"] \[rev "2.2.1"] \[msg "Argument name too long"] \[severity "WARNING"] \[hostname "localhost"] \[uri "/picasa_album_uploader/selftest"] \[unique_id "Tl5bYgpABGUAAJ5HBIIAAAAK"] ModSecurity: Access denied with code 403 (phase 2). Pattern match "(.*)" at TX:960015-PROTOCOL_VIOLATION/MISSING_HEADER-REQUEST_HEADERS. \[file "...modsecurity_crs_49_inbound_blocking.conf"] \[line "26"] \[id "981176"] \[msg "Inbound Anomaly Score Exceeded (Total Score: 6, SQLi=, XSS=): Last Matched Message: Argument name too long"] \[data "Last Matched Data: 0"] \[hostname "localhost"] \[uri "/picasa_album_uploader/selftest"] \[unique_id "Tl5bYgpABGUAAJ5HBIIAAAAK"]
Depending on your configuration, the modsecurity configuration line affecting this size might look like the following. A setting of at least 100 is recommended to allow the long names used by Picasa.
Special thanks go to rbredow for the assistance in diagnosing this interaction with server software.
There are several possible failures:
picasa://. You could try to reinstall Picasa, which should cause it to register itself with your browser. You must also be using at least Picasa v3.0.
The .pbz file is dynamically created by the plugin due to the customization required in the contents. See the question below about the contents of the download for details. The name of the file is determined by the Site Name that is provided in Settings->General.
The URL used to generate and download the button file is generated based on the slug name assigned to the plugin. Assuming a simple default configuration, the URL would be: http://your-site.com/picasa_album_uploader/your-site-name.pbz
Once downloaded this file can be placed in the Picasa configuration directory and the button can be configured in Picasa the next time Picasa is launched. The configuration directory path is detailed further below.
There is no executable code in the download. It is comprised of two elements:
Yes! Just put the shortcode
[picasa_album_uploader_button] where you want the button to display.
Yes! The tool tip for the button will identify the name of the WordPress site associated with the button. You might want to change the button icon to graphically differentiate the connected WordPress installs.
The plugin also functions in a multi-site environment.
In the future, a setting will be allowed to override the button graphic. Right now, the only way to change the button is by replacing the file
picasa-album-uploader/images/wordpress-logo-blue.psd in the plugin directory with the desired content. This is a photoshop file and a compatible image editor must be used. The layer containing the button image must be named "upload-button". The image should be no larger than 40 pixels wide by 25 pixels high with 72 dpi resolution. The color model used must be RGB with 8 bits/channel and should use a transparent background. Full details can be found at the Picasa Button API reference.
The Picasa Desktop client is very picky about the format of the URLs that it will accept during the upload process and will only accept a simple URL consisting of a single filename. The use of the slash (/) and question-marks (?) in the URL syntax results in no files being uploaded by Picasa to the server. In order to satisfy this Picasa requirement, permalinks must be used.
The Picasa button contains a URL to your WordPress installation, including the slug name used by this plugin. If any portion of the URL changes, the button in Picasa must be replaced so that the button is sending to the correct location in your WordPress site.
You may freely change the format of your permalinks without affecting the ability to upload files from Picasa Desktop. You must however keep permalinks enabled as discussed above.
This is a real plugin that lives in the
wp-content/plugins/ directory and does not require special files to be placed in either your server root or in the
This plugin can be uninstalled from the WordPress Plugin Admin screen. An uninstall script has been provided that will perform the necessary WordPress cleanup.
your-site-name.pbzfile from the Picasa configuration directory on your computer.
Button files end with
.pbz and the location depends on the OS you are using:
Windows: C:\Program Files\Google\Picasa3\buttons XP: C:\Documents and Settings\Username\Local Settings\Application Data\Google\Picasa3\buttons Vista: C:\Users\Username\AppData\Local\Google\Picasa3\buttons OSX: ~/Library/Application Support/Google/Picasa3/buttons
Requires: 4.0 or higher
Compatible up to: 4.2.2
Last Updated: 2015-6-6
Active Installs: 500+
0 of 1 support threads in the last two months have been resolved.
Got something to say? Need help?