[WordPress] 外掛分享: Wallet Pass Generator for Gravity Forms

首頁外掛目錄 › Wallet Pass Generator for Gravity Forms
全新外掛
安裝啟用
尚無評分
98 天前
最後更新
問題解決
WordPress 5.0+ PHP 7.4+ v1.7.9 上架:2026-01-03

內容簡介

總結:這外掛提供一個安全、靈活的解決方案,讓管理員可以從Gravity Forms的輸入中生成Apple Wallet通行證。這個外掛允許將表單字段直接映射到Apple Wallet通行證的不同位置,包括主要、次要、輔助、標題和背部字段。

### 問題與答案:
1. 這個外掛提供了什麼功能?
- 提供一個安全、靈活的解決方案,讓管理員可以從Gravity Forms的輸入中生成Apple Wallet通行證。
2. 在設置中,如何將表單字段映射到Apple Wallet通行證位置?
- 在Global Settings中,輸入Apple Team ID、Pass Type ID和.p12證書文件的絕對服務器路徑。
- 在Form Setup中,開啟特定的Gravity Form,並前往Settings > Wallet Pass。
- 在Primary Field中,映射一個標籤和字段來源。
3. 如果想要在生成的通行證中添加標題、次要、輔助或背部字段,應該如何處理?
- 在Optional Fields中,提供標籤給每個領域。如果標籤留白,該字段將被省略。
4. 提供了哪些視覺設置選項?
- 指定標誌和圖示的絕對路徑。最佳效果是使用320x100的PNG格式作為標誌,與58x58的PNG格式作為圖示。
5. 如何啟用通行證上的條碼?
- 在QR Code中輸入URL或文本,以啟用通行證上的條碼。

開發者團隊

⬇ 下載最新版 (v1.7.9) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Wallet Pass Generator for Gravity Forms」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

A secure, dynamic solution for generating Apple Wallet passes from Gravity Forms entries. This plugin allows administrators to map form fields directly to Apple Wallet pass locations including Primary, Secondary, Auxiliary, Header, and Back fields.
Configuration

Global Settings: Navigate to the Wallet Pass global settings page. Enter your Apple Team ID, Pass Type ID, and the absolute server path to your .p12 certificate file.
Form Setup: Open a specific Gravity Form and navigate to Settings > Wallet Pass.
Primary Field: Map a label and a field source. This field is required to generate a valid pass.
Optional Fields: Provide labels for Header, Secondary, Auxiliary, or Back fields. If a label is left blank, that specific field will be omitted from the generated pass.
Visuals: Specify absolute paths for your logo and icon. For best results, use 320×100 PNG for logos and 58×58 PNG for icons.
QR Code: Enter a URL or text in the QR Code Message field to enable the barcode on the pass.

Troubleshooting
Common Error: OpenSSL “invalid key length”
If you see this error on modern hosting (like SiteGround), it means your .p12 file is using older encryption that OpenSSL 3.x rejects by default.
To fix this, perform the “2-Step Legacy to Modern AES” conversion on your Mac Terminal:

Unpack the original file (requires your Keychain password):
openssl pkcs12 -in YourCert.p12 -nodes -out temp.pem

Repack it using Modern AES-256 encryption:
openssl pkcs12 -export -in temp.pem -out YourCert_Fixed.p12 -certpbe AES-256-CBC -keypbe AES-256-CBC -macalg SHA256

Upload YourCert_Fixed.p12 to your server and update the password in settings.

Error: “Could not find private key”
This occurs if you only exported the Certificate from Keychain Access.
Fix: In Keychain Access, click the arrow (▶) next to the certificate to reveal the Private Key. Highlight BOTH items before selecting “Export”.

延伸相關外掛

文章
Filter
Apply Filters
Mastodon