Restricting Formulate package access breaks editing of Content nodes
Our client is not savvy enough for us to want them ever touching the Formulate (1.3.0) section of their website admin. We've got some cool stuff happening and the slightest alteration could bring the whole thing down :)
However there is an ability in some Document Types on their site, for editors to choose a pre-configured Formulate Form to display on a page (using Pick Configured Form property).
Our client's user account has access to Content and Media Sections but NOT Formulate.
This results in the following issues.
When they browse a page node and click to "Choose" a pre-configured Formulate form, they are sent to the Umbraco log-in page with a message "Session timed out."
When they try to Edit a node (by clicking on the node name in the Content list) where a form has previously been chosen, they are also sent to a login page with the "Session timed out." message. They cannot edit other elements of the node.
Cheers,
TFA
ps. Tried the new reCaptcha form element. Not working. Error : You need to set the "key" attribute to your public reCaptcha key. Any instructions about where this might be set? Thanks.
That definitely sounds like a pain. I'll try to get that working this weekend (probably a matter of moving the web methods used by the form picker to a new controller that allows access for anybody who has permission to the content section).
Tried the new reCaptcha form element. Not working.
If you take a look at the reCAPTCHA field in your form in the back office, you should see some text that explains the two keys you'll need to add to your web.config app settings. Once you add those two keys, that instructional text will disappear.
We've got some cool stuff happening and the slightest alteration could bring the whole thing down
That sounds like fun. I'd love to hear about it if you care to share someday :-)
That 1.3.1 release is FANTASTIC.
I can now leave the form picker in my page nodes, and lock the formulate editor off from prying hands.
THANK YOU!
I will endeavour to tell the entire story of our client's site upon launch. Suffice to say, it's very simple for the editors to reuse Formulate forms for lot's of purposes.
ps. Our Dev is polling the AngularJS back-office now to try and locate messages about reCAPTCHA requirements. We can't see anything like instructional text in Umbraco. Perhaps adding these clues to the CMS interface for Formulate would be helpful? Or adding this dependency to the instructions doc? Maybe it is there... but I just can't find it! :)
Correction: We see it! It just didn't get deployed to the staging environment from Dev. Looking at what dependency we missed!
Strange: There was a comma in the web.config default recaptcha key values when it was deployed to the web server. The commas resulted in the Umbraco back-office tips not rendering.
// Ensure the Recaptcha keys exist in the web.config.
foreach (var recaptchaKey in recaptchaKeys)
{
if (!DoesAppSettingExist(recaptchaKey))
{
settings.Add(recaptchaKey, string.Empty);
}
}
Restricting Formulate package access breaks editing of Content nodes
Our client is not savvy enough for us to want them ever touching the Formulate (1.3.0) section of their website admin. We've got some cool stuff happening and the slightest alteration could bring the whole thing down :)
However there is an ability in some Document Types on their site, for editors to choose a pre-configured Formulate Form to display on a page (using Pick Configured Form property).
Our client's user account has access to Content and Media Sections but NOT Formulate.
This results in the following issues.
When they browse a page node and click to "Choose" a pre-configured Formulate form, they are sent to the Umbraco log-in page with a message "Session timed out."
When they try to Edit a node (by clicking on the node name in the Content list) where a form has previously been chosen, they are also sent to a login page with the "Session timed out." message. They cannot edit other elements of the node.
Cheers, TFA
ps. Tried the new reCaptcha form element. Not working. Error : You need to set the "key" attribute to your public reCaptcha key. Any instructions about where this might be set? Thanks.
That definitely sounds like a pain. I'll try to get that working this weekend (probably a matter of moving the web methods used by the form picker to a new controller that allows access for anybody who has permission to the content section).
If you take a look at the reCAPTCHA field in your form in the back office, you should see some text that explains the two keys you'll need to add to your web.config app settings. Once you add those two keys, that instructional text will disappear.
That sounds like fun. I'd love to hear about it if you care to share someday :-)
This has been fixed in the latest version of Formulate (1.3.1).
That 1.3.1 release is FANTASTIC. I can now leave the form picker in my page nodes, and lock the formulate editor off from prying hands. THANK YOU!
I will endeavour to tell the entire story of our client's site upon launch. Suffice to say, it's very simple for the editors to reuse Formulate forms for lot's of purposes.
ps. Our Dev is polling the AngularJS back-office now to try and locate messages about reCAPTCHA requirements. We can't see anything like instructional text in Umbraco. Perhaps adding these clues to the CMS interface for Formulate would be helpful? Or adding this dependency to the instructions doc? Maybe it is there... but I just can't find it! :)
Correction: We see it! It just didn't get deployed to the staging environment from Dev. Looking at what dependency we missed!
Strange: There was a comma in the web.config default recaptcha key values when it was deployed to the web server. The commas resulted in the Umbraco back-office tips not rendering.
FYI, the default values should be an empty string. Here's the code that adds the defaults: https://github.com/rhythmagency/formulate/blob/119904ad313c15c59fb909df5642c0b15d4e2bfd/src/formulate.app/Handlers/ApplicationStartedHandler.cs#L590
is working on a reply...