Archive for January, 2012

How to add admins to a Google+ page

Thursday, January 26th, 2012

I’ve used the term admins as that is what Facebook calls them, but Google+ refers to extra users that are able to manage a business page as Managers.

  1. Go to your Google+ business page and make sure you are using Google+ as the page, not your personal account. The page name should be displayed at the top right.
  2. Click on the options icon (the cog) at the top right-hand side of the screen, then select ‘Google+ settings’
  3. On the following page you should see an option called ‘Managers’ on the left-hand side. If you don’t see it, double check that you’re signed in as the page and not your personal account.
  4. Select the Managers option and on the following page you are able to add another manager to the page via entering their email address. Make sure you enter the email address that is associated with the user’s G+ account.
  5. The user is then sent an invite which they must accept before they can manage the page. Until that time the invite is marked as ‘pending’.
  6. Once the user has accepted the invite you have the option to remove them from the same page. There’s also the option to transfer ownership if you’re no longer involved with the project or business the page is promoting.
Adding Google+ page Managers

Adding Google+ page Managers

 

Protocol Relative URLs

Tuesday, January 17th, 2012

Thanks to the excellent Paul Irish and HTML5 Boilerplate, I discovered an excellent nugget of information recently, that’s incredibly useful when building sites / web apps that need to work both on secure (https://) and non-secure (http://) URLs. This includes all Facebook apps since October 2011.

When linking to an external JS, css or image file that is available over both https:// and https://, you can use a URL of the form:

//domain.com/path/to/asset

for example (loading the jQuery library from Google’s CDN):

<script src="//ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.js"></script>

Your browser will request the asset using whichever protocol you’re viewing the current page in.

This has implications if your viewing a page locally via file://, which is why you’re always better off using a local web server rather than opening a file directly. There’s also an issue that causes IE7 and IE8 to download the file twice when this method is used in <link> tags or @imports statement within CSS, so I would say it’s best of avoided there. More details here.

This technique allows you to quickly and easily avoid the dreaded ‘this page contains both secure and nonsecure items’ warning in Internet Explorer.