The form component in AEM and all other form related components mandate that it should be used under parsys component (by dragging and dropping). When I use these form components without a parsys as their parent, are not behaving as expected for ex: form end component does not show submit button even though i have checked the option to show submit button.
Question: I want to use the form components but I don't want to use drag and drop. I want to create a reusable form component with predefined fields. Any way to achieve this?
Finally after a lot of searching, I found the best solution here :
http://versatileankur.blogspot.in/2014/11/component-with-default-components-in-cq5.html
Related
I need to add static text on my form (can't use the xrm notification option) under specific terms I need to show and hide that text but I can't hold it in a field.
First I thought to use an Image with my text on the form, is there a better way to do that?
Like said in comments, HTML web resource is the way to go. You can embed the HTML in a form section/tab and hide them using conditional scripting in form load.
Reference
in aem in touch ui using sightly if I add a parsys component with some width(ex:30%) and after adding some component to it next parsys should come after that one not below of the previous component. How can I do that one?
There is not something like "fixed-fluid layout" in AEM.
You should create a layout before drop the components, you can use column control to achieve this, take a look to the documentation: https://helpx.adobe.com/experience-manager/using/custom_columns.html
If a component is created, but a dialog.xml file isn't included within it, it will not show as available within the Sidekick, even if enabled in Design mode, and with a Component Group specified — why is this?
If you add a cq:editConfig node to the component it will show up in the sidekick, after being enabled in the design dialog of the parsys, without having a dialog.
As reference: http://dev.day.com/docs/en/cq/5-3/developing/components.html#Components and their structure
dialog boxes are meant for dynamically adding content to the components.
if there is no dialog box in a component there is no reason for component to display in sidekick .
u can directly hard code the component like this.
<cq:include path="par0" resourceType="/apps/...." />
Have you gone into the design portion to allow your component? I've often created a new component, and been unable to add it simply because I forgot to allow it in the design mode on that page.
EDIT
Good point - I do believe a dialog.xml file is required for it to show up in the sidekick. Otherwise you have to hard code the include of your component where you need it. I would suggest adding a dialog.xml file, even if it is only for the reason of showing it in the sidekick, so you can add it dynamically to different pages.
Is there a way to add HTML5 placeholders to Gravity Forms? I've tried a number of plugins, but none of them appear to work.
Gravity Forms: http://www.gravityforms.com/
One Plugin (that doesn't work): http://wordpress.org/extend/plugins/gravity-forms-auto-placeholders/changelog/
Another: http://wordpress.org/extend/plugins/gravity-forms-placeholders/
Yes, please see my answer on the following thread: Can I Define my own form markup and map with to the form generated using Gravity Form (wordpress plugin)?
This will add an extra field for text inputs that will allow for placeholder text. Very easy to implement, basically adding some code to the functions.php file.
I have a page where I need one form in the main content and one in the footer.
The problem is that these two forms should be connected.
The form in the main content have three input fields for name, email etc. and the one in the footer has two radio buttons.
The radiobuttons work as "I agree" so they have to, somehow, be connected to the other fields.
I use typo3 with powermailer.
I have a thougth of using css and just move those radiobuttons to the footer.
But I would like a more permanent sollution. Thanks.
I think that there is currently no better solution, but youre on the right way with CSS.
If i understood you correctly. You are trying to implement two plugins which are connected to each other. This is impossible with powermail.
Dirty, but useable is the CSS way or maybe a JavaScript solution for some fancy effects.