AEM submit form returning status = 500

[Weston_Leavitt]

Good Afternoon!

We've got a feedback form that we have setup to as follows:

[img]Screen Shot 2015-03-13 at 11.36.25 AM.png[/img]

[img]Screen Shot 2015-03-13 at 11.37.03 AM.png[/img]

When I test the form within aem, the form send through, and the email gets sent out, and the page returns with submit=200 in the url.

HOWEVER. when I publish the page, and try to then run the form from it's published url, it returns with submit=500, and the emails do not get sent out.

any ideas on what may be the issue? 

[smacdonald2008 · Accepted solution]

Looks like the endpoint that you are submitting to is not present on the pub instance.

Another option that you have is submit to a custom OSGi AEM service that sends email. On AEM pub instance - deploy the OSGi bundle. This way - you know for sure that the service is deployed on AEM pub instance.

To learn how to submit an AEM adaptive form to a custom service -- read this community article. 

https://helpx.adobe.com/experience-manager/using/posting-aem-6-form-data.html

In the AEM custom service - write email logic. See this article to learn how to perform that task:

https://helpx.adobe.com/experience-manager/using/creating-custom-cq-email-services.html

You have much greater control when you perform these tasks. 

[Weston_Leavitt]

Is there anyway this is possible while I do not have access to edit resources within the CRX? I am authorized only as an aem author, and do not have capabilities of creation within the CRX, but was asked to solve this problem. I'm guessing this would be an issue I would need to send backwards to our developers? it only started occuring when we ported to AEM 6.0

[smacdonald2008]

You need access to JCR when developing solutions like this. You need to add nodes and backend services via OSGi bundles.