-
This is a very important project for me and I want to get it right. I have been looking at orchard but had to take a break because of my exams at uni. Now I am back and I want to continue learning Orchard. I have been struggling with understanding the rendering model. The samples are helping tremendously, but I still have some missing parts. I created these types and its corresponding files. The hierarchy of the types is as follows: And here is the FormTx definition, similarly to BlogPost, it has Tags, Subtitle and Category. And also: Essentially a FormTx has a title, subtitle to indicate what this form is form, and it can have tags and category. I think this is not the best solution, and I don't have a clear idea on how to implement this, but it is a start and I want to see where it will lead me, but you are more than welcome to suggest any changes or different way on how to implement this. Just to see how it looks on Content-FormTx.liquid And this is how it looks in the console This is my repo, if you can make some very quick changes, I would greatly appreciated. As I said this is very important project for me, so I can even pay some money (reasonably) just to learn this properly. EDIT: I am using pages to make new forms, as it was demo-ed from Lombiq in the OrchardCore tutorial. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
You have content item FormTx with FormPart but you have nothing in it to render. Attach a FlowPart so you could add form widgets like label, input, button to the form. Also Please share the rendered html |
Beta Was this translation helpful? Give feedback.
You have content item FormTx with FormPart but you have nothing in it to render. Attach a FlowPart so you could add form widgets like label, input, button to the form.
Also Please share the rendered html