AMS Studio ERP — Invoicing & Accounting

cd app && npm ci && npm run build

npm ci installs the exact dependency versions recorded in
app/package-lock.json. `npm run build` type-checks the sources with TypeScript

Changelog

0.5.25

• On a site without the stock, WooCommerce or accounting modules, the admin
  interface no longer requests routes that do not exist there: the dashboard
  only asks for stock alerts when stock is installed, the VAT settings only list
  accounting accounts when accounting is, and the Warehouses and Store settings
  tabs only appear when their module does.
• Demo data no longer writes purchase orders and supplier invoices on a site
  that has no purchasing module.

0.5.24

• Plugin Check reports nothing left in the plugin’s own code. The hook fired when
  the installation fingerprint is renewed is now fired by its literal, prefixed
  name. The one call it discourages, load_plugin_textdomain(), says why it
  stays: the plugin ships its own English catalogue, which WordPress only finds
  through that call.

0.5.23

• The print page of a document is no longer echoed as one string. Its template
  is included directly in the response, and escapes every value at the exact
  place where it is output.
• No inline JavaScript left: the print button, the confirmation before a status
  change, the setup fields to copy and the “copy backup codes” button now use a
  script enqueued with wp_enqueue_script(), or printed with
  wp_print_inline_script_tag() on the standalone print page. The “copy backup
  codes” button, which copied nothing, now copies.
• PDF downloads, accounting exports and stored attachments are sent with
  X-Content-Type-Options: nosniff.
• Bundled php-font-lib: a font-debugging method that built HTML with inline
  scripts, and that nothing calls, is emptied — see “Third-party libraries”.

0.5.22

• The sources of the admin interface shipped in app/src/ can be rebuilt from
  the plugin package alone again. A screen that is not part of this package was
  imported unconditionally, so npm run build stopped on a missing file; it is
  now loaded only where its file exists.
• The same sources are published at https://github.com/SanMat11/wp-erpx, and the
  readme gives the Node.js version, the exact command and where the output goes.

0.5.21

• English is translated again. The English catalogue was deleted during the
  0.5.7 rename and never rebuilt: since then every string written by the server
  — API refusals shown on screen, e-mails, PDFs, meta boxes — came out in French
  on English sites, while the interface itself switched. All 971 strings the
  code asks for are now translated and shipped as
  languages/ams-studio-erp-invoicing-accounting-en_US.mo.
• A quote could not be accepted in English. The wording a customer copies
  out to accept a quote was compared against the French bon pour accord, while
  the refusal message told English customers to type “Agreed and accepted”. They
  typed exactly what was asked and were turned away. The expected wording now
  follows the language of the site, and French stays accepted so agreements
  given before a language change remain valid.
• Four screen strings still quoted the French wording inside English sentences,
  and two were left in French outright. The screen, the refusal message and the
  check now say the same thing.

0.5.20

• The text domain is now ams-studio-erp-invoicing-accounting, matching the
  slug registered on WordPress.org. It was ams-studio-business-management on
  1155 i18n calls, which prevented the plugin from being translated through
  translate.wordpress.org. The PHP prefix amsbm_, the option, table, post
  type and REST namespace names are unchanged, as is the main file name.
• Internal: the translation catalogue built by bin/i18n/ was named
  amsbm-.po, which matched no text domain — WordPress would never
  have loaded it. It now carries the domain, as the format requires.

0.5.19

• Internal: the Peppol reader no longer emits a PHP warning when an incoming
  invoice omits optional elements — payment terms, legal entity, trading name
  or tax scheme. Absent elements read back as an empty string, as intended.
• Internal: the test asserting that every document type is reachable by a role
  performed no assertion at all: it returned on the first role covering
  everything. It now checks the business roles, and was seen to fail when a
  document type is unwired from them.

0.5.18

• Internal: the bundled PDF libraries — dompdf, php-font-lib, masterminds/html5
  and sabberworm/php-css-parser — now live under the AMSBM\Vendor\ namespace,
  prefixed with PHP-Scoper. Two plugins bundling dompdf in different versions
  can no longer break each other. A document renders byte-for-byte as before.

0.5.17

• Internal: the document editor’s article catalogue no longer writes its
  tag by hand. It goes through wp_print_inline_script_tag(), which
  carries the page’s Content-Security-Policy nonce where there is one. It stays
  a JSON data block, not executable code. Nothing changes on screen.

0.5.16

• Security: SVG rendering has been removed from the PDF engine, and the
  php-svg-lib library with it. Drawing an SVG meant parsing user-supplied XML
  inside the printing chain, for a format the plugin never needed: logos are
  PNG, JPEG, GIF or WebP. An SVG is now refused when the logo is uploaded, and
  refused again before it reaches the PDF. Documents without an SVG render
  byte-for-byte as before.

0.5.15

• Internal: every SQL query now goes through wpdb::prepare(), with no exception.
  Table and column names are bound with the %i placeholder instead of being
  interpolated into the query string, and the plugin’s own table names are checked
  against a hard-coded list before any query is built. Nothing changes on screen:
  the 132 read routes return byte-for-byte identical answers.

0.5.14

• Internal: the public quote and invoice page no longer writes its script tags by hand.
  They go through the WordPress loader, which now also carries the page’s
  Content-Security-Policy nonce. Nothing changes on screen.

