Hello @loevgaard, this plugin is a good idea because we often use CMS for this kind of pages. But I think it could be even better :)
Like cookies consent with GPDR, we should store the agreement between the customer and the company.
Terms and condition is similar to a contract signed between a customer and the company that run the website. A customer can complain on an order based on the previous year terms for example and as a company when a customer complain we should be sure what was the version of the terms he signed.
To improve the plugin I suggest to :
Add some versioning (disable editing on terms and only allow admin to create new versions) (maybe create a TermRevision Entity)
Store in each order the version of the term the user has "signed".
We may use a hash of the term content (md5 or other) on the TermRevision entity and store this hash in the order. The hash should ensure the term has not been modified.
NB : There are online services that warn their users when terms are changing, with this model this would be something doable if a sylius shop want to warn its customers when terms change...
Hello @loevgaard, this plugin is a good idea because we often use CMS for this kind of pages. But I think it could be even better :)
Like cookies consent with GPDR, we should store the agreement between the customer and the company.
Terms and condition is similar to a contract signed between a customer and the company that run the website. A customer can complain on an order based on the previous year terms for example and as a company when a customer complain we should be sure what was the version of the terms he signed.
To improve the plugin I suggest to :
NB : There are online services that warn their users when terms are changing, with this model this would be something doable if a sylius shop want to warn its customers when terms change...
Thank you for your work :)