-
Notifications
You must be signed in to change notification settings - Fork 27
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
Cannot submit custom form #44
Comments
Hi, what is the exact error message you're getting? I'm assuming you get the "red screen of death", right? Otherwise, set |
Thanks for getting back. I have updated the original question. In my .env file I have:
Dump info
Red screen error is:
in var/cache/dev/twig/b4/b4bf65673e8d48cfd0be98a711189f44c25d8d79a65b5b1cddb7f0391eacee4c.php twig_get_attribute (line 50) If I comment out this
from article.twig, I don't see red error screen with "Call to a member function sanitise() on null" error anymore when submitting the form. |
Maybe the information is not useful to you, but it might hold a clue for us. Please make a full screenshot of the error screen. |
Sure, here you are, hope this helps. |
Are you getting the error on POST'ing only, or also when reloading the page later? I'm not sure what causes this. What i'd try to do, is maybe make a really simple contenttype with literally only a Then, simplify your form and only store that one field. If that works, add the fields one by one, pinpointing where it breaks.
Is that so? I think |
I only get that error when posting, not reloading. I made my form to only have content textarea and there is still the same error. Not I get the same error despite where I submit form: via shortcode or via custom. I bet It has to do something with displaying comment list below, because when I comment it out, no error. Regarding hidden input in boltform, I am not sure whether it is possible to set its value to something related to the current post being displayed. Does this have to be done in config? I am also not sure why this is needed "string_city_processor_string" or "table: bolt_secret_table" if I am storing a contenttype. |
That's what i was trying to get at: Is it breaking when adding something, or when retrieving it.. If you comment out the "displaying the comments", does it then work? |
Yes, If I comment out displaying comments bellow, it works, but only if "{{ boltform('commentForm') }}" is present. |
Any clue what might be wrong here? |
I get bolt forms last_processor_contact_domain too. Why Bolt Forms add this "extra" fields? |
Hi ! Maybe related to this issue ? I see you are using : from_name: name # A field name, specified in the fields: section below
replyto_email: email # A field name, specified in the fields: section below
replyto_name: name # A field name, specified in the fields: section below
from_email: email But actually it's not working |
Oh ho ho :-( I have described form config in ~/config/extensions/bolt-boltforms/myform.yaml Why Bolt Forms allowed to add this "extra" visible field and how I can fix it? |
Hello. I want to make a custom form to submit a comment for an article, and not to use {{ boltform('myForm') }} in order to pass some additional fields (author, articleId) that point to record relations.
I have the following code:
bolt-boltforms.yaml
article.twig
_comment_new.twig
Unless I put {{ boltform('commentForm') }} above
element, this form does not work. I prefer to make my custom form instead of using shortcode to insert it.If I put {{ boltform('commentForm') }} above my form, when submitting it I get an error:
HTTP 500 Internal Server Error
Call to a member function sanitise() on null
But after hitting enter in URL, page is reloaded and record saved.
Not sure where the bug is. Would be thankful for any insights.
The text was updated successfully, but these errors were encountered: