The developers agreed to take a closer look at this. The behaviour hasn't changed, and is consistent with what happens when editing posts in the backend, and so it's odd that you are the first person to raise it, but the behaviour isn't really what would be expected from a user perspective.
I'm always keen to testing everything, I need to make sure my site is idiot-proof, so I have to sometimes act as an idiot and do all the stupid things they would.
I don't see any progress in the internal ticket, so I've prompted the developers for an update about when an update can be expected. I'll let you know what they say.
I'm wondering something about Forms and Notifications. I understand that I can add a notification for the admin, user or both when the user fills in the form to create a new custom post.
Now let's say the admin creates the post in the back end, how does he add the notification aspect of it? For example, I create a listing in my site that needs to expire in 30 days and I need the notification to be sent to the user 5 days before expire, 3 days and 1 day, but I'm not using the form, I'm creating the custom post in the back end of wordpress. Is it possible?
That's not possible. The notifications are part of forms, and only apply to posts created using a front-end form.
If you examine wp_postmeta for posts created with a form that include post expiration and notifications you will see there are a number of hidden fields relating to this. I don't know whether you manually add such fields to a post created in the backend the notifications will work, it's not the expected or supported behaviour, but you could experiment with that. Be careful how the data is stored in serialized arrays.
Ok so the only work around would be to create a custom post with the front end form with my email, then in the back end change the email to the customer's email, correct?
Another question is, when the time of expiration come, and I extend it because the customer pays, does the notification work with the updated date?
And the notifications will work based upon whatever the currently stored expiration time is, so if you update the expiration time the notifications will work relative to that new time.
An update to Forms 2.5.1 this week together with the earlier update to Types means that the issue originally reported in this ticket should be resolved if you want to update and confirm that for yourself.
(You should also receive notice that the other issue you linked to is fixed in the same release.)
