=== WPGPlus ===
Contributors: johneckman
Tags: google plus, platform, application, blog
Stable tag: 0.8.7
Tested up to: 3.8
Requires at least: 3.2

WPGPlus posts your blog posts to Google+ when published on WordPress blog. 

Currently works with plus.google.com accounts, provided:
 - You are NOT using "2 factor authentication"
 - You have accepted the terms of service and can successfully post using
   http://plus.google.com/app/basic/share/ on a mobile device
   
It does store your Google+ username and password in the WordPress database. 
This is not ideal from a security POV but is the only way to get it working when you
are not present to login. 

== Description ==

WPGPlus posts your blog posts to Google+ when published on WordPress blog. 

Posts are made to "Public" circle. If you include an excerpt (using the
post excerpt box, not just the "teaser" before the <more> tag) it will
be used, otherwise post-content is used. 

This plugin requires PHP 5 and a compatible transport layer for WordPress
HTTP API - most likely this means cURL. 

Still working on cleaning up the output, working on getting
Google+ to recognize the links posted, show images, etc. 

This plugin is based on Dmitry Sandalov's standalone PHP script for 
publishing to Google+ from php. 

== Installation ==

1. Copy the entire wpgplus directory into your wordpress plugins folder,
   /wp-content/plugins/

2. Login to Wordpress Admin and activate the plugin

3. Using the WPGPlus menu, (Dashboard->Settings->WPGPlus) fill 
   in the appropriate information including the email address you
   use to sign in to Google+ and your Password   

== Frequently Asked Questions ==

= Why aren't my custom post types or pages posted? =

WPGPlus is currently only set to post to Google+ when the post type is "post."

To enable other post types, open wpgplus.php and find the "if" statement in the
beginning of the wpgplus_update_profile_status() function, where the code checks
for if post_type is not equal to 'post' - comment that whole if() { } section out
to get all types, or add into the if condition all the post types you want to 
specifically include. 

= Why doesn't it work for me? =

Hard to say. Most likely this is due to either:
 * server config (no available HTTP transport that can POST to and GET from google+)
 * google+ account config (if your google+ account has two factor authentication
   set, or expects confirmation of your mobile phone number, or other security
   issues
 * google+ waiting for you to accept the mobile terms of service
You can enable debugging in the wpgplus settings page and see if that produces
useful output. 

= Can I post to pages instead of my profile? =

Not yet. Working on it. 

= Why does the plugin ask for my Google+ username and password? Why not use OAuth? =

Because for now the Google+ API offered by Google is read-only - no posting allowed. 

As soon as they release a read-write API I will work on switching to it and 
eliminate the need for username and password to be in the database. 

If you really don't want your username and password in the WordPress database, 
you could hack the wpgplus_login_data() function and hard-code your username and
password into it - they'd still be accessible to someone with filesystem access. 

== Changelog ==

= 0.8.7 = 
* Added better checking for redirects where the 'baseurl' is not returned as part of the
  redirect and has to be manually added. For now I'm just adding plus.google.com but 
  ultimately this will need to be parameterized
* Request form directly at /app/basic/share/ rather than old url  

= 0.8.6 = 
* Restarting development. Got a test version working with Google+ in the us - changes
  to all the redirects it goes through, now using /app/basic/share/ instead of the 
  older mobile version
* Updating notes in the readme to clarify what does not work - 2 factor auth, non-US

= 0.8.5 =
* Setting redirection back to 5 on the login check. I'd prefer not to rely on redirection
  this way, given that on some hosts curl redirection isn't allowed, but that will require
  a more fundamental rewrite I haven't had time to do. (I'd have to handle the redirection
  myself as current is done during the posting process, and all the variants for different
  global versions of google+

= 0.8.4 = 
* Was not checking for wp_error object on first request, now we are

= 0.8.3 = 
* One user reported multiple posts to Google+ for one WordPress post, so I tightened
  the final POST to google+ to not follow redirects, which should not be required. 
  
= 0.8.2 = 
* That's what I get for weekend coding. Left a number of old debug statements
  in the main plugin file that weren't using the new function. 
* Updated plugin requirements - needs WordPress 3.2 as a major issue with redirection => 0
  was fixed in that release. Given 3.4 is out now I'm ok with that. 
  
= 0.8.1 =
* Left an outdated "echo" statement in the logout function for 0.8 - fixed

= 0.8 = 
* Extensive re-write to be more "WordPress Like"
* Replaced cURL calls with wp_remote_request, wp_remote_post, and wp_remote_head
* Storing cookies returned by Google+ in WordPress transients
* Debug is now an option 

= 0.7.3 = 
* Checked for login form being presented by google else it will fail
* Wrapped calls to curl_setopt() for FOLLOWLOCATION - now checks to see if that
  setting was successful and dies if it was not. 
* Wrapped fwrite calls for debug.txt in checks for valid file pointer first.

= 0.7.2 = 
* Adding further detection for cases where Google+ returns a client-side
  redirect in response to a login request, rather than returning the right form


= 0.7.1 =
* Fixed bug in which message and publish meta were being duplicated
* Turned off debug logging including password - not good for production environment

= 0.7 = 
* Added more debugging output
* Shifted to loadHTML, suppressed warnings from loading DOM

= 0.6 = 
* Added post-meta box for Google+ message

= 0.5 =
* Initial release

== To-do ==
* Get google+ to recognize URL of permalink and treat it as it does from
  web client - image, excerpt
* Explore full web interface not mobile one, which is limited in functionality
* Posting to pages?