Aluleth Proposals Pro – Proposals, Quotes, E-Signature and Payment at Signing for WordPress

Changelog:

Aluleth Proposals Pro 0.4.4
= 0.4.4 =
* Complete plugin: Aluleth Proposals 0.5.2 is included (unchanged), nothing else to install.
* Reminders to the next signers ("your turn to sign") now go through the proposals waiting for signatures the same way as the follow-ups: page by page in a fixed order, from where the last hourly run stopped (the place is saved, also through proposals that get no reminder), and back to the start once the end is reached. Proposals with follow-ups turned off or whose signers were already reminded no longer keep later proposals from getting their reminders, however many there are (before, only the first 10,000 were looked at). Each signer still gets at most one reminder per version.
* Each list (reminders, follow-ups, signers) reads for about 8 seconds at most per hourly run.

Aluleth Proposals Pro 0.4.3
= 0.4.3 =
* Complete plugin: Aluleth Proposals 0.5.2 is included (unchanged), nothing else to install.
* Follow-ups ("opened, not signed") and reminders before the end date: proposals are now read page by page in a fixed order, from where the last hourly run stopped, and back to the start once the end is reached. Proposals that get no follow-up (follow-ups turned off in their terms, sent without Pro terms, or sent too recently) no longer fill the list and keep other proposals from getting theirs, however many there are. A run sends at most 40 emails of each kind and reads each list for about 12 seconds at most; the next run goes on from there. Each proposal still gets at most one follow-up and one reminder per version sent.
* Reminders to the next signers read the proposals waiting for signatures by id instead of by page number, so none is skipped when the list changes during a run.

Aluleth Proposals Pro 0.4.2
= 0.4.2 =
* Complete plugin: Aluleth Proposals 0.5.2 is included (unchanged), nothing else to install.
* Approval requests reach everyone who can approve and open the proposal, whatever gives them that right: administrators, the roles given the Settings and Proposals access in Aluleth › Settings › Access, rights given one by one or by another plugin. Each person is checked with WordPress's own capability check before the email goes (filter aluleth_proposals_pro/approvers). The message after "Ask for approval" says whether everyone was emailed, only some of them, nobody (no email could be sent) or that nobody else can approve; when no email went, the button can be used again at once. The activity shows how many people were emailed.
* FluentCart: one payable attempt per payment. The cart made for a payment is used again, and so is the order it became while that order can still be paid (pending or failed payment, also an offline order on hold): the client pays that same order (on FluentCart's own "pay for this order" page once the cart is completed), so opening the payment link again, or many times at once, never makes a second order to pay. An order counts as paid only when its payment status is paid (an order moved to processing by hand before the money came is not); a paid order is taken into account even when its message has not come yet; a payment being processed (authorized, scheduled, partly paid) shows a "being processed" message and nothing new to pay; a cancelled order cancels the request, also when it is cancelled on FluentCart's order screen. A new cart is made only once the earlier order is gone, failed for good or refunded.
* Every order and cart made for a payment stays linked to it (new table aluleth_prop_pay_orders, filled from the existing payments on update), so a late payment, refund or cancellation of an earlier order still finds its payment: a late payment of an earlier order marks the payment paid and closes the newer cart; a refund or cancellation of an earlier order never changes a payment paid by a later one (it is noted on the proposal). A payment that version 0.4.1 had given a second cart goes back to its first order while that order can be paid.

Aluleth Proposals Pro 0.4.1
= 0.4.1 =
* Complete plugin: Aluleth Proposals 0.5.2 is included, nothing else to install. If the free Aluleth Proposals plugin is already on the site, it is used as before and its proposals stay.
* Payments: one order (WooCommerce) or one cart (FluentCart) per payment, also when the link is opened twice at the same moment. A FluentCart order counts as the payment only when it holds the payment product alone.
* Reminders, follow-ups, "your turn" emails to signers and plan links are recorded before they are sent, with a unique key: two tasks running at once never send them twice. Every proposal waiting for signatures is looked at, however old.
* Limits (codes by email, payment tries, AI requests, time read) are counted in one database statement, so requests at the same moment are all counted.
* Approval: the approver approves the version they saw; documents and signers are part of what is approved (proposals approved before this version ask for approval again).
* After signing: a step that stopped half-way is no longer run again on its own; you choose with "Run the steps left again". The webhook address must start with https://.
* FluentCart: the payment products are made through FluentCart's own models.
* WooCommerce: declared compatible with its order tables (HPOS) and block checkout.
* Personal data export in pages; reports counted by the database, for any number of proposals.
* Uninstall: settings and AI settings are kept unless "delete data" is ticked.

Aluleth Proposals 0.5.2 (included)
* Signed PDFs and documents: kept in a private folder with a random name (older files move there). A daily check tells the site admins when the web server (Nginx) lets the folder be opened, with the rule to add; ALULETH_PROPOSALS_FILES_DIR in wp-config.php keeps them outside the website.
* "Your turn" emails to signers are recorded before they are sent, with a unique key: two people signing at the same moment never send them twice.
* Limits and counts (forms sent, openings, quote requests) are counted in one database statement, so requests at the same moment are all counted.
* A signed PDF is made once, also when it is downloaded twice at the same moment.
* Two proposals saved at the same moment cannot get the same number.
* Works without the mbstring PHP extension.
* WooCommerce: declared compatible with its order tables (HPOS) and block checkout.