[WordPress] 外掛分享: Church Theme Content Integration

首頁外掛目錄 › Church Theme Content Integration
⚠ 此外掛已下架 — 不再更新維護,建議勿安裝。
10+
安裝啟用
尚無評分
4250 天前
最後更新
問題解決
WordPress 3.9+ v0.4.2 上架:2014-07-25

內容簡介

本外掛專為 WordPress Church Theme Content WP 外掛使用者設計。
它加入了將 Fellowship One 人員資料同步至 CTC 人員記錄的功能。
需求

WordPress Church Theme Content WP 外掛。請注意,CTC 整合將安裝但沒有 CTC 的話,你將無法執行任何動作。已在 CTC 1.0.8+ 進行測試。
PHP cURL 函式庫用以與 Fellowship One 通訊。啟用本外掛後,它會檢查 cURL 是否存在,如果不存在,會通知您,並防止您運行受影響的同步作業。

使用 WordPress 控制台

進入「外掛 > 新增外掛」。
搜尋「Church Theme Content Integration」。
從外掛頁面啟用「Church Theme Content Integration」。

使用 WordPress.org

下載「Church Theme Content Integration」。
使用您喜愛的方法 (ftp、sftp、scp...等) 上傳「church-theme-content-integration」資料夾至「/wp-content/plugins/」資料夾。
從 WordPress 的外掛頁面啟用「Church Theme Content Integration」。

設置 (重要!)
Fellowship One

為了從 Fellowship One 帳戶同步資料:

取得您的 API 金鑰:

選擇 People、Groups、和 Events 涵蓋範圍。目前只需要 People 和 Group 範圍,但未來可能會增加對 Events 的支援。

在 WP 中,導覽至「CTC Integration > Fellowship One」。輸入 API URL (僅限基本 URL,不包括「/v1/」)、Consumer Key 和 Consumer Secret。

如果您使用 2nd 方憑證進行身分驗證,請輸入您的使用者名稱和密碼。但請注意,這將以明文形式存儲在 WordPress 資料庫中,請謹慎使用!

2nd 方和 3rd 方身分驗證之間的差異

本外掛允許您使用任一身分驗證方法。
為了簡化流程,如果不確定,請使用 3rd 方身分驗證,因為它更安全。如果您了解風險,可以使用 2nd 方身分驗證。

以下是幾個幫助您決定的理由。

如果您想要最佳安全性,請使用 3rd 方身分驗證。

您樂意(或寧願)只允許那些擁有 Fellowship One 帳號的人運行同步作業。

如果您想要允許您教會的網站管理員進行資料同步,即使他們沒有 Fellowship One 帳戶,可以使用 2nd 方身分驗證。

您同意將您的一個 Fellowship One 帳戶的使用者名稱和密碼以明文形式存儲在 WP 資料庫中。

設定人員同步

在 Fellowship One 中,創建您想要同步的人員列表。

在 WordPress 管理員中,進入「CTC Integration > Fellowship One」,將那些人員列表名稱新增至「People Lists to Sync」選項。

刪除安裝

如果您決定刪除本外掛,則卸載過程將刪除此外掛用於跟蹤 CT 關聯之所有自定義表格和自定義文章元標籤。

外掛標籤

開發者團隊

⬇ 下載最新版 (v0.4.2) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Church Theme Content Integration」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

This plugin is designed for users of the Church Theme Content WP plugin.
It adds the ability to synchronise people data from Fellowship One into CTC people records.
Requirements

The Church Theme Content WP plugin. Note that CTC Integration
will still install without CTC, but you wont be able to run anything. Tested against CTC 1.0.8+
The PHP cURL library to communicate with Fellowship One. This plugin, once activated, will check that cURL exists and
inform you if it doesn’t, as well as preventing you from running the affected synchronisations.

From your WordPress dashboard

Visit ‘Plugins > Add New’
Search for ‘Church Theme Content Integration’
Activate Church Theme Content Integration from your Plugins page.

From WordPress.org

Download Church Theme Content Integration.
Upload the ‘church-theme-content-integration’ directory to your ‘/wp-content/plugins/’ directory, using your favorite method (ftp, sftp, scp, etc…)
Activate Church Theme Content Integration from your Plugins page.

Setup (Important!)
Fellowship One
In order to sync data from your Fellowship One account:

Get your API key:

Select the People, Groups, and Events realms. Currently only the People and Group realms are required, but support for Events may be added later.

In WP, navigate to CTC Integration -> Fellowship One. Enter your API URL (base URL only, minus the ‘/v1/’),
Consumer Key and Consumer Secret.

If you are using 2nd party credential based authentication, enter your username and password. However, note that this
will be stored as plain text in the wordpress database, so use with care!

Difference between 2nd Party and 3rd Party authentication
This plugin allows you to use either authentication method.
To keep it simple, if in doubt, use 3rd party authentication as it is more secure. Use 2nd-party only if you know the risks.
Here are some reasons to help you decide.
Use 3rd party authentication if:

You want the best security.
You are happy (or indeed, would prefer) to only allow those with Fellowship One accounts to be able to run the
synchronisation.

Use 2nd Party authentication if:

You are ok with having the username and password of one of your Fellowship One accounts stored as plain text
in the WP database.
You would like to allow individuals at your church with web admin access the ability to synchronise data even if
they don’t have a Fellowship One account.

People Sync Setup

In Fellowship One, create people list(s) of the people that you want to sync.

In WordPress Admin, under CTC Integration -> Fellowship One, add the names of those people list(s) to the ‘People Lists to Sync’ option.

Uninstallation
If you decide to uninstall the plugin, the uninstall process will delete all custom tables, and custom post meta tags,
that this plugin uses to track associations between CTC records and the service provider records that they were
synced from. This does not make any changes to the data that was synced, that is, the CTC fields themselves.
Fellowship One Options

People Lists to Sync: Type in the names of the people list(s) that you created in Fellowship One, one on each line.

Sync Lists to Groups?: Check this if you would like the people list(s) to correspond to groups of the same name in CTC.
Uncheck this if you don’t want the people records added to groups in CTC, or if you would like to manage groups in CTC manually.

Name Format: Select the name format to be used for the name field in CTC.

Sync Position? / Position Attribute Group: For the position field in CTC, you can optionally sync that as well. To do so,
in Fellowship One create an Attribute Group (with any name), and define Attributes in that group with the names of
your positions. Add these position attributes to the appropriate people records. Then in CTC Integration, check the
Sync Position? checkbox, and enter the name of the Fellowship One Attribute Group into the Position Attribute Group field.

Sync …?: These checkboxes control whether or not each of those fields will be synced. In the case of Phone and Email,
the entry designated as the preferred contact will be used.

延伸相關外掛

文章
Filter
Apply Filters
Mastodon