WordPress.org
Get WordPress

Plugin Directory

Changeset 2921840


Ignore:
Timestamp:
06/05/2023 04:08:01 PM (3 years ago)
Author:
multifidelidade
Message:

init v1.0.0

File:
1 edited

Legend:

Unmodified
Added
Removed

  • wc-multipay/trunk/readme.txt

    r2921670 r2921840  
    1 === Woo Multipay ===
    2 Contributors: (this should be a list of wordpress.org userid's)
    3 Tags: comments, spam
    4 Requires at least: 4.5
    5 Tested up to: 6.2
    6 Requires PHP: 5.6
    7 Stable tag: 0.1.0
    8 License: GPLv2 or later
    9 License URI: https://www.gnu.org/licenses/gpl-2.0.html
     1=== QR Code PicPay for WooCommerce ===
     2Contributors: dadeke
     3Donate link: https://app.picpay.com/user/deividsondamasio
     4Tags: woocommerce, picpay, payment
     5Requires at least: 5.0
     6Tested up to: 6.0
     7Stable tag: 1.2.0
     8License: GPLv3 or later
     9License URI: http://www.gnu.org/licenses/gpl-3.0.html
    1010
    11 Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.
     11Add PicPay E-Commerce as payment method in WooCommerce.
    1212
    1313== Description ==
    1414
    15 This is the long description.  No limit, and you can use Markdown (as well as in the following sections).
     15### Add PicPay E-Commerce gateway to WooCommerce ###
    1616
    17 For backwards compatibility, if this section is missing, the full length of the short description will be used, and
    18 Markdown parsed.
     17This plugin adds PicPay E-Commerce gateway to WooCommerce.
    1918
    20 A few notes about the sections above:
     19Please notice that WooCommerce must be installed and active.
    2120
    22 *   "Contributors" is a comma separated list of wp.org/wp-plugins.org usernames
    23 *   "Tags" is a comma separated list of tags that apply to the plugin
    24 *   "Requires at least" is the lowest version that the plugin will work on
    25 *   "Tested up to" is the highest version that you've *successfully used to test the plugin*. Note that it might work on
    26 higher versions... this is just the highest one you've verified.
    27 *   Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use `/trunk/` for
    28 stable.
     21[PicPay E-Commerce](https://ecommerce.picpay.com/) is a brazilian payment method developed by PicPay Serviços S.A.
    2922
    30     Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so
    31 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
    32 for displaying information about the plugin.  In this situation, the only thing considered from the trunk `readme.txt`
    33 is the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in
    34 your in-development version, without having that information incorrectly disclosed about the current stable version
    35 that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag.
     23This plugin was developed with [the official PicPay E-Commerce documentation](https://ecommerce.picpay.com/doc/) and uses the latest version of the payment API.
    3624
    37     If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where
    38 you put the stable version, in order to eliminate any doubt.
     25The PicPay WooCommerce plugin was developed without any incentive from PicPay Serviços S.A.
     26None of the plugin developers have links to the company.
    3927
    40 == Installation ==
     28This software is free and is not associated with PicPay. PicPay is a registered trademark of PicPay Serviços S.A. This plugin is not affiliated with PicPay Serviços S.A and therefore is not an official PicPay product.
    4129
    42 This section describes how to install the plugin and get it working.
     30= How to test =
    4331
    44 e.g.
     32The PicPay API does not have an production environment. All sales testing should be done using the production environment.
     33The values can be refund by the [Painel do Lojista - PicPay](https://lojista.picpay.com/login) or by WooCommerce changing the order Status to "Canceled".
     34After the order Status is changed to "Canceled" in WooCommerce, automatically (after a few seconds) the plugin should change the order Status to "Refunded".
    4535
    46 1. Upload `plugin-name.php` to the `/wp-content/plugins/` directory
    47 1. Activate the plugin through the 'Plugins' menu in WordPress
    48 1. Place `<?php do_action('plugin_name_hook'); ?>` in your templates
     36= Contribute =
     37
     38You can contribute to the source code in our [GitHub](https://github.com/dadeke/woo-picpay) page.
     39
     40= Compatibility =
     41
     42Compatible with latest versions of WooCommerce.
     43
     44The use of the plugin [Brazilian Market on WooCommerce](http://wordpress.org/plugins/woocommerce-extra-checkout-fields-for-brazil/) is mandatory, because in this way it is possible to send the fields of "CPF" or "CNPJ" to process the payment.
    4945
    5046== Frequently Asked Questions ==
    5147
    52 = A question that someone might have =
     48= What is the plugin license? =
    5349
    54 An answer to that question.
     50* This plugin is released under a GPL license.
    5551
    56 = What about foo bar? =
     52= What is needed to use this plugin? =
    5753
    58 Answer to foo bar dilemma.
     54* WooCommerce latest version installed and active.
     55* Own an account at [PicPay E-commerce](https://ecommerce.picpay.com/ "PicPay E-commerce").
     56* Generate the PicPay Token and the Seller Token in the [PicPay Dashboard](https://lojista.picpay.com/login "PicPay Dashboard").
     57* Have the plugin [Brazilian Market on WooCommerce](http://wordpress.org/plugins/woocommerce-extra-checkout-fields-for-brazil/) installed and configured.
     58
     59= PicPay receives payments from which countries? =
     60
     61At the moment PicPay receives payments only from Brazil.
     62
     63The plugin has been configured to receive payments only from users who select Brazil in payment information during checkout.
    5964
    6065== Screenshots ==
    6166
    62 1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
    63 the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets
    64 directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png`
    65 (or jpg, jpeg, gif).
    66 2. This is the second screen shot
     671. Plugin settings.
     682. Payment method on the order completion page.
     693. Example of the PicPay payment page.
    6770
    6871== Changelog ==
    6972
    70 = 1.0 =
    71 * A change since the previous version.
    72 * Another change.
     73= 1.2.0 - 2020/07/13 =
    7374
    74 = 0.5 =
    75 * List versions from most recent at top to oldest at bottom.
     75* Fix for not request cancellation in the PicPay API if another payment method was used.
     76* Add process the request payment with order create via WooCommerce REST API.
     77* Add new functionality: QR Code expiration.
     78* Add hooks so that other developers can extend and modify it.
     79* Add header "Accept: application/json". Good practice.
     80
     81= 1.1.8 - 2020/06/10 =
     82
     83* Fix "Order properties should not be accessed directly."
     84
     85= 1.1.7 - 2020/06/09 =
     86
     87* Fix bug. Added the invoice prefix in the request cancel.
     88
     89= 1.1.6 - 2020/06/08 =
     90
     91* Added config param "Invoice Prefix".
     92* Added response of the payment request in the log.
     93* Allow the callback to cancel orders only with "Pending payment" and "On hold" status.
     94* Fix. Reduce stock only from "Pending payment" to "Processing" status.
     95* Changed PicPay dashboard links.
     96* WC tested up to 4.2.0
     97
     98= 1.1.5 - 2020/01/03 =
     99
     100* Remove unused code.
     101* WC tested up to 3.8.1
     102
     103= 1.1.4 - 2019/09/25 =
     104
     105* Set SVG with both fixed width.
     106
     107= 1.1.3 - 2019/09/24 =
     108
     109* Updated plugin name from "WooCommerce PicPay" for "QR Code PicPay for WooCommerce".
     110
     111= 1.1.2 - 2019/07/30 =
     112
     113* Fixed order cancellation bug.
     114
     115= 1.1.1 - 2019/04/10 =
     116
     117* Changed to save the metadata in the order as the unique key.
     118
     119= 1.1.0 - 2019/04/09 =
     120
     121* Added the prefix "PicPay_" in all metadata that is saved in the order.
     122
     123= 1.0.0 - 2019/03/03 =
     124
     125* Published the first version.
    76126
    77127== Upgrade Notice ==
    78128
    79 = 1.0 =
    80 Upgrade notices describe the reason a user should upgrade.  No more than 300 characters.
     129= 1.2.0 =
    81130
    82 = 0.5 =
    83 This version fixes a security related bug.  Upgrade immediately.
     131* See changelog for more details.
    84132
    85 == Arbitrary section ==
     133= 1.1.8 =
    86134
    87 You may provide arbitrary sections, in the same format as the ones above.  This may be of use for extremely complicated
    88 plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or
    89 "installation."  Arbitrary sections will be shown below the built-in sections outlined above.
     135* See changelog for more details.
    90136
    91 == A brief Markdown Example ==
     137= 1.1.7 =
    92138
    93 Ordered list:
     139* See changelog for more details.
    94140
    95 1. Some feature
    96 1. Another feature
    97 1. Something else about the plugin
     141= 1.1.6 =
    98142
    99 Unordered list:
     143* See changelog for more details.
    100144
    101 * something
    102 * something else
    103 * third thing
     145= 1.1.5 =
    104146
    105 Here's a link to [WordPress](https://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].
    106 Titles are optional, naturally.
     147* See changelog for more details.
    107148
    108 [markdown syntax]: https://daringfireball.net/projects/markdown/syntax
    109             "Markdown is what the parser uses to process much of the readme file"
     149= 1.1.4 =
    110150
    111 Markdown uses email style notation for blockquotes and I've been told:
    112 > Asterisks for *emphasis*. Double it up  for **strong**.
     151* See changelog for more details.
    113152
    114 `<?php code(); // goes in backticks ?>`
     153= 1.1.3 =
     154
     155* See changelog for more details.
     156
     157= 1.1.2 =
     158
     159* See changelog for more details.
     160
     161= 1.1.1 =
     162
     163* See changelog for more details.
     164
     165= 1.1.0 =
     166
     167* See changelog for more details.
     168
     169= 1.0.0 =
     170
     171* See changelog for more details.
     172
     173"For God so loved the world, that he gave his only begotten Son, that whosoever believeth on him should not perish, but have eternal life." John 3:16
Note: See TracChangeset for help on using the changeset viewer.