Answers.Body: <p>I found the solution in <a href="https://civicrm.stackexchange.com/questions/6558/send-test-and-next-not-clickable-greyed-due-to-missing-value-in-reply-id-field/6559#6559">another question</a>. Go to Administer > CiviMail > Headers &amp; Footers. Edit the auto-responder, set default to yes. The Next and Test buttons in new mailings should now be enabled.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-13T05:11:49.240Z
Answers.LastActivityDate: 2015-12-13T05:11:49.240Z
Answers.UserDisplayName: Sphinges
Answers.Body: <p>Unfortunately, my last post affirming that the problem is real and still present in the current version was deleted because the moderator thought it would be better as a 'comment' without realizing that commenting is disabled for most users. I'm not yet certain of the cause but there are a few fields in the civicrm_mailing table. In particular, the reply_id field (and a few other suspects) look like they may not be getting updated properly.
  Nicholai, I'd have been happy to post this as a comment if you would be kind enough to enable commenting for individual's with a reputation of less than 50.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-10T02:58:00.880Z
Answers.Text: I can confirm that manually setting the reply_id field in mysql enables the next & test buttons in the mailing.
Answers.UserDisplayName: Sphinges
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-12T17:39:54.343Z
Answers.Text: We've stumbled upon the same solution, at about the same time. Now what's the problem???
Answers.UserDisplayName: Jeff Wood
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-12T21:09:18.553Z
Answers.Text: As I posted in another place, possibly this will shed some light on the cause:
  In my case, I had a site where the Auto-responder (from Administer > CiviMail > Headers, Footers, and Automatic Messages) was disabled when the first mailing was created (actually, all of the pre-configured messages/headers/footers were disabled). Enabling all of them and setting as default didn't fix the already created mailing (the "Send Test" and "Next" buttons were still disabled) but everything worked properly in a new mailing, created after enabling pre-configured messages/headers/footers.
