內容簡介
AdTrails UTM Grabber for CF7 可將 UTM 數據插入表單提交中，以進行投資回報率分析，若您正在尋找 Gravity Forms、WP Forms 和 Ninja Forms 相容性呢？我們在 AdTrails.com 提供外掛的高級版本。
出於向後相容性，若此區段遺失，則會使用完整的簡介並轉換成 Markdown 語法。
以下是有關以上部分的一些注意事項：
Actuate Media
UTM Grabber、UTM Tracker
“Requires at least” 指定外掛可運行的最低版本。
“Tested up to” 指定您已成功測試過的最高版本，但仍有可能適用於更高版本，此處僅為您驗證的最高版本。
Stable tag 應指定最新穩定版本的 Subversion “tag” 或者如果您把 /trunk/ 用作穩定版本，則指定為 “trunk”。
請注意，穩定版本的 readme.txt 應視為外掛的定義，因此，如果 /trunk/readme.txt 檔案指定穩定標記為 4.3，那麼將使用 /tags/4.3/readme.txt 顯示有關外掛的信息。在這種情況下，從 trunk readme.txt 中考慮的唯一事項是穩定標記指針。因此，如果您在 trunk 中進行開發，可以更新 trunk readme.txt 以反映正在開發版本中的更改，而不必披露關於當前穩定版本不存在這些更改的信息 — 只要 trunk 的 readme.txt 指向正確的穩定標記即可。
如果未提供穩定標籤，則假定 trunk 穩定，但如果您將穩定版本放在 trunk 中，則應指定為「trunk」，以排除所有疑慮。
自訂區段
您可以提供自訂區段，格式與上面的區段相同。這對於極其複雜的外掛可能有用，因為需要傳達更多信息，這些信息不適合於“描述”或“安裝”的類別。自訂區段將顯示在上述內置區段下面。
Markdown 範例
有序列表:
Some feature
Another feature
Something else about the plugin
無序列表:
something
something else
third thing
以下是指向 WordPress 和 Markdown 語法文件 的鏈結。
標題是可選的。
Markdown 使用電子郵件風格的記號引用塊，並告訴過我：
星號用於強調。強調時請加倍。
<?php code(); // goes in backticks ?>
外掛標籤
開發者團隊
📦 歷史版本下載
原文外掛簡介
AdTrails UTM Grabber for CF7 will push UTM data into your form submissions for ROI purposes. Are you looking for Gravity Forms, WP Forms, and Ninja Forms compatability? We offer a premium version of the plugin at AdTrails.com.
For backwards compatibility, if this section is missing, the full length of the short description will be used, and
Markdown parsed.
A few notes about the sections above:
Actuate Media
UTM Grabber, UTM Tracker
“Requires at least” is the lowest version that the plugin will work on
“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on
higher versions… this is just the highest one you’ve verified.
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for
stable.
Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so
if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt that’ll be used
for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in
your in-development version, without having that information incorrectly disclosed about the current stable version
that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where
you put the stable version, in order to eliminate any doubt.
Arbitrary section
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
A brief Markdown Example
Ordered list:
Some feature
Another feature
Something else about the plugin
Unordered list:
something
something else
third thing
Here’s a link to WordPress and one to Markdown’s Syntax Documentation.
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
Asterisks for emphasis. Double it up for strong.