0.5.13

• Internal: four blocks in the bundled PDF libraries were rewritten from heredoc to
  string concatenation, so that the whole package passes the directory’s automated
  check. The generated PDFs are byte-for-byte identical. Every deviation from the
  upstream libraries is now listed in lib/pdf/ECARTS.md.

0.5.12

• The “Upgrade to Pro” link in the header now offers to subscribe, in so many words:
  the dialog it opens says “Subscribe” instead of “Learn more” and states the price —
  the same one the website quotes. It no longer names an empty module when it was not
  opened from a particular screen.

0.5.11

• Internal: this package now refuses any update whose archive does not come from where
  it says it does. Nothing changes for you here — the free edition is updated by
  WordPress.org as it should be.

0.5.10

• Removing the demo dataset and installing it again left you with no customers and no
  products at all — while reporting it had created twenty. Removing deleted the
  WordPress posts but not the plugin’s own rows, and the next install reused a post id
  that pointed at nothing.
• A company named “Roussel & Fils” read “Roussel & Fils” in the demo dataset.
• An IBAN broke into six stacked pieces in the treasury list, and an IBAN entered with
  spaces was regrouped wrongly. A cash account shows a dash instead of an empty box.

0.5.9

• This installation now has an identity of its own — an identifier drawn at random on
  your site, and a secret drawn with it. Nothing is sent anywhere: they exist so that a
  licence bought later belongs to this site and fills itself in, instead of being copied
  by hand. See “External services” for the one moment anything leaves, and what it is.
• The activate button no longer sits flush against the licence field.

0.5.8

• Screens that spoke French on an English site. The public invoice page a customer
  opens to pay, the goods receipt screen and the online payment settings carried their
  wording inside the code instead of in the catalogues: 87 sentences that no
  translation could reach. They are now in both catalogues, English included.
• The subscription screen showed its translation keys instead of its labels — its
  whole set of 80 keys was in neither catalogue. It also named the four licence states
  it had never been given a word for, starting with a site that simply has no key.

0.5.7

• This package now contains exactly what it runs. Purchasing, stock, deals, treasury,
  accounting, the document library and the WooCommerce bridge moved to a separate
  add-on — their code is no longer shipped here. Nothing is capped or locked: what is
  present works, in full.
• New name. The plugin was called ERP-X; it is now AMS Studio ERP.
  Everything it declares was renamed with it — options, tables, custom post types,
  capabilities, hooks and the REST namespace. Nothing carries over from the old
  names, so this version is an installation, not an upgrade.
• Nothing in this package is capped, time-limited or tied to a key. What is here
  is installed and open; what is not here is not shipped at all.
• Electronic invoicing follows. Factur-X (PDF/A-3) and Peppol BIS Billing 3.0
  used to be conditional; they now apply to every invoice, which is what a legal
  obligation ought to be.
• The plugin no longer looks anywhere but here for its updates.

0.5.6

• A document the WooCommerce bridge found wrong now says so before you click. The
  bridge marks it, approval refuses it — but nothing showed the reason, so the refusal
  arrived out of nowhere.
• The supplier invoice screens stop offering what the server will refuse: five write
  actions in the list, and approving a credit note, are now hidden from roles that do
  not have the right — and the reason is stated, with who to ask.
• A supplier credit note table headed two different columns “Amount excl. VAT”.
• The credit note route names the capability it needs instead of relying on the global
  write right.

0.5.5

• The plugin’s own header is translated at last. Its name and description were in no
  catalogue, so an English site read the description in French on its plugins screen —
  the one place never reread. The extractor now covers the header, as xgettext does.
• One header dropped: the plugin address and the author address may not be the same,
  and the site at ams-studio.lu presents the plugin.

0.5.4

• Every PHP file the plugin ships now refuses a direct HTTP call. On shared hosting
  wp-content is often served without going through WordPress, and a file reached that
  way ran outside it — printing the server’s absolute path in the fatal error that
  followed. A test counts them all and fails on the next file shipped without a guard.
• The two-factor QR script goes through the WordPress script queue.
• Repository compliance: exemptions declared for the directory’s own database sniff,
  which is stricter than the WordPress coding standard, and one core function dropped
  in favour of a plain expression.

0.5.3

• The plugin is named ERP-X throughout, with a new mark drawn in one place and used on
  the admin menu, the sidebar and the sign-in screen.

0.5.2

• fail2ban on the API, installation blocking, and an allow list on the administration.

0.5.1

• Sealing: an invoice or credit note the WooCommerce bridge found wrong can no longer be
  approved by any path.
• Electronic invoicing: a non-compliant invoice no longer goes out by email or on the
  public page either.
• Purchasing: only what has been received is invoiced; invoicing ahead must be asked for.

0.5.0

• Two-factor authentication and the per-module permission matrix.

0.2.0

• The sales cycle end to end: items, parties, quotes, invoices.
• Multi-rate VAT rounded per rate at the foot of the document.
• Quote to invoice transformation, with a line-by-line trace.

0.1.0

• Exact decimal arithmetic, with no silent overflow.
• Numbering by atomic UPDATE, refusing documents backdated below the last period used.
• Migration lock through a MySQL GET_LOCK, genuinely atomic.