Scheduler values are auto populating on content submission

Hi sudhanjs,

You said "In one of my other instance i am not getting this same issue even the scheduler configurations in both instance are same." so this shows me that your problem is a normal support request, not a critical bug.

Looking at the screenshot you gave, I can see that both of the times are identical, and this is probably the current time when you tried to save. This could be because the wrong widget has got set for the two Scheduler date fields. This can happen if the module is uninstalled and re-installed. For background see

• #2652036: Field widget set incorrectly after Scheduler module re-install →
• #2848213: Give warning when wrong datetime field widget is set →

It is not possible to fix automatically, but you should get a warning that the wrong widget it set, see attached screenshots. Then visit admin/structure/types/manage/{type}/form-display to fix it.

Hi Jonathan,

Thank you for response !
I have attached the widget we are using as an option for scheduler in one of our content where we are facing the issue. It is not standard Datatime Timestamp but Datetime Timestamp for Scheduler.
We are not getting any warnings as well regarding wrong Widget selection. Infact we have not done any reinstallation of the scheduler module recently.
Is there any other point where we need to debug more or any other custom code that can impact the default behavior of this module? Because like i mentioned the issue appears whenever we are not filling the mandatory field in node for the first time and Hit submit and again refill/select the mandate field and submit again. The mandatory fields here are List/Reference/Media field, We are not getting the error for the same with text field / text area.

Thanks again.!

It would have been a simple solution if your site did have the wrong widget. But I suppose it is good that that is correct.

Is there any other point where we need to debug more or any other custom code that can impact the default behavior of this module?

If you can replicate the problem in a test environment, not production, then one approach could be to disable each of the other module one at a time and see which one finally removes the problem.

Another thing toi try is add in debug to write a stack trace to try to see what other functions are being called after you click 'submit'.