Another thing: When you send the form, does the send button get disabled? Or do you get a browser message when refreshing the page after clicking on the send button?
The 2.3 version had a simple one page guide on github to install and configure. Only controller, template form and little else.
For install the 3.0.1 there is 5 page of documentation to read, there aren’t simple example to copy or a linear guide and (I now I’m ignorant) I don’t know what is the Guards and how to configure it.
I promise that I try the 3.0.1 in the weekend, but I’m only a poor frontend developer, a day maybe…
Thanks for the feedback! I try to improve Uniform where I can and my goal for v3.0 definitely was not to make it harder to use.
The “Installation”, “Setup” and “Quick example” sections of the GitHub readme should get you up and running already. Do you have suggestions how to improve the readme for a quick start?
The Usage section of the documentation should be the one page guide you are looking for. Please get back to me if you think it can be improved. All other pages of the documentation (Methods, Guards, Actions etc.) are for advanced usage and reference only. You shouldn’t have to read them to get started with Uniform
I too have this problem. I have a form and the logic in the site footer (snippet) and it works great on all the subpages but not on the home page. The form action looks like this
action="<?php echo $page->url()?>/#main-footer"
I have tried to add and remove the “/” before #main-footer but still the same problem.
In Chrome Dev Tool I can see that Request Headers looks like this:
:authority: domain.com
:method: POST
:path: /
origin: https://domain.com
referer: https://domain.com/
From a subpage it looks like this:
referer: https://domain.com/products
No “/” at the end of the url. Is this the problem? If, yes, how do I fix this? I want the urls to end without a “/”.