local:shop

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
local:shop [2021/04/06 18:08]
florence
local:shop [2024/08/08 09:44] (current)
florence
Line 4: Line 4:
    * **Component type:** local    * **Component type:** local
    * **Name:** Shop    * **Name:** Shop
-   * **Versions:​** :M27: to :M39:+   * **Versions:​** :M27: to :M41:
    * **Distribution:​** Public and PRO versions (dual release)    * **Distribution:​** Public and PRO versions (dual release)
    * **Availability:​** Stable - Distribution** ActiveProLearn**    * **Availability:​** Stable - Distribution** ActiveProLearn**
Line 11: Line 11:
 <​html><​!-- nomoodle --></​html>​ <​html><​!-- nomoodle --></​html>​
    * **Repository:​** Community version http://​github.com/​vfremaux/​moodle-local_shop    * **Repository:​** Community version http://​github.com/​vfremaux/​moodle-local_shop
-   * **Unit tests:** http://​travis-ci/​vfremaux/​moodle-local_shop/​branches 
 <​html><​!-- /nomoodle --></​html>​ <​html><​!-- /nomoodle --></​html>​
 +
 +====Solution presentation====
 +
  
 The shop core plugin provides a complete, flexible, and extensible base shop engine to transform Moodle “items” into saleable products. Items can be many things, since they are mainly linked to an action script triggered on product payment. Scripts can be custom or predefined. Shop implementation is equipped with a set of predefined action scripts, addressing the most common cases. “Product action scripting” is an extensible implementation that uses new scenarios as sub-plugins. The shop core plugin provides a complete, flexible, and extensible base shop engine to transform Moodle “items” into saleable products. Items can be many things, since they are mainly linked to an action script triggered on product payment. Scripts can be custom or predefined. Shop implementation is equipped with a set of predefined action scripts, addressing the most common cases. “Product action scripting” is an extensible implementation that uses new scenarios as sub-plugins.
-The shop core engine is provided in both “community” and “pro” versions:+The shop core engine is provided in both “community” and “PRO” versions:
  
  
-The shop core engine is provided in both "​community"​ and "pro" versions: ​+The shop core engine is provided in both "​community"​ and "PRO" versions: ​
  
    - The community release: features the full core engine, plus a limited set of action scripts and payment methods.    - The community release: features the full core engine, plus a limited set of action scripts and payment methods.
Line 100: Line 102:
   * [[:​auth:​ticket|Ticket based authentication (authticket)]]   * [[:​auth:​ticket|Ticket based authentication (authticket)]]
   * [[blocks:​userquizlimit|User Quiz Limit Block]] ​   * [[blocks:​userquizlimit|User Quiz Limit Block]] ​
 +  * block_mycredits
  
 <​html><​!-- nomoodle --></​html>​ <​html><​!-- nomoodle --></​html>​
-==== Builds ==== 
- 
-^ 2.7 ^ 2.8 ^ 2.9 ^ 3.0 ^ 3.1 ^ 3.2 ^ 3.3 ^ 3.4 ^ 
-| <​html><​img src="​https://​travis-ci.org/​vfremaux/​moodle-local_shop.svg?​branch=MOODLE_27_STABLE"></​html>​ | <​html><​img src="​https://​travis-ci.org/​vfremaux/​moodle-local_shop.svg?​branch=MOODLE_28_STABLE"></​html>​ | <​html><​img src="​https://​travis-ci.org/​vfremaux/​moodle-local_shop.svg?​branch=MOODLE_29_STABLE"></​html>​ | <​html><​img src="​https://​travis-ci.org/​vfremaux/​moodle-local_shop.svg?​branch=MOODLE_30_STABLE"></​html>​ | <​html><​img src="​https://​travis-ci.org/​vfremaux/​moodle-local_shop.svg?​branch=MOODLE_31_STABLE"></​html>​ | <​html><​img src="​https://​travis-ci.org/​vfremaux/​moodle-local_shop.svg?​branch=MOODLE_32_STABLE"></​html>​ | <​html><​img src="​https://​travis-ci.org/​vfremaux/​moodle-local_shop.svg?​branch=MOODLE_33_STABLE"></​html>​ | <​html><​img src="​https://​travis-ci.org/​vfremaux/​moodle-local_shop.svg?​branch=MOODLE_34_STABLE"></​html>​ | 
- 
-[[https://​travis-ci.org/​vfremaux/​moodle-block_shop_access/​branches|Travis-ci Continuous integration]] 
- 
-Note : "​Failing"​ state will NOT stand necessarilty for the plugin is NOT functionning. this status essentially gives the state of the Moodle Coding standard testing suite, and will denote how close to moodle code requirements the plugin is. 
- 
  
 ------------ ------------
local/shop.1617725320.txt.gz · Last modified: 2024/04/04 15:50 (external edit)