Wondering if anyone is having issues with the form action upon subscription submission?
Currently, with or without the opt in option enabled, on sign up submission, the user is taken to a random page on the site.
Disregarding the url that I define in the subscriber list "Confirmation success page" field.
The form action seems to be randomly defined.

example: http://www.wickinn.com/discover-tofino

Thanks,

Roger

Comments

cableman0408’s picture

cableman0408 commented

I have seen behavior link this on other sites where it turned out to be the block cache, that was the issue. Could you try with and without block cache turned on ?

RogerSarrasin’s picture

RogerSarrasin commented

Thank you for your reply. The block cache was the problem! When turned on, the form action was redirecting to a random page. With Block Cache off, it is submitting and keeping the user on the current page.

Still having an issue with trying to direct the user to a success page upon clicking the submit. Success page url is set in the newsletter subscriber list in the module and in in the CM account.

Thanks again!

Roger

RogerSarrasin’s picture

RogerSarrasin commented

Thank you for your reply. The block cache was the problem! When turned on, the form action was redirecting to a random page. With Block Cache off, it is submitting and keeping the user on the current page.

Still having an issue with trying to direct the user to a success page upon clicking the submit. Success page url is set in the newsletter subscriber list in the module and in in the CM account.

Thanks again!

Roger

woeldiche’s picture

woeldiche commented
Version: 7.x-1.0-rc1 » 7.x-1.0-rc2

We are experiencing the same issue on RC2. Even with submit and unsubscribe pages defined the newsletter form just redirects to the current page and shows a Drupal message with the information.

cableman0408’s picture

cableman0408 commented
Category: support » bug
Status: Active » Fixed

The issue have been resolved in the development branch :-). Thanks for reporting the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.