Answers.UserDisplayName: Kasia W
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-02T23:53:39.650Z
Answers.LastActivityDate: 2015-11-02T23:53:39.650Z
Answers.UserDisplayName: Jeff Wood
Answers.Body: <p>Since one of the above comments confirms that it works fine on demo instance, I think a possible solution will be to upgrade to latest <strong>4.6.x</strong> version. ( <em>if upgrade is possible</em> )</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-28T07:47:51.280Z
Answers.LastActivityDate: 2015-10-28T07:47:51.280Z
Answers.UserDisplayName: Kurund Jalmi
Answers.Body: <p>Just found another possible reason whereby no warnings are given. A user has created a template, and created a txt only template too. The footer had unsub in, neither of the above had opt out. I added opt-out to HTML but of course Plain Text was not expanded so i didn't know it was even in use!! And so setting the token in there fixed it. but at no point of the OptOut button being missing from either did i get a warning, until i saved, closed, continued and bingo Plain Text was expanded and showed the warning</p>
  
  <p>I found a couple more situations that the greyed out button can appear which may be less than obvious</p>
  
  <ul>
  <li><p>if there is no Resubscribe Msg set on the Response tab (no alert is currently provided</p></li>
  <li><p>if you put in a Subject, but then decide to switch to using a Template the Subject gets changed to the Subject of the Template, so if the Template does not have one you may get surprised</p></li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2016-06-22T08:14:44.230Z
Answers.LastActivityDate: 2020-04-01T00:23:32.603Z
Answers.LastEditDate: 2020-04-01T00:23:32.603Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>New mailings with all required fields and the default responsive template do not enable the Next or Test mailing buttons. As a workaround I can reuse an old mailing and update the fields. The last successful mailing was sent using 4.6.2, the current installed version of CiviCRM is 4.6.3.</p>
  
  <p>Drupal 7.38</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-07-07T22:51:14.897Z
Comments.Text: since 4.6.4 is now available you probably want to check if you can replicate your problem on Demo and if not, then upgrade and test again
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-07-07T22:56:10.117Z
Comments.Text: I'll try that, but I didn't see anything related in the issue tracker.
Comments.UserDisplayName: Sphinges
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-10T17:02:46.647Z
Comments.Text: Upgrading to 4.6.6 did not resolve the issue.
Comments.UserDisplayName: Sphinges
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-10T21:03:34.787Z
Comments.Text: So it sounds like civi thinks something is missing hence the Next and Test options are greyed out? Presumably there is nothing obvious eg 'no recipients' message or lack of opt-out tokens etc. Might be worth trying to compare with a 'new mailing' on http://d46.demo.civicrm.org/
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-11T14:05:34.077Z
Comments.Text: The demo works as expected, as soon as I fill in all required fields the buttons are activated; they stay disabled on my site. I'm trying to find the code where the required fields are checked, it might help narrow down the cause if I disable the checks one by one.
Comments.UserDisplayName: Sphinges
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-10-15T19:29:29.280Z
Comments.Text: Drupal is up to 7.39 and civi to 4.6.9, the bug remains.
Comments.UserDisplayName: Sphinges
Tags: <civimail><upgrade>
Title: Mailings - Disabled Next/Test Buttons
ThreadText: # Mailings - Disabled Next/Test Buttons
  
  (Asked by: username_0 on 2015-07-07)
  
  New mailings with all required fields and the default responsive template do not enable the Next or Test mailing buttons. As a workaround I can reuse an old mailing and update the fields. The last successful mailing was sent using 4.6.2, the current installed version of CiviCRM is 4.6.3.
  
  Drupal 7.38
  
  **Tags:** civimail, upgrade
  
  > **Comments:**
  > **username_1**: since 4.6.4 is now available you probably want to check if you can replicate your problem on Demo and if not, then upgrade and test again  
  > **username_0**: I'll try that, but I didn't see anything related in the issue tracker.  
  > **username_0**: Upgrading to 4.6.6 did not resolve the issue.  
  > **username_1**: So it sounds like civi thinks something is missing hence the Next and Test options are greyed out? Presumably there is nothing obvious eg 'no recipients' message or lack of opt-out tokens etc. Might be worth trying to compare with a 'new mailing' on http://d46.demo.civicrm.org/  
  > **username_0**: The demo works as expected, as soon as I fill in all required fields the buttons are activated; they stay disabled on my site. I'm trying to find the code where the required fields are checked, it might help narrow down the cause if I disable the checks one by one.  
  > **username_0**: Drupal is up to 7.39 and civi to 4.6.9, the bug remains.  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_0 on 2015-12-13. Score: 2 | Accepted answer
  
  I found the solution in [another question](https://civicrm.stackexchange.com/questions/6558/send-test-and-next-not-clickable-greyed-due-to-missing-value-in-reply-id-field/6559#6559). Go to Administer > CiviMail > Headers & Footers. Edit the auto-responder, set default to yes. The Next and Test buttons in new mailings should now be enabled.
  
  
  ---
  
  ### Answer by username_2 on 2015-11-02. Score: 2
  
  Unfortunately, my last post affirming that the problem is real and still present in the current version was deleted because the moderator thought it would be better as a 'comment' without realizing that commenting is disabled for most users. I'm not yet certain of the cause but there are a few fields in the civicrm\_mailing table. In particular, the reply\_id field (and a few other suspects) look like they may not be getting updated properly.
  Nicholai, I'd have been happy to post this as a comment if you would be kind enough to enable commenting for individual's with a reputation of less than 50.
  
  > **Comments:**
  > **username_0**: I can confirm that manually setting the reply_id field in mysql enables the next & test buttons in the mailing.  
  > **username_2**: We've stumbled upon the same solution, at about the same time. Now what's the problem???  
  > **username_3**: As I posted in another place, possibly this will shed some light on the cause: In my case, I had a site where the Auto-responder (from Administer > CiviMail > Headers, Footers, and Automatic Messages) was disabled when the first mailing was created (actually, all of the pre-configured messages/headers/footers were disabled). Enabling all of them and setting as default didn't fix the already created mailing (the "Send Test" and "Next" buttons were still disabled) but everything worked properly in a new mailing, created after enabling pre-configured messages/headers/footers.  
  
  ---
  
  ### Answer by username_4 on 2015-10-28. Score: 1
  
  Since one of the above comments confirms that it works fine on demo instance, I think a possible solution will be to upgrade to latest **4.6.x** version. ( *if upgrade is possible* )
  
  
  ---
  
  ### Answer by username_1 on 2016-06-22. Score: 0
  
  Just found another possible reason whereby no warnings are given. A user has created a template, and created a txt only template too. The footer had unsub in, neither of the above had opt out. I added opt-out to HTML but of course Plain Text was not expanded so i didn't know it was even in use!! And so setting the token in there fixed it. but at no point of the OptOut button being missing from either did i get a warning, until i saved, closed, continued and bingo Plain Text was expanded and showed the warning
  
  I found a couple more situations that the greyed out button can appear which may be less than obvious
  
  * if there is no Resubscribe Msg set on the Response tab (no alert is currently provided
  * if you put in a Subject, but then decide to switch to using a Template the Subject gets changed to the Subject of the Template, so if the Template does not have one you may get surprised
  
  
  ---
  
  