Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conditional / flexible content field support #314

Open
onetrev opened this issue Dec 21, 2018 · 3 comments
Open

Conditional / flexible content field support #314

onetrev opened this issue Dec 21, 2018 · 3 comments

Comments

@onetrev
Copy link

onetrev commented Dec 21, 2018

A flexible content field (similar to the similarly named field in Advanced Custom Fields for WordPress) would add a massive amount of power and functionality to Grav forms.

The idea for this was posted a Grav discourse post, along with some code to essentially get it working. But if this could be integrated into the Form plugin core that would be amazing!

@mahagr
Copy link
Member

mahagr commented Jan 3, 2019

There's one more thing that needs to be taken into consideration: form validation.

@onetrev
Copy link
Author

onetrev commented Nov 19, 2019

Hey @Romarain I was just wondering how you ended up going with your JS script that would enable this in Grav? Were you thinking of creating a pull request?

@Heraes-git
Copy link

Heraes-git commented Mar 20, 2020

@onetrev Sorry for the late response. Glad you mention my work.
It ended well and work perfectly for its purpose : making some form fields to be conditioned by other fields' states. It also give the power to mix several layers of conditioning ( A conditioning B, B conditioning C, etc).

I never posted it publicly because I was wondering if I could sell it (i try to start my business and anything count), but I could give it to Grav for it to integrate in the project, as a "thank you" gift. It would be the least I can do.

But things gone wild in the Discord of Grav, and I've been told to stop interacting with people. So now, I suppose I'd rather release it for my own account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants