hectavex

<p>New providers and features are being added regularly! See the <a href="https://wordpress.org/plugins/wp-oauth/changelog/" rel="ugc">Changelog</a> for details.</p>
<p>As a reminder, WP-OAuth is a still a pre-v1.0 release, which means some features may not work as intended or might change over time. Please report any bugs/issues to the support forum so they can be fixed as soon as possible. Thank you!</p>
<h4>Facts</h4>
<ul>
<li>With so many sites offering membership now, users may suffer registration fatigue and forget their passwords, or use the same password for several sites, increasing their security risk.</li>
<li><a href="http://www1.janrain.com/rs/janrain/images/Industry-Research-Value-of-Social-Login-2013.pdf" rel="nofollow ugc">56% of consumers</a> have at least one major social network profile they could be using for membership, registration and login purposes across multiple websites without having to maintain multiple accounts and passwords (2013).</li>
<li><a href="http://www.marketingprofs.com/charts/2012/7060/social-media-users-prefer-social-login-over-traditional" rel="nofollow ugc">40% of consumers</a> currently utilize social login (2012).</li>
</ul>
<h4>Features</h4>
<ul>
<li>Free, unlimited, unbranded and white-labeled from the beginning. No upselling, no payment plans, no SaaS, no proxy authentication! WP-OAuth communicates from your WordPress site <em>directly</em> with the <em>trusted</em> third-party login providers.</li>
<li>WP-OAuth collects and stores ONLY the user’s <em>OAuth identity</em> in the WordPress database for future logins; no other user information is collected or stored.</li>
<li>Fully integrates with WordPress. Drops into existing WordPress sites and integrates with existing WordPress users.</li>
<li>Supports third-party authentication with Google, Facebook, LinkedIn, Github, Reddit, Windows Live, PayPal and Instagram via OAuth 2.0 / OpenID Connect. Providers can be enabled or disabled.</li>
<li>Automatic user registration if <em>Anyone can register</em> has been enabled under Settings > General > Membership.</li>
<li>Users can manage their third-party login providers via the standard “Your Profile” WordPress page. They may link more providers, or unlink existing providers.</li>
<li>Displays a message via Javascript to the user when they login or logout. This feature can also be disabled.</li>
<li>Add a custom login form to any post or page using the [wpoa_login_form] shortcode. Choose from 4 different layouts. See <a href="https://wordpress.org/plugins/wp-oauth/installation/" rel="ugc">Installation</a> for details.</li>
<li>Customize the default login screen with a logo or background. Point the logo URL to your home page instead of WordPress.org. Hide the default username/password login form if you want. Automatically include login buttons for any providers that are enabled.</li>
<li>Supports cURL or stream context for the authentication flow, meaning the plugin should be compatible with a wide range of PHP servers.</li>
<li>The authentication flow was adapted from code samples provided by Google, Facebook and LinkedIn. It has been updated, rigorously tested and debugged for solid error handling. Provider implementations share much of the same code (very high code re-use) and the differences between the providers have been fully documented.</li>
<li>The user experience and on-boarding process was inspired by StackExchange/StackOverflow login system.</li>
<li>Extremely light-weight, optimized code base for high performance. Doesn’t require third-party OAuth libraries; everything is built first-class into the plugin. Previously, WP-OpenLogin required LightOpenID and Facebook-PHP-SDK, but this is no longer necessary. Keeps the bloat low and the performance high. Tested with P3 Plugin Profiler, WP-OAuth’s plugin overhead is around 0.001 seconds which is 6x less overhead than Akismet in the same run! That means there shouldn’t be a performance hit.</li>
</ul>
<h4>How to Contribute</h4>
<p>Visit the <a href="https://github.com/perrybutler/WP-OAuth" rel="nofollow ugc">GitHub development repository</a>.</p>
<h3>History</h3>
<p>This project is a continuation of <a href="http://github.com/perrybutler/wp-openlogin" rel="nofollow ugc">WP-OpenLogin</a> which was originally developed with OpenID in mind. We’re moving on; OAuth 2.0 is now the standard.</p>


WP-OAuth

Allows users to login or register by authenticating with an existing Google, Facebook, LinkedIn, Github, Reddit (and more!) account via OAuth 2.0.

Wott

thhake

gjanes

<p>Browse your Google+/Picasa Web albums and select images or whole albums to insert into your posts/pages. This is an unofficial<br />
fork of Picasa Express 2.</p>
<p>The fork has been necessary because the authentication for private photo albums of “Picasa and Google Plus Express” has been broken since<br />
 April 2015 due to changes to the authentication protocol. This is the first release after a major change to the code. Please<br />
  be so kind and test this version before putting it into production.</p>
