I would like to ask you to improve the procedure to change the colors of the forms.
Add an option to change the predefined colors in the color picker. It’s easy to select a color from there, but it’s pretty useless because you can’t predefine your own colors. So you keep on having to copy and paste the hex codes from elsewhere. For every single setting.
Add an option to change the default colors on a higher level. For example, each element/field has it’s own color settings for the label, background, border, text, placeholder. Often different settings for default, hover and focus. If you want to change that color, you have to do it in a hundred different places. Provide a place where you can specify a default color for all of these elements, for example under field basics. Then let all elements/fields follow these defaults, unless it’s overruled on the element level.
Or, if you change a color, ask if you also want to replace the <old> color for the <new> color. So if the text color is black and you change it to blue, ask if you want to change all black settings into blue settings.
There is no preview for the ‘Global Appearance Presets’. So the cumbersome procedure is to change a preset, save, then apply the preset to a form, save the form and (pre)view the form. To make this easier, provide an option under a form » appearance, to save the current settings as a preset and also allow to overwrite an existing preset.
At the moment if you want to use a preset, you need to select the preset and apply it to the form, after which the settings are copied to the form. So if you change a preset, you need to apply it to each and every form. It would be better if you can just link a preset to a form after which the form follows the settings of the preset, instead of it’s own settings.
Thank you for all the details. I have passed your suggestions to our developers to review this and see what is possible in those cases, and whether we can consider those in future updates. We will post an update here as soon as more information is available.
We received further feedback from our Forminator team.
We are currently in the initial phase of collaboration with the design team and management to finalize the user experience. We are also working on enhancing the new features based on user feedback.
Your feedback is important to us, and we will work on improving the colors in future updates.
That said, this was already forwarded to our developers and I am marking this thread as resolved, but if you have any additional questions, feel free to let us know.
I tried to subscribe to the roadmap, but it doesn’t accept my email address. Is there a filter to not allow .nl domains? I tried multiple addresses on my own domain @horecawebservice.nl and none of them are accepted. It also doesn’t accept a Gmail address with plus-addressing.
Also, can you only subscribe to the generic roadmap that holds all products? I am only interested in the Forminator roadmap.
I tried to subscribe to the roadmap, but it doesn’t accept my email address. Is there a filter to not allow .nl domains?
Could you please confirm if you notice any specific error while trying to subscribe?
I was able to check this further with our team internally, and we don’t block any specific TLD. It could be the issue not related to TLD but more about the deliverability, whether the email can receive emails or not. Can you please confirm if the email you entered was an active email address which can recieve emails?
It also doesn’t accept a Gmail address with plus-addressing.
Indeed, this is related to the same validation; it won’t allow email addresses from Gmail etc, to use a Plus address.
I would recommend you use a valid email ID which is able to recieve emails and it should ideally work fine without any issues.
Also, can you only subscribe to the generic roadmap that holds all products? I am only interested in the Forminator roadmap.
I am afraid, at the moment, we only have a generic roadmap focusing on all products.
This is what I get, the entered address is a valid email address that can send and receive e-mail.
Why does it not except plus-addressing from gmail or an alias from a real address on my own TLD? I use these methods for spam prevention. I don’t use my day to day address for subscriptions.
Why does it not except plus-addressing from gmail or an alias from a real address on my own TLD? I use these methods for spam prevention. I don’t use my day to day address for subscriptions.
I’m afraid adding plus isn’t supported. I also could notice alias isn’t accepted too, and have brought this to our teams attention to see what might be causing it and if this could be improved.
Will keep you posted once we give a closer look. For now, I’m afraid emails without plus and alias will only work.
Thanks, but a real email address wasn’t accepted either…
As for the +addressing/alias, I think it’s bad you don’t accept them because they exist for spam protection. If I would subscribe with my real email address and your system gets compromised, it ends up on a spam list. It happens. Several +addresses/aliases I have used, ended up on spam lists. I know, because due to the +address/alias I can exactly see who I gave that address. Among them are well known, big companies. Why don’t you accept them in the first place? To prevent fake subscriptions? Just use a double optin or unsubscribe when they bounce.
I understand your frustration. The roadmap subscription form includes a verification feature that checks email addresses. If the email is valid and has an inbox, it passes; otherwise, it is marked as invalid. The system doesn’t accept email aliases or plus addressing.
I’ll consult with the team and update you on whether there’s a way to allow your domain. If not, you’ll need to use any email address with a working inbox.
I highly appreciate understanding and cooperation in this matter.
Your feedback has been forwarded to the developers, and we’re marking this thread as resolved for now. Please feel free to reopen it, in case you still have any questions or need our assistance.