From 6ccd8c9c998060a3744e9f62ddfd8b1b134805c8 Mon Sep 17 00:00:00 2001 From: Hofmann Dominique Marc Date: Sun, 2 Jun 2019 20:01:35 +0000 Subject: Update readme.txt --- src/GNU-taler-payment/readme.txt | 117 ++++++++++----------------------------- 1 file changed, 28 insertions(+), 89 deletions(-) diff --git a/src/GNU-taler-payment/readme.txt b/src/GNU-taler-payment/readme.txt index 23e6935..7c16af6 100644 --- a/src/GNU-taler-payment/readme.txt +++ b/src/GNU-taler-payment/readme.txt @@ -1,66 +1,42 @@ -TODO: Write this stuff and use https://wordpress.org/plugins/developers/readme-validator/ - -=== Plugin Name === -Contributors: (this should be a list of wordpress.org userid's) -Donate link: https://example.com/ -Tags: comments, spam -Requires at least: 4.6 -Tested up to: 4.7 -Stable tag: 4.3 -Requires PHP: 5.2.4 -License: GPLv2 or later -License URI: https://www.gnu.org/licenses/gpl-2.0.html - -Here is a short description of the plugin. This should be no more than 150 characters. No markup here. +=== GNU Taler Payment Gateway for Woocommerce === +Contributors: hofmd2, sakaeo +Donate link: https://donations.demo.taler.net/ +Tags: woocommerce, e-commerce, GNU Taler, Taler, Payment Gateway +Requires at least: 5.1 +Tested up to: 5.2.1 +Stable tag: 5.2 +Requires PHP: 7.2 +License: GNU General Public License v3.0 +License URI: http://www.gnu.org/licenses/gpl-3.0.html + +Online payment plugin for Woocommerce powered by GNU Taler == Description == -This is the long description. No limit, and you can use Markdown (as well as in the following sections). - -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: - -* "Contributors" is a comma separated list of wordpress.org usernames -* "Tags" is a comma separated list of tags that apply to the plugin -* "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. +This plugin provides a safe and secure way to pay via the GNU Taler system. The plugin sends a request to and receives a respones from the GNU Taler Backend. +After that the plugin confirms the transaction again and redirect the customer to his own wallet to confirm the transaction. +The plugin provides the possibilitiy for the admininstrator to send the costumer a refund. +For that the plugin sends a refund request to the GNU Taler backend and receives a refund-url, which will be forwarded to the customer via an email to confirm the refund. - 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. +The GNU Taler payment system has some certificate and includes latest fraud and risk management. == Installation == -This section describes how to install the plugin and get it working. - -e.g. - -1. Upload the plugin files to the `/wp-content/plugins/plugin-name` directory, or install the plugin through the WordPress plugins screen directly. -1. Activate the plugin through the 'Plugins' screen in WordPress -1. Use the Settings->Plugin Name screen to configure the plugin -1. (Make your instructions match the desired user flow for activating and installing your plugin. Include any steps that might be needed for explanatory purposes) - +1. Ensure you have latest version of WooCommerce plugin installed +2. Upload the plugin files to the `/wp-content/plugins/plugin-name` directory, or install the plugin through the WordPress plugins screen directly. +3. Activate the GNU Taler Payment for Woocommerce plugin through the 'Plugins' screen in WordPress. +4. Use WooCommerce settings-> payment tab -> GNU Taler Payment for Woocommerce Settings to configure the plugin. == Frequently Asked Questions == -= A question that someone might have = += Do I have to have a GNU Taler account to use the plugin? = -An answer to that question. +Yes, you need to have an account. +You can join the GNU Taler family on: https://bank.demo.taler.net/ -= What about foo bar? = += Can the plugin work without Woocommerce = -Answer to foo bar dilemma. +For the plugin to work perfectly you need to have the Woocommerce plugin installed == Screenshots == @@ -69,51 +45,14 @@ the /assets directory or the directory that contains the stable readme.txt (tags directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png` (or jpg, jpeg, gif). 2. This is the second screen shot +TODO make screenshots == Changelog == = 1.0 = -* A change since the previous version. -* Another change. - -= 0.5 = -* List versions from most recent at top to oldest at bottom. +* First Public Release == Upgrade Notice == = 1.0 = -Upgrade notices describe the reason a user should upgrade. No more than 300 characters. - -= 0.5 = -This version fixes a security related bug. Upgrade immediately. - -== 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: - -1. Some feature -1. Another feature -1. Something else about the plugin - -Unordered list: - -* something -* something else -* third thing - -Here's a link to [WordPress](https://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax]. -Titles are optional, naturally. - -[markdown syntax]: https://daringfireball.net/projects/markdown/syntax - "Markdown is what the parser uses to process much of the readme file" - -Markdown uses email style notation for blockquotes and I've been told: -> Asterisks for *emphasis*. Double it up for **strong**. -`` \ No newline at end of file -- cgit v1.2.3