Chuyển đến nội dung chính

[CQ Embedded Form] Route to different pages after submit on CQ embedded form

Issue

In CQ you have the form functionality available that allows you to create a form on a page, for each form you can specify a “thank you” page that will be displayed when the form is submitted.
In this blogpost I will explain how you conditionally can route to different thank you pages depending on the values entered by the user.

Solution

Use request.setAttribute(“cq.form.redirect”,”/content/myproject/en/thank-you-no.html”); in forward.jsp.

Detail

Create a simple form
The first step here is to create a (simple) form to test the basic functionality.
You start with the “form” component, after this you can drag/drop other form-components like textfields etc in your form.
Configure the thank-you page
When you click “Edit” on the “Start of Form”, you can configure the “Thank You Page”, where the user will be redirected to after submitting the form.
So until now this is all out of the box functionality, the implementation of this you can see via CRXDE Lite via this path : “/libs/foundation/components/form”
In the advanced-tab you can choose the Action Type you want to use for your form after submitting the form.
In our case we will use the “Store Content” (default) action, that is implemented via this path : /libs/foundation/components/form/actions/store
Every “Action Type” consists out of some default JSP that can be found here : /libs/foundation/components/form/defaults/action
I will add some logic in the “forward.jsp” to implement the dynamic routing. For doing that I copied only the forward.jsp from /libs/foundation/components/form/actions/store to /apps/foundation/components/form/actions/store.
In the forward.jsp I added the following lines at the end of the file :
// added : if no was chosen for download, go to a different thank you page
// request.getParameter(“download”) will retrieve the value for the yes/no option
if ( “no”.equals( request.getParameter(“download”))) {     request.setAttribute(“cq.form.redirect”,”/content/myproject/en/thank-you-no.html”);
}
// end of added code
FormsHelper.setForwardPath(slingRequest, path);
request.setAttribute(FormsConstants.REQUEST_ATTR_REDIRECT_TO_REFERRER, “true”);
%>
When you now submit the form and you choose “no” for download it will redirect you to a different page than when you choose “yes” for the download option.
Next steps:
This example is just to give you an idea where to make the changes if you have such a use-case.  If you have multiple forms then you have to consider extending or implementing an action whereby the author can specify the rules instead of hardcoding it.

By Feike Visser

Nhận xét

Bài đăng phổ biến từ blog này

How to add a new supported language in CQ / WEM (Translator in CQ)

Use case:  You want to add new language to CQ Change display language options in translator grid Change language name and default countries  Solution: You can access translator UI in CQ with following URL http://<HOST>:<PORT>/libs/cq/i18n/translator.html Create new language location for Dictionary Go to CRXDE lite (or your favorite JCR browser) and add this structure (assuming /apps/myapp/i18n as a typical location for custom apps): /apps/myapp/i18n [sling:Folder]     - de [nt:unstructured]         + jcr:mixinTypes = [mix:language]         + jcr:language = de     - fr [nt:unstructured]         + jcr:mixinTypes = [mix:language]         + jcr:language = fr Then reload the translator and the path /apps/ myapp /i18n should show up in the drop-down at the top. Note: the translator will only save translations for languages that are actually present underneath the path (e.g. /apps/myapp/i18n), others will be skipped. Then on jsp pa

Login / Logout on a Publish instance and Closed User Group (CUG)

In CQ5 there is the login logout could be configured using a Closed User Group. Closed User Groups (CUGs) are used to limit access to specific pages that reside within a published internet site. Such pages require the assigned members to login and provide security credentials. http://dev.day.com/docs/en/cq/5-4/howto/create_apply_cug.html The logout using /libs/cq/core/content/login.logout.html always gets redirected to the geometrixx site   http://localhost:4503/content/geometrixx-outdoors/en.html By configuring the Default login page  under the osgi configuration for com.day.cq.auth.impl.LoginSelectorHandler to be – /content/mysite/en/login But still after logout the page goes to the geometrixx site. IIRC, the redirect first goes to to / which then goes through the standard, somewhat complex handling of the root with multiple redirects: 1) / has a resource type of sling:redirect and redirects to /index.html 2) /index.html is handled by the RootMappingServlet [0] which h

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene