gnu-social

History

Diogo Cordeiro 8c0601816f [CORE] Move core plugins to a new modules directory For reference (raised by rozzin in IRC): * http://foldoc.org/module * http://foldoc.org/library * http://foldoc.org/plugin As noted by XRevan86, modules are not necessarily non-essential. As we will keep the modules directory in GS root [therefore, near to plugins/], it is evidenced the difference between both. This is a simple yet fundamental structural change. It doesn't change functionality but makes clearer the way we understand GNU social's internals.		2019-08-22 03:13:58 +01:00
..
actions	plugins onAutoload now only overloads if necessary (extlibs etc.)	2013-08-28 16:10:30 +02:00
locale	[CORE] Move core plugins to a new modules directory	2019-08-22 03:13:58 +01:00
BitlyUrlPlugin.php	[ROUTES] Allow accept-header specification during router creation	2019-08-03 17:47:16 +01:00
README	Add a README for BitlyUrlPlugin	2010-10-07 13:23:18 -07:00

README

bit.ly URL shortening requires the login name and API key for a bit.ly account.
Register for an account or set up your API key here:

  http://bit.ly/a/your_api_key

Administrators can configure a login and API key to use through the admin panels
on the site; these credentials will then be used for all users.

(In the future, options will be added for individual users to override the keys
with their own login for URLs they post.)

If the login and API key are left empty in the admin panel, then bit.ly will be
disabled and hidden from the list of available URL shorteners unless a global
default was provided in the plugin configuration.


To enable bit.ly with no default credentials, simply slip into your config.php:

  addPlugin('BitlyUrl');

To provide default credentials, add them as parameters:

  addPlugin('BitlyUrl', array(
      'login' => 'myname',
      'apiKey' => '############################'
  ));

These settings will not be individually exposed to the admin panels, but the
panel will indicate whether or not the global default settings are available;
this makes it suitable as a global default for multi-site hosting, where admins
on individual sites can change to use their own settings.


If you're using a bit.ly pro account with a custom domain etc, it should all
"just work" as long as you use the correct login name and API key for your
account.