Hi there.
I am developing a webiste that is in test subdomain for now.
How can i use my validation key to the subdomain and after the development move the same key to the live website?
I am developing a webiste that is in test subdomain for now.
How can i use my validation key to the subdomain and after the development move the same key to the live website?
Hi Panosgr ,
If I understand correctly
+ the free version will show you all your form in the Admin view (but only 15 inputs in the front-end view)
+ there is an option to enable a developer validation for 10 days that lets you see the whole form in the front-end view
+ if that is not enough you can use a validation key on the development site and then ask to have that transferred to the live site later.
Bob
If I understand correctly
+ the free version will show you all your form in the Admin view (but only 15 inputs in the front-end view)
+ there is an option to enable a developer validation for 10 days that lets you see the whole form in the front-end view
+ if that is not enough you can use a validation key on the development site and then ask to have that transferred to the live site later.
Bob
I will stick to the third option.
So i will validate the key to the demo url and when i will go online to the real url then you can change the key for me?
So i will validate the key to the demo url and when i will go online to the real url then you can change the key for me?
Thanks for directing me to this question, Bob. I didn't find it when searching.
Our form has more than 15 elements, so it would be a bit awkward not to see all of them during development.
This solution would work for 10 days, and then? Also, the validation key in the database would be different for dev and prod. So, when deploying to prod we would have to make sure to replace the key.
This isn't really a one-time process. Once the site is live, we still need a key to continue development.
I don't really get the point of not allowing a validation key for domain xyz.com on localhost. You can't run a live site from localhost. Also, many APIs handle it like that: You have a key for domain xyz.com, but can also use it from localhost.
+ the free version will show you all your form in the Admin view (but only 15 inputs in the front-end view)
Our form has more than 15 elements, so it would be a bit awkward not to see all of them during development.
+ there is an option to enable a developer validation for 10 days that lets you see the whole form in the front-end view
This solution would work for 10 days, and then? Also, the validation key in the database would be different for dev and prod. So, when deploying to prod we would have to make sure to replace the key.
+ if that is not enough you can use a validation key on the development site and then ask to have that transferred to the live site later.
This isn't really a one-time process. Once the site is live, we still need a key to continue development.
I don't really get the point of not allowing a validation key for domain xyz.com on localhost. You can't run a live site from localhost. Also, many APIs handle it like that: You have a key for domain xyz.com, but can also use it from localhost.
I don't really get the point of not allowing a validation key for domain xyz.com on localhost.
I just tested and it seems that this is actually working. I activated the key on domain xyz.com and imported the database in my dev environment. And ChronoForms seems to work.
Hello,
The new Elastic subscription should solve this problem by giving users the ability to validate multiple domains.
Best regads,
Max
The new Elastic subscription should solve this problem by giving users the ability to validate multiple domains.
Best regads,
Max
This topic is locked and no more replies can be posted.
