{"id":630,"date":"2024-04-25T06:50:37","date_gmt":"2024-04-25T04:50:37","guid":{"rendered":"https:\/\/website.mosparo.local\/?p=630"},"modified":"2024-04-25T06:55:55","modified_gmt":"2024-04-25T04:55:55","slug":"new-features-changes-in-version-1-2","status":"publish","type":"post","link":"https:\/\/website.mosparo.local\/2024\/04\/25\/new-features-changes-in-version-1-2\/","title":{"rendered":"New Features & Changes in Version 1.2"},"content":{"rendered":"\n

The new version, v1.2, contains several new features, changes, and bug fixes. We want to give you an overview of the most important changes in this version.<\/p>\n\n\n\n

Important: <\/strong>A bug fix regarding verifying the origin hosts can break your form. Please verify that you configured your hosts in the project settings correctly and verify the functionality of your form after the upgrade to v1.2. Read more about it in the documentation<\/a><\/p>\n\n\n\n

New features<\/h2>\n\n\n\n

Compatibility with PostgreSQL<\/h3>\n\n\n\n

In January 2024, we received a question from a user if it\u2019s possible to use mosparo with a PostgreSQL database instead of the MySQL database. When we started developing mosparo, we only concentrated on using MySQL because using two database systems would complicate many things (regarding our dependencies on Symfony\/Doctrine).<\/p>\n\n\n\n

We now took a second look at the options and added a different option to configure the database. With this new approach, our development was almost unchanged, and we were able to add compatibility to PostgreSQL.<\/p>\n\n\n\n

With the new version, while installing mosparo, you can decide if you want to use a MySQL or PostgreSQL database.<\/p>\n\n\n\n

Suggested by <\/em>skid9000<\/em><\/a><\/p>\n\n\n\n

Security feature to block repetitive submissions<\/h3>\n\n\n\n

We received the question of whether blocking repetitive submissions with mosparo is possible. Repetitive submission means that the same form data gets submitted multiple times. Since that was not possible before, we\u2019ve added a fifth security feature to the project security settings, which will block repetitive submissions.<\/p>\n\n\n\n

It\u2019s possible to configure the number of submissions and the time frame in which it should be counted. Additionally, it\u2019s possible to configure whether repetitive submissions should be counted based on the IP address or all users.<\/p>\n\n\n\n

Suggested by <\/em>Geremia<\/em><\/a><\/p>\n\n\n\n

Web-based cron jobs<\/h3>\n\n\n\n

We\u2019ve added the option to enable web-based cron jobs to make it easier to execute the cron jobs. These cron jobs can be enabled in the administration interface and are not enabled by default (for security reasons).<\/p>\n\n\n\n

As soon as enabled, you can set up a cron job to request a URL. You can also use an external cron job service to execute the mosparo cron job by defining a cron job with the cron job address.<\/p>\n\n\n\n

Inspired by <\/em>mpaglia0<\/em><\/a><\/p>\n\n\n\n

Changes<\/h2>\n\n\n\n

Upgrade to Symfony 6.4<\/h3>\n\n\n\n

The framework we use, Symfony, got upgraded to the latest LTS version, 6.4. We\u2019ve also updated all the other dependencies to the latest version.<\/p>\n\n\n\n

While this changed many things in the code, it should not impact the user interface or the functionality of mosparo in general.<\/p>\n\n\n\n

Negative spam rating for rules<\/h3>\n\n\n\n

We received the question of whether it\u2019s possible to reverse a rule, for example, if it\u2019s possible to mark submissions from all countries except one as spam. While we considered this question, we detected that it\u2019s impossible to add rules with a positive effect.<\/p>\n\n\n\n

As an easy solution, we\u2019ve adjusted the spam rating value fields for the rule items and changed them to allow negative values. With this change, adding rule items with a negative rating value is now possible.<\/p>\n\n\n\n

When the form data is validated, the total number of points is calculated to determine whether a submission is spam or not. A rule with a negative value can reduce the number of points, for example, if the submission is from a specified country or IP subnet.<\/p>\n\n\n\n

Inspired by <\/em>cesare190<\/em><\/a><\/p>\n\n\n\n

Compatibility with reverse proxy subpath setup<\/h3>\n\n\n\n

We\u2019ve added some adjustments to mosparo to allow using mosparo in a subpath setup with a reverse proxy. With these changes, it\u2019s possible to set up mosparo in a subpath like example.com\/mosparo\/, as long as you configure it with a reverse proxy.<\/p>\n\n\n\n

We still recommend using a domain or subdomain to set up mosparo, but there is no reason not to install it in a subpath with a reverse proxy.<\/p>\n\n\n\n

Inspired by <\/em>davd-edia<\/em><\/a><\/p>\n\n\n\n

Accessibility optimizations<\/h2>\n\n\n\n

While testing compliance with WCAG 2.1<\/a>, Access for all found multiple things that could be optimized for better usage of assistance tools. We implemented the majority of these recommendations with v1.2.<\/p>\n\n\n\n