Can't save schedule step by step (was: New issue - subject line can't be edited)

 
From: "Mary Ann Kelley maryann@PROTECTED [Dada Mail Developers]" <dadadev@PROTECTED>
In-Reply-To: (no subject)
Date: July 25th 2016
Not sure when I can update the installs, but had to schedule a mailing this morning and this is the step by step with screenshots.

  1. Choose Send a Webpage from Mass Mailing dropdown.
  2. Paste URL of HTML webpage into the “Grab content from a URL” field under HTML Version tab.
  3. Add subject line
  4. Click “Save as Schedule”
  5. Choose date and time under "Single -> Schedule for:" (Leave Activate checkbox empty for now) 
  6. Screenshot just before clicking Save Schedule: https://www.evernote.com/l/AG1WxI4k6FdJc7P72ze4M2EXeyxrsC4QrMQ
  7. Click Save Schedule
  8. Screenshot just after clicking Save Schedule (note the missing time and date that had been present): https://www.evernote.com/l/AG3yw96VxlZHaa3n1RBXzw9LAAaI0MmZjxQ
  9. Choose date and time again under "Single -> Schedule for:” again (still leaving Activate checkbox empty for now) 
  10. Choose Send Test
  11. Screenshot just after clicking Send Test: https://www.evernote.com/l/AG3J67GMwaJJW7SXRyfBbBAh6knV1KfNhKk

Sending the test saved the schedule but clicking Save Schedule did not. Oddly, once the schedule was saved the first time by sending a test, I could click the Save Schedule button and it saved the changes made afterward (namely the subject line and the activation checkbox, both of which were giving me trouble before). I don’t understand why Save Schedule doesn’t work until after the schedule is saved through sending a test.

Error log:

[Mon Jul 25 14:10:10 2016] mail.cgi: doesn't have a draft! at /DADA/App/MassSend.pm line 1681.
[Mon Jul 25 14:15:02 2016] mail.cgi:     (in cleanup) Can't access 'DESTROY' field in object of class DADA::App::ScheduledTasks at /cgi-bin/dada//DADA/App.pm line 13507.
[Mon Jul 25 14:20:02 2016] mail.cgi:     (in cleanup) Can't access 'DESTROY' field in object of class DADA::App::ScheduledTasks at /cgi-bin/dada//DADA/App.pm line 13507.
Problem fetching webpage, '':400 URL missing at /DADA/App/MassSend.pm line 743.
[Mon Jul 25 14:22:18 2016] mail.cgi: returning message id<xxxxx> at /DADA/App/MassSend.pm line 409.
[Mon Jul 25 14:25:01 2016] mail.cgi:     (in cleanup) Can't access 'DESTROY' field in object of class DADA::App::ScheduledTasks at /cgi-bin/dada//DADA/App.pm line 13507.
Problem fetching webpage, '':400 URL missing at /DADA/App/MassSend.pm line 743.
[Mon Jul 25 14:25:50 2016] mail.cgi: returning message id<xxxxx> at /DADA/App/MassSend.pm line 409.
[Mon Jul 25 14:30:02 2016] mail.cgi: (in cleanup) Can't access 'DESTROY' field in object of class DADA::App::ScheduledTasks at /cgi-bin/dada//DADA/App.pm line 13507. [Mon Jul 25 14:35:01 2016] mail.cgi: (in cleanup) Can't access 'DESTROY' field in object of class DADA::App::ScheduledTasks at /cgi-bin/dada//DADA/App.pm line 13507.


Warm regards,

Mary Ann




On Jul 23, 2016, at 5:38 PM, Mary Ann Kelley[Dada Mail Developers] <dadadev@PROTECTED> wrote:

Yeah, I had just upgraded when new releases came out. I’m running 9.2.0 Stable on all 3 installs. Since I have to upgrade 3 installs I was waiting until it seemed like there was a good reason to upgrade. I will do so as soon as I can carve out the time (just returned from being out of the office for 3 weeks so I’m trying to get caught up) and send the steps and error log results.

The biggest problem with sending the steps is that I can’t even recreate my own problems on the site running on a different server - it’s only the installs on my LiquidWeb dedicated server that are doing it. :/

Warm regards,

Mary Ann


On Jul 22, 2016, at 5:33 PM, Justin J justin@PROTECTED [Dada Mail Developers] <dadadev@PROTECTED> wrote:


Mary, I'm not able to recreate your problems w/schedules not saving using the, "Save Schedule" button. Everything saves just fine. I'm wondering if you could try to list the steps used to recreate your problem, and do so in the simplest ways. That's pretty invaluable to me, when trying to work through a bug.

Also, you may want to start first with just upgrading to the latest version. I can tell you're not up to date, as this error (or type of error) 
  • This mailing list is a public mailing list - anyone may join or leave, at any time.
  • This mailing list is a group discussion list (unmoderated)
  • Start a new thread, email: dadadev@dadamailproject.com

This is the developer discussion mailing list for Dada Mail.

If you are just looking for support Dada Mail, consult the message boards at:

https://forum.dadamailproject.com

Documentation for Dada Mail:

https://dadamailproject.com/d

Specifically, see the Error FAQ:

https://dadamailproject.com/d/FAQ-errors.pod.html

To post to this list, send a message to:

mailto:dadadev@dadamailproject.com

All subscribers of this list may post to the list itself.

Topics that are welcome:

  • Constructive critiques on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
  • Bug/Error reports
  • Bug fixes
  • Request For Comments on any changes to the program
  • Help customizing Dada Mail for your own needs
  • Patches
  • Language Translations
  • Support Documentation/Doc editing, FAQ's, etc.
  • Discussion of any changes that you would like to be committed to the next version of Dada Mail -

Dada Mail is on Github:

https://github.com/justingit/dada-mail/

If you would like to fork, branch, send over PRs, open up issues, etc.

Privacy Policy:

This Privacy Policy is for this mailing list, and this mailing list only.

Email addresses collection through this mailing list are used explicitly to work within this email discussion list.

We only collect email addresses through our Closed-Loop Opt-In system.

We don't use your email address for any other purpose.

We won't be sharing your email address with any other entity.

Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.

All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.

All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.