CapDecisions: ready for Dolibarr 24, public pages and demonstration made reliable

Compatible with Dolibarr 24

Dolibarr 24 requires an anti-forgery token on requests that previously did without. Two CapDecisions screens were missing it; they now include it:

• the image gallery for discussions and proposals loads again;
• the public page logout link actually logs the visitor out.

Complete public pages on screen

The public pages' stylesheet has been rebuilt: several elements were displayed without formatting. The vote result bars, the button loading indicator, and the login code input field have regained their appearance.

The correct vote count on all databases

Under PostgreSQL and SQLite, the card of a proposal displayed an incorrect total of votes. It now counts each voter, regardless of the database.

A demonstration at the scale of a real structure

The demonstration dataset now represents an organisation of around fifty members: fifty third parties and their contacts, eight groups, months of discussions, proposals of the five decision types with their votes and comments. Dates start from the day of generation: over a year of history, and ongoing votes, some of which end within two days.

A demonstration dataset that can be relaunched

The demonstration data generator can be relaunched as many times as necessary: existing data is reused, nothing is duplicated, and a login belonging to a real account stops the generation without any changes.

The demonstration accounts use the module's name: capdecisions.animateur, capdecisions.membre and capdecisions.observateur. Since their addresses are fictitious, no login code is sent to them by email: the public login page displays the code directly.

For the administrator

Every message the module writes to the Dolibarr log starts with CapDecisions, followed by the relevant method, and a rejected image upload or deletion leaves its reason. A simple filter is enough to monitor the module.

Installation and compatibility

Dolibarr 18 to 24, PHP 7.4 or later. The update is done by simply replacing the module, with no database migration.

Try it

Try CapDecisions on a Dolibarr installed in under 20 seconds, with groups, discussions and demonstration proposals already filled: dolitry.fr/capdecisions