WP Arda-Report

WordPress side of MOSE: the WP Arda-Report plugin, installed in the folder multi-block.

• Report and Customer post types, under the Reports menu.
• Report blocks: Title, Client, Introduction (context, author, revisions, customer address), Social, version, arda_MQ.
• The graphs of the MOSE Markdown reports: view.js draws the ``blocks namedVolbarstacked,NasVolume,CommVaultJob,plotly,plotlybarstacked,Multiline,StorageEvolutionandwarningPie` with Chart.js, from the table inside them.

Install

1. Download multi-block.zip from the latest release.
2. In WordPress: Plugins → Add New → Upload Plugin, choose the zip, install and activate. On a site that already has the plugin, WordPress offers to replace it: accept.

The site needs WordPress 6.1 and PHP 7.0 or later.

Updates

From then on, a new release shows on the site's Plugins page like any other plugin update (Plugin Update Checker, bundled in plugin-update-checker/). WordPress checks every 12 hours; Dashboard → Updates → Check again checks now.

A site with a version from before the updater (1.0.0) must install the zip once by hand, as above.

Make a release

1. Change Version: in multi-block.php (e.g. 1.2.0) and push to main.

2. Tag that commit and push the tag:

   git tag -a v1.2.0 -m "WP Arda-Report 1.2.0"
   git push origin v1.2.0

The Release workflow checks that the tag matches the version, builds multi-block.zip and publishes the release. A tag with a suffix, like v1.2.0-rc.1, is a pre-release: the sites ignore it, so it can be tested by installing its zip by hand.

Report style

report.css styles the reports on screen and for A4 print: numbered headings, tables, code blocks, the cover header, page breaks. It is loaded with the fonts Source Code Pro and Fira Sans on the Report pages and the Reports archive only, so the rest of the site keeps its theme.

The image behind the cover header is set per site in Settings → General → Report header image (a URL, e.g. copied from the Media Library).

A site that had this style in Appearance → Customize → Additional CSS can remove it from there once the plugin is updated: the plugin now brings it.

Development

The blocks are in src/<Block>/ (block.json, edit.js, save.js, render.php, styles) and compile to build/, which is what the sites run. Needs Node.js 22 or later.

npm install
npm run start   # rebuilds build/ on every change
npm run build   # production build before a release

Commit src/ and build/ together: the release zip contains build/, not src/.

• The blocks are drawn by render.php. Do not change what save.js returns: the reports already contain that markup, and the editor would mark those blocks as invalid.
• view.js at the root is loaded on every page; src/arda_MQ/view.js is an identical copy, built into the arda_MQ block. Change both.
• src/ was rebuilt from the development build, since the original was not kept.

Graph blocks

A graph is a ``block whose name is the graph type, with a Markdown table inside: the first row is the title then the labels, the|---|` row is skipped, the other rows are the data.

```Volbarstacked
| Disk % | datastore1 |
|--------|------------|
| Free   |  34        |
```

Known issues

• The print link exposes the login session. For a logged-in user, front_print_footer_scripts() writes a spietopdf: link at the bottom of every page with the value of the wordpress_logged_in_* cookie, for the PDF printer. Anyone who gets the page's HTML (cache, saved page, browser extension, script on the page) can use it to log in as that user. Kept on purpose until the PDF printer has another way to authenticate.