Skip Navigation

[Resolved] Reaching cred form page “only” through another page

This thread is resolved. Here is a description of the problem and solution.

Problem: I would like to place a CRED form on my site, and I would like to require my site users to first fill out a captcha on another page of the site before accessing the CRED form.

Solution: The only way captchas are implemented in Toolset is inside a CRED form. If you want to add a captcha outside a CRED form, it will require custom code or another plugin. I think you could accomplish something similar with two CRED forms, though. Include just a captcha and a submit button in the first form. Configure the CRED form to redirect the User to another page after the form is submitted. Place the second CRED Form on that page. It's not strictly secure, because a User can type the second page's URL directly into the browser to bypass the first form.

There are two basic ways to prevent accessing a page in Toolset:
1. Restrict that page access to specific User role(s) using Toolset Access. If the first CRED form does not create or edit a User's account, then this probably isn't helpful because the User will be a guest when filling out form 1 and still a guest when filling out form 2. You cannot use different User roles in this case. Custom code would be required.

2. Use conditional HTML to hide the form in some circumstances. You can use custom code to provide the terms of that conditional code if you want, or you can use any Types or Views shortcodes.

Relevant Documentation:
https://toolset.com/documentation/user-guides/conditional-html-output-in-views/
https://toolset.com/documentation/user-guides/views-shortcodes/
https://toolset.com/documentation/customizing-sites-using-php/functions/

This support ticket is created 6 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 2 replies, has 2 voices.

Last updated by simranjeetS-2 6 years, 9 months ago.

Assisted by: Christian Cox.

Author
Posts
#620987

Tell us what you are trying to do?
I want to reach cred form only through another page. Example - on another website, I have to reach this page - hidden link to reach another page to fill form on this page hidden link . Unless I fill first page, I cant go directly to next. I want captcha and instructions to be on first page and cred form on next.

Is there any documentation that you are following?
No. But I am following above example.

Is there a similar example that we can see?
yes, see above

What is the link to your site?
Join form is here -
hidden link

#621131

Hi, I'll be glad to help.

I want captcha and instructions to be on first page and cred form on next.
The only way captchas are implemented in Toolset is inside a CRED form. If you want to add a captcha outside a CRED form, it will require custom code or another plugin. I think you could accomplish something similar with two CRED forms, though. Include just a captcha and a submit button in the first form. Configure the CRED form to redirect the User to another page after the form is submitted. Place the second CRED Form on that page. It's not strictly secure, because a User can type the second page's URL directly into the browser to bypass the first form.

There are two basic ways to prevent accessing a page in Toolset:
1. Restrict that page access to specific User role(s) using Toolset Access. If the first CRED form does not create or edit a User's account, then this probably isn't helpful because the User will be a guest when filling out form 1 and still a guest when filling out form 2. You cannot use different User roles in this case. Custom code would be required.

2. Use conditional HTML to hide the form in some circumstances. You can use custom code to provide the terms of that conditional code if you want, or you can use any Types or Views shortcodes. We have information about conditional HTML here:
https://toolset.com/documentation/user-guides/conditional-html-output-in-views/
Views shortcodes:
https://toolset.com/documentation/user-guides/views-shortcodes/
Types shortcodes:
https://toolset.com/documentation/customizing-sites-using-php/functions/

#621532

Thanks a lot. But it is too difficult for a non coder.