I will enable the Private Form so you can submit me the required details.
I need to confirm, Is this a issue in CRED?
Behause Types by itself will not let you create Front End Editable Calendar (Date Fields)
It only will display the Date selected.
If this is about Types, can you elaborate where and how the issue happens?
The 502 gateway error is an unrelated server issue I'm discussing with my host. It only lasts for about 15seconds before everything returns to normal.
What I've done so far:
- Copied my site to staging3.balifoodsafari.com (HTTPAUTH: balifood:dev123)
- Created a new CRED form and used auto generate
- Displayed it on a new test page : hidden link
- Disabled plugins likely to interact with its execution: iThemes Security, WP-Rocket
- Checked Console for any JS Errors (none)
At this point the error was still occuring.
I then swapped to TwentyFifteen theme and the field worked correctly. So the issue is a conflict between the theme and the CRED form.
Any idea what the conflict could be or how to resolve?
Please send me the Theme in a Zipped File via Google Drive or DropBox, and it the Theme is a active supported Theme where we can reproduce the problem and contact the Author we can try to get in touch with them
Then we perhaps can work on a fix.
Not always the solution can be provided by use, as it might depend on cooperation of the 3rd Party Software developers.
The issue is reproduced but this is the Theme's "fault", CRED works just fine with many other WordPress Themes out there.
I escalated the issue to our DEV for the porpoise to get in touch with the Theme DEV Team.
Please can you contact your Theme's Developers and inform them, that there is a Conflict with the CRED Plugin, and ask if they are willing in a Co-Work with Toolset Developers to solve this issue?
I’m Adriano, Toolset support lead and I have been escalated to this thread. I’ll give my best to help you to achieve your needs through Toolset components.
I've spent some time testing this and it ended up being a CSS issue in the theme. Adding the CSS below will solve the issue:
Ok, no problem if you're not entirely sure, just thought if there was an explanation for it it's something I'd be able to catch and work out myself next time.
Thanks again for all your assistance working through this issue 🙂
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.