<p><strong>This fork supports OAUTH authentication with Google, so you can access private photos and albums again! Currently this only works on a blog-wide mode (Google+ Express access level: blog). I am working on a solution for a per user authentication.</strong></p>
<p>Upgrade notice:<br />
*   The plugin requires at <strong>least PHP 5.4</strong>. Using a version before PHP 5.4 leads to parse errors.<br />
*   If you have shortcodes for single images that have been generated using a prior version of “Photo Express for Google” (0.1) or “Picasa and Google Plus Express” (all versions), you’ll have to update them to make photoswipe work correctly. Please have a look into the FAQ.<br />
*   The prefix for all CSS classes has changed from “pe2” to “peg”. Please consider this when upgrading from “Picasa and Google Plus Express”.<br />
*   The function to store authentication data on a user basis has been removed. The use case for storing it on a per user basis was not clear. If you rely on this function, please post a feature request with your particular use case.</p>
<p>Features:</p>
<ul>
<li>Use your Google user to access your photos and albums</li>
<li><strong>Private</strong> album access after granting access via Google auth service</li>
<li>Select albums / images from GUI listing by album cover and name</li>
<li><strong>Mobile gallery</strong> display support with PhotoSwipe</li>
<li>Google+ style <strong>phototile</strong> gallery display or standard gallery utilizing native WordPress image thumbnail size</li>
<li>Create a gallery of a subset of photos from an album by <strong>filtering the album with tags</strong></li>
<li>Gallery and image shortcodes for display of entire album or selected images</li>
<li><strong>WordPress MU</strong> support – sitewide activation, users, roles</li>
</ul>
<p><strong>Additional settings:</strong></p>
<ul>
<li>Image link:
<ul>
<li><strong>Mobile gallery</strong> with PhotoSwipe – in desktop browsers PhotoSwipe is clean and works nicely.  On a mobile device, swiping between photos is supported</li>
<li>Custom thickbox with plugin – including keyboard navigation and Google+ view link</li>
<li>WordPress thickbox – using the integrated thickbox provided by WordPress</li>
<li>3rd-party thickbox – setup the thickbox class/rel, but rely on external library</li>
<li>3rd-party lightbox – setup the lightbox class/rel, but rely on an external library</li>
<li>3rd-party highslide – setup the highslide class/rel, but rely on an external library</li>
<li>Google+ image page – a direct link to the Google+ image page for the photo</li>
<li>direct – a direct link to the large photo</li>
<li>none – just the image thumbnails are displayed with no link</li>
</ul>
</li>
<li>CSS / style customizations for most tags created in galleries, photos & captions</li>
<li>Caption under image and/or in image/link title and gallery display</li>
<li>Alignment for images and gallery using standard CSS classes</li>
<li>Define <strong>Roles</strong> who are allowed to use the plugin</li>
<li>Switch from blog to <strong>user level</strong> for storing the user and private access token</li>
<li>Settings for single-image thumbnail size, single-video thumbnail size and large image size limit</li>
<li>Forcing SSL connection to the Google photo APIs</li>
<li>Optional caching of the Google photo API results</li>
</ul>
<p><strong>And by design:</strong></p>
<ul>
<li>Shortcodes inserted for both albums and photos in anticipation of changes forthcoming in Picasaweb to Google+ migration.</li>
<li>Support native WordPress image and link dialog for album image thumbnail size</li>
<li>Support native WordPress gallery captions</li>
<li>Multilanguage support</li>
</ul>
<h3>Old changelog of Picasa Express 2</h3>
<h4>2.2.10</h4>
<ul>
<li>Corrects a bug introduced in 2.2.7 regarding per-post options on thumbnail size setting</li>
</ul>
<h4>2.2.9</h4>
<ul>
<li>Corrects an undefined variable</li>
</ul>
<h4>2.2.8</h4>
<ul>
<li>Corrects a bug with non-proportional image thumbnail sizes</li>
<li>Corrects a bug with images displayed without a caption when captions are enabled, the alignment was not being properly assigned</li>
</ul>
<h4>2.2.7</h4>
<ul>
<li>Added an option to allow single image/video thumbnails to be configured non-proportionally</li>
<li>Added the configuration option for PhotoSwipe to prevent upscaling of images</li>
</ul>
<h4>2.2.6</h4>
<ul>
<li>Added a browser check for Photoswipe to switch to Thickbox if the client is using any version of IE, as the current version of Photoswipe has a bug in all versions of IE.</li>
<li>Standardized the image links in Thickbox-Custom to match those of Photoswipe.</li>
</ul>
<h4>2.2.5</h4>
<ul>
<li>Attempted a fix suggested by Google to show all tag search results correctly.</li>
<li>Corrected the use of the pe2_img_css and style options when displaying an album.</li>
</ul>
<h4>2.2.4</h4>
<p>Bugfix for image thumbnail size that was introduced in new posts created after<br />
installing version 2.2.3.</p>
<h4>2.2.3</h4>
<ul>
<li>Removed the “Video overlay” option and replaced with Google+’s native “play overlay” for videos</li>
<li>Bugfix: A PHP warning was being generated when a gallery shortcode was wrapped around individual images.</li>
<li>Bugfix: Removed the need for the alignX classes being added to the image when captions are being displayed below the image.  This was causing issues with certain themes, and is no longer necessary since the “Video overlay” is built into the thumbnail image.</li>
<li>Bugfix: Changes to the js include method for thickbox used by the dialog to hopefully help resolve some issues certain users are experiencing with media-upload.js</li>
</ul>
<h4>2.2.2</h4>
<ul>
<li>Changed the name of the plugin from “Picasa Express x2” to “Picasa and Google Plus Express”:
<ul>
<li>As Google migrates to Google+ from Picasaweb, so is/will this plugin</li>
<li>Renamed the plugin to hopefully help indicate that and assist with plugin searches</li>
<li>Plugin URL / SVN name that WordPress uses to update the plugin will remain unchanged so that plugin updates can continue to occur from older versions</li>
</ul>
</li>
<li>Removed the requirement of jquery.mobile for PhotoSwipe:
<ul>
<li>PhotoSwipe appears to work properly without jquery.mobile</li>
<li>jquery.mobile was causing many other issues with themes not designed for it</li>
</ul>
</li>
<li>Removed the reference to the 3rd parameter of “round()”:
<ul>
<li>The 3rd parameter of round() was introduced in PHP 5.3, so users of previous versions were getting a warning.</li>
<li>If PHP version is detected previous to 5.3, it will not call round with the 3rd parameter.  This may cause some rounding errors, but will not prevent it from working.</li>
</ul>
</li>
</ul>
<h4>2.2.1</h4>
<p>Phototile last row will now properly select a row template so the template<br />
number of images matches the number of images remaining, therefore preventing<br />
the last row of a phototile gallery from being incomplete.</p>
<h4>2.2</h4>
<ul>
<li>Phototile support for the image gallery
<ul>
<li>Google+ style phototile image gallery option</li>
<li>Thumbnail sizes are generated dynamically based on phototile layout</li>
<li>Set the width of the phototile container and the phototile layout sizes to match</li>
</ul>
</li>
<li>Bugfix for mobile device detection to enable mobile interface for “Touch” Windows 8 devices</li>
<li>Bugfix to move the is_mobile_device function into the class to prevent conflicts caused by the include</li>
</ul>
<h4>2.1</h4>
<ul>
<li>Mobile-friendly gallery option added:
<ul>
<li>The link option of <a href="http://www.photoswipe.com" rel="nofollow ugc">PhotoSwipe</a>, an open-source<br />
mobile-friendly image gallery.</li>
<li>This is now the default image link option as it provides superior performance in both desktop and mobile clients.</li>
<li>Added some additional options that display if PhotoSwipe is selected to configure the caption format.</li>
</ul>
</li>
<li>Some additional improvements to the preferences to clean things up and hide options that aren’t necessary based on other option settings.</li>
<li>RSS parsing option has been added to enable parsing the RSS to remove the caption entry for records where Google sends the caption as the image filename when the caption itself is blank. </li>
<li>Some bug-fixes related to caption width and non-width-based thumbnail scaling.</li>
</ul>
<h4>2.0.6</h4>
<ul>
<li>A small release to improve messaging for the Google username check and to<br />
clean up a few additional bugs</p>
<ul>
<li>Messaging when checking the username’s validity is now improved</li>
<li>The FAQ now includes an entry speaking to the old picasaweb “short username” that Google appears to have removed support for</li>
<li>Some shortcode attributes for gallery shortcodes were previously not being sent if changed in the dialog options.  Corrected this and the back-end processing to handle them.</li>
<li>Some internal code cleanup and addition of some shared code to remove duplicate code.</li>
</ul>
</li>
</ul>
<h4>2.0.5</h4>
<ul>
<li>A small release to add additional style control for captions.
<ul>
<li>Added the ability to set classes & styles for the P tag that contains the caption text</li>
</ul>
</li>
</ul>
<h4>2.0.4</h4>
<ul>
<li>A small release to add additional style control for captions.
<ul>
<li>Added the ability to set classes & styles for the A tag that wraps the img tag</li>
<li>Added the ability to set classes & styles on the caption container if captions are enabled for display</li>
<li>Fixed a bug that was preventing the width from being set for single-image captions, therefore preventing the caption from appearing at all</li>
</ul>
</li>
</ul>
<h4>2.0.3</h4>
<ul>
<li>A bugfix and feature addition update.
<ul>
<li>Fixed bug related to PHP short_open_tag use</li>
<li>Fixed bug related to image insertion in order</li>
<li>Added option to return HTML rather than pe2-image shortcode</li>
</ul>
</li>
</ul>
<h4>2.0.2</h4>
<p>A bugfix release to correct bugs with the options page and requesting auth<br />
tokens from an SSL-based site.</p>
<h4>2.0.1</h4>
<p>A small bugfix release to correct a fatal error when gathering the transport<br />
for user-based access levels.</p>
<h4>2.0</h4>
<ul>
<li>A major change release that adds a lot of new functionality:
<ul>
<li>Fixed a bug introduced by Google+ that was preventing private albums access</li>
<li>Added video support – video thumbnail images have a “video play button overlay”, and the link opens in a new tab for viewing on Google+</li>
<li>Added filtering albums with tags</li>
<li>Added built-in customized thickbox option</li>
<li>Added single-image shortcode</li>
<li>Single-image insert method now allows selecting multiple images to insert together</li>
</ul>
</li>
</ul>
<h4>1.5.4</h4>
<p>Picasa change URL for origin image so /s0</p>
<h4>1.5.3</h4>
<ul>
<li>WordPress 3.3 fixes</li>
<li>Gallery shortcode:
<ul>
<li><code>class</code>, <code>style</code> and <code>align</code> for gallery</li>
<li><code>img_class</code>,<code>img_style</code> and <code>img_align</code> for images inside gallery<br />
( align can be <code>none</code>, <code>left</code>, <code>right</code> or <code>center</code> )</li>
<li><code>img_sort</code> for sort images ( possible values: <code>none</code>, <code>date</code>, <code>title</code>, <code>file</code> or <code>random</code> )</li>
<li><code>img_asc=1</code> for ascending sort otherwise will be descending sort</li>
<li><code>caption=1</code> for use image description as image caption</li>
<li><code>use_title=1</code> for use description as image title</li>
<li><code>tag</code> for enveloping tag ( <code>div</code> by default )</li>
<li><code>thumb_w</code> and <code>thumb_h</code> for thumnails size and <code>thumb_crop=1</code> if you need to crop thumbnail to square </li>
<li><code>large_size</code> for limit opened image</li>
<li><code>link</code> for enveloping link (possible values: <code>none</code>, <code>direct</code>, <code>picasa</code>, <code>thickbox</code>, <code>lightbox</code> or <code>highslide</code> )</li>
<li><code>limit</code> to limit number of images displayed</li>
<li><code>hide_rest=1</code> include images over limit but with display:none. It’s for gallery script which show all images including hidden.</li>
</ul>
</li>
</ul>
<h4>1.5.2</h4>
<p>WordPress 3.2 fixes</p>
<h4>1.5</h4>
<ul>
<li>Save last state</li>
<li>Can limit the big size of images</li>
<li>
<p>Revoke access to private albums from settings</p>
</li>
<li>
<p>avoid some warnings for PHP4</p>
</li>
<li>Add error handling in several cases</li>
<li>remove SSL verification ( some hosts report the problem with ssl verification – thanks to streetdaddy)</li>
<li>increase timeout for connection with Google Picasa</li>
<li>add Picasa username test in settings</li>
<li>Envelop html special chars in titles</li>
</ul>
<h4>1.4</h4>
<ul>
<li>Some code was re-factored to be more extensible</li>
<li>Warning for non standard image library. Help and links. </li>
<li>Donate banner and “power by” link in the footer (of course you can disable link and banner in the settings)</li>
<li>New smart size for thumbnails</li>
<li>Options on fly</li>
<li>Insert Picasa album by shortcode</li>
</ul>
<h4>1.3</h4>
<ul>
<li>Define roles which capable to use the plugin</li>
<li>Switch from blog to user level for store Picasa user and private access token </li>
<li>WordPress MU support – sitewide activation, users, roles</li>
</ul>
<h4>1.2</h4>
<ul>
<li>Finally make compatible with old PHP versions</li>
<li>Access to private albums via granting on Google page. See FAQ for more details </li>
<li>Reload button in dialog to retreive last changes</li>
</ul>
<h4>1.1</h4>
<ul>
<li>Remove STATIC – should work with old PHP version. Optimize hooks and setting. Keep settings after deactivation.</li>
<li>Change Picasa request method. Remove WP cache – changes displayed immediatelly.</li>
<li>Add sorting ( date, title and file name , asc and desc ) for images in the dialog in settings. Without sorting should be displayed as in PicasaWeb.</li>
<li>Add ordering for images in gallery ( by clicking )</li>
<li>Add <strong>Highslide</strong> support</li>
</ul>
<h4>1.0</h4>
<ul>
<li>First public release</li>
</ul>


Photo Express for Google

Although this plugin hadn't been updated for a while, it still worked.

However it caused WordPress 5.9 to break completely.

Plugin is broken

Browse and select photos from any public or private Google+ album and add them to your posts/pages. This is an unofficial fork of "Picasa and Goo …

WP-OAuth vs Photo Express for Google