WordPress.org
Get WordPress

Plugin Directory

Changeset 2603170


Ignore:
Timestamp:
09/22/2021 04:08:12 PM (4 years ago)
Author:
wpwiredin
Message:

Version 1.1

Location:
multi-roles-vendor
Files:
69 added
2 edited

Legend:

Unmodified
Added
Removed

  • multi-roles-vendor/trunk/readme.txt

    r2602180 r2603170  
    1 === Multi Roles Vendor ===
    2 Author: wpwiredin
     1=== Multi Roles Vendor === 
     2Contributors: (this should be a list of wordpress.org userid's)
    33Donate link: https://wpwiredin.github.io/plugins/
    4 Tags: WooCommerce, MultiVendor, Marketplace, Users, User Roles, Registration, Login
    5 Version: 1.0.0
    6 Stable Tag: 1.0.0
    7 Tested up to: 5.8
    8 Requires PHP: 6.0
     4Tags: comments, spam
     5Requires at least: 3.0.1
     6Tested up to: 3.4
     7Stable tag: 4.3
    98License: GPLv2 or later
    10 License URI: https://www.gnu.org/licenses/gpl-2.0.html
     9License URI: http://www.gnu.org/licenses/gpl-2.0.html
     10
     11User Role assigment Plugin for WooCommerce Multivendor Sites
    1112
    1213== Description ==
    1314
    14 User Role assigment Plugin for WooCommerce Multivendor Sites (Only WCMP Supported)
     15This is the long description.  No limit, and you can use Markdown (as well as in the following sections).
    1516
    16 # Requirements
     17For backwards compatibility, if this section is missing, the full length of the short description will be used, and
     18Markdown parsed.
    1719
    18 - You have to have WooCommerce installed and activated
    19 - You have to have WCPM installed and activated
    20 - You have to have a User Login/Registration plugin installed, or custom Login/Registration page setup
     20A few notes about the sections above:
    2121
    22 # How the Plugin Works
     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
     26higher 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
     28stable.
    2329
    24 Just activate the plugin and whenever a User registers on your multi-vendor site, they will be assigned a vendor role
     30    Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so
     31if 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
     32for displaying information about the plugin.  In this situation, the only thing considered from the trunk `readme.txt`
     33is the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in
     34your in-development version, without having that information incorrectly disclosed about the current stable version
     35that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag.
    2536
    26 # Alterations/Editing
     37    If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where
     38you put the stable version, in order to eliminate any doubt.
    2739
    28 You may change the user role in the plugin to any WCMP roles, like pending vendor etc.
     40== Installation ==
    2941
    30 # Versions and Pre-Realease
     42This section describes how to install the plugin and get it working.
    3143
    32 - This is minimal pre-release of the plugin which only includes support for WCMP, we will release a more production friendly version in due time.
     44e.g.
    3345
    34 Enjoy!!!
     461. Upload `multi-roles-vendor.php` to the `/wp-content/plugins/` directory
     471. Activate the plugin through the 'Plugins' menu in WordPress
     481. Place `<?php do_action('plugin_name_hook'); ?>` in your templates
     49
     50== Frequently Asked Questions ==
     51
     52= A question that someone might have =
     53
     54An answer to that question.
     55
     56= What about foo bar? =
     57
     58Answer to foo bar dilemma.
     59
     60== Screenshots ==
     61
     621. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
     63the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets
     64directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png`
     65(or jpg, jpeg, gif).
     662. This is the second screen shot
     67
     68== Changelog ==
     69
     70= 1.0 =
     71* A change since the previous version.
     72* Another change.
     73
     74= 0.5 =
     75* List versions from most recent at top to oldest at bottom.
     76
     77== Upgrade Notice ==
     78
     79= 1.0 =
     80Upgrade notices describe the reason a user should upgrade.  No more than 300 characters.
     81
     82= 0.5 =
     83This version fixes a security related bug.  Upgrade immediately.
     84
     85== Arbitrary section ==
     86
     87You may provide arbitrary sections, in the same format as the ones above.  This may be of use for extremely complicated
     88plugins 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.
     90
     91== A brief Markdown Example ==
     92
     93Ordered list:
     94
     951. Some feature
     961. Another feature
     971. Something else about the plugin
     98
     99Unordered list:
     100
     101* something
     102* something else
     103* third thing
     104
     105Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].
     106Titles are optional, naturally.
     107
     108[markdown syntax]: http://daringfireball.net/projects/markdown/syntax
     109            "Markdown is what the parser uses to process much of the readme file"
     110
     111Markdown uses email style notation for blockquotes and I've been told:
     112> Asterisks for *emphasis*. Double it up  for **strong**.
     113
     114`<?php code(); // goes in backticks ?>`

  • multi-roles-vendor/trunk/uninstall.php

    r2597625 r2603170  
    1 // if uninstall.php is not called by WordPress, die
    2 if (!defined('WP_UNINSTALL_PLUGIN')) {
    3     die;
     1<?php
     2
     3/**
     4 * Fired when the plugin is uninstalled.
     5 *
     6 * When populating this file, consider the following flow
     7 * of control:
     8 *
     9 * - This method should be static
     10 * - Check if the $_REQUEST content actually is the plugin name
     11 * - Run an admin referrer check to make sure it goes through authentication
     12 * - Verify the output of $_GET makes sense
     13 * - Repeat with other user roles. Best directly by using the links/query string parameters.
     14 * - Repeat things for multisite. Once for a single site in the network, once sitewide.
     15 *
     16 * This file may be updated more in future version of the Boilerplate; however, this is the
     17 * general skeleton and outline for how the file should work.
     18 *
     19 * For more information, see the following discussion:
     20 * https://github.com/tommcfarlin/WordPress-Plugin-Boilerplate/pull/123#issuecomment-28541913
     21 *
     22 * @link       https://wpwiredin.github.io/plugins/
     23 * @since      1.0.0
     24 *
     25 * @package    Multi_Roles_Vendor
     26 */
     27
     28// If uninstall not called from WordPress, then exit.
     29if ( ! defined( 'WP_UNINSTALL_PLUGIN' ) ) {
     30    exit;
    431}
Note: See TracChangeset for help on using the changeset viewer.