shop_run
Run a custom module on the store and read its printed output for one-off reports, data checks, or fixes.
Instructions
Run a module of YOUR OWN on this store and read what it printed. This is for code you wrote yourself and want to try: a report over several tables, a check across the catalogue, a one-off fix with its own logic. For work the owner of the shop already provided for, use tool_run instead - that one has a registry row and a grant behind it, this one has nothing but the session key. The storefront runs the module exactly as it runs any module - same parser, same cache, same access to the data. Three conditions. The name starts with agent_ (the entry point runs nothing else); the module exists - create it with engine_php_add and write it with engine_php_save; and it is saved as an entry point, which is manifest ajax_load=1. The output is saved under mcp/melbis/runs/ and comes back here whole unless it is long.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mod | Yes | Module name without .php, for example agent_price_audit. | |
| params | No | Values for the module, by name. The entry point hands them over as one serialized argument, so the module declares post: serial in its manifest param_info and reads them as $mVars[post] - names survive, and so do commas and any alphabet inside a value. The same values are in $_POST; login, secret and mod are stripped before the module sees them. |