From 449027d0869bb57bbbfaf6e5a9994326bb335fb9 Mon Sep 17 00:00:00 2001
From: Tim Otten <totten@civicrm.org>
Date: Wed, 27 Jul 2016 12:23:40 -0700
Subject: [PATCH] Fix links to wiki pages
---
docs/api/actions.md | 2 +-
docs/api/general.md | 4 ++--
docs/api/params.md | 6 +++---
docs/api/usage.md | 10 +++++-----
docs/hookref-old.md | 4 ++--
5 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/docs/api/actions.md b/docs/api/actions.md
index df564570..771298b2 100644
--- a/docs/api/actions.md
+++ b/docs/api/actions.md
@@ -52,7 +52,7 @@ getlist
-------
Used for autocomplete lookups by the
-[entityRef](/confluence/display/CRMDOC/EntityRef+Fields) widget
+[entityRef](https://wiki.civicrm.org/confluence/display/CRMDOC/EntityRef+Fields) widget
getoptions
----------
diff --git a/docs/api/general.md b/docs/api/general.md
index 9c9e0e06..14676676 100644
--- a/docs/api/general.md
+++ b/docs/api/general.md
@@ -87,14 +87,14 @@ also find the examples on GitHub:
There is also the code-level documentation which can be found at
[http://api.civicrm.org/v3/](http://api.civicrm.org/v3/)
-Also, the [API Reference](/confluence/display/CRMDOC/API+Reference) page
+Also, the [API Reference](https://wiki.civicrm.org/confluence/display/CRMDOC/API+Reference) page
on this wiki.
Changelog
---------
Any API change you should be aware of will be recorded on this wiki
-documentation at [API changes](/confluence/display/CRMDOC/API+changes)
+documentation at [API changes](https://wiki.civicrm.org/confluence/display/CRMDOC/API+changes)
Examples
========
diff --git a/docs/api/params.md b/docs/api/params.md
index f6aff5a5..b59e04e3 100644
--- a/docs/api/params.md
+++ b/docs/api/params.md
@@ -5,7 +5,7 @@ API examples. However, some parameters are particularly dynamic or
generic; these may not be explained well by the auto-generated
documentation. The format for passing options as parameters using the
REST interface is explained at [REST
-interface\#optionsparameters](/confluence/display/CRMDOC/REST+interface#RESTinterface-optionsparameters).
+interface\#optionsparameters](https://wiki.civicrm.org/confluence/display/CRMDOC/REST+interface#RESTinterface-optionsparameters).
**sequential**
@@ -268,6 +268,6 @@ $param['return'] => 'custom_N,custom_O,custom_P';
For setting custom date fields, (ie CustomValue create), date format is YmdHis, for example:Â 20050425000000.
-This is just a brief introduction; each API may have different requirements and allow different formats for accessing the custom data. Â See the [API function documentation](/confluence/display/CRMDOC/Using+the+API) and also read the comments and documentation in each API php file (under civicrm/CRM/api/v3 in your CiviCRM installation) for exact details, which vary for each API entity and function.
+This is just a brief introduction; each API may have different requirements and allow different formats for accessing the custom data. Â See the [API function documentation](https://wiki.civicrm.org/confluence/display/CRMDOC/Using+the+API) and also read the comments and documentation in each API php file (under civicrm/CRM/api/v3 in your CiviCRM installation) for exact details, which vary for each API entity and function.
-For more details and examples, [see the tutorial on using custom data with the API here](/confluence/display/CRMDOC/Using+Custom+Data+with+the+API).
+For more details and examples, [see the tutorial on using custom data with the API here](https://wiki.civicrm.org/confluence/display/CRMDOC/Using+Custom+Data+with+the+API).
diff --git a/docs/api/usage.md b/docs/api/usage.md
index 53c8a85f..974607ad 100644
--- a/docs/api/usage.md
+++ b/docs/api/usage.md
@@ -81,7 +81,7 @@ for usability:
*Note*: If you're writing a Drupal module, a Joomla extension, a WordPress
plugin, or a standalone script, then you may need to **bootstrap** CiviCRM
before using the API. See the examples in [Bootstrap
-Reference](/confluence/display/CRMDOC/Bootstrap+Reference).Â
+Reference](https://wiki.civicrm.org/confluence/display/CRMDOC/Bootstrap+Reference).Â
PHP (class.api.php)
@@ -144,7 +144,7 @@ and options available using the [api
explorer](http://sandbox.civicrm.org/civicrm/ajax/doc#explorer) (also on
your site!)
-Please note that the REST interface is subject to [API Security](/confluence/display/CRMDOC/API+Security).
+Please note that the REST interface is subject to [API Security](https://wiki.civicrm.org/confluence/display/CRMDOC/API+Security).
For more details, see [REST
interface](http://wiki.civicrm.org/confluence/display/CRMDOC/REST+interface).Â
@@ -158,11 +158,11 @@ CRM.api3('entity', 'action', [params], [statusMessage]);
````
For more details, see [AJAX
-Interface](/confluence/display/CRMDOC/AJAX+Interface).
+Interface](https://wiki.civicrm.org/confluence/display/CRMDOC/AJAX+Interface).
The AJAX interface is automatically available for web-pages generated through CiviCRM (such as ***standard CiviCRM web-page****s***, CiviCRM ***extensions***, and custom CiviCRM ***templates***).
-The AJAX interface could be made available to other parts of the same website (e.g. a drupal module or wordpress widget) by calling CRM\_Core\_Resources::singleton()-\>addCoreResources() from php. Please note that the AJAX interface is subject to [API Security](/confluence/display/CRMDOC/API+Security) and [Same Origin Policy](http://en.wikipedia.org/wiki/Same_origin_policy). To use it from an external site or application, see REST interface documentation.
+The AJAX interface could be made available to other parts of the same website (e.g. a drupal module or wordpress widget) by calling CRM\_Core\_Resources::singleton()-\>addCoreResources() from php. Please note that the AJAX interface is subject to [API Security](https://wiki.civicrm.org/confluence/display/CRMDOC/API+Security) and [Same Origin Policy](http://en.wikipedia.org/wiki/Same_origin_policy). To use it from an external site or application, see REST interface documentation.
Smarty
------
@@ -179,7 +179,7 @@ The smarty call is to add extra information, therefore *create* or
*delete* actions don't make sense in this case.
For more details, see [Smarty API
-interface](/confluence/display/CRMDOC/Smarty+API+interface).
+interface](https://wiki.civicrm.org/confluence/display/CRMDOC/Smarty+API+interface).
CLI (drush)
-----
diff --git a/docs/hookref-old.md b/docs/hookref-old.md
index ffd819f4..c06ae2e8 100644
--- a/docs/hookref-old.md
+++ b/docs/hookref-old.md
@@ -54,7 +54,7 @@ For A CiviCRM (native) Extension
--------------------------------
- See this page for [creating an extension and implementing hooks
- within it](/confluence/display/CRMDOC/Create+a+Module+Extension).
+ within it](https://wiki.civicrm.org/confluence/display/CRMDOC/Create+a+Module+Extension).
For A Drupal Module
-------------------
@@ -70,7 +70,7 @@ For a Joomla Plugin
observer design pattern.
- Hook plugins should be placed in the civicrm plugin group in a subfolder with the same name as the plugin.
- Once created plugins may be packaged and installed with the Joomla installer or the files can be placed in the appropriate folder and installed with the discover method.
-- See this [sample Joomla plugin for CiviCRM hooks](/confluence/display/CRMDOC/Example+Joomla+Plugin+for+implementing+hooks)
+- See this [sample Joomla plugin for CiviCRM hooks](https://wiki.civicrm.org/confluence/display/CRMDOC/Example+Joomla+Plugin+for+implementing+hooks)
For a WordPress Plugin
----------------------
--
GitLab