Brining this back to the top - seems like this error is happening again, and is now impacting courses too. What seems to be occurring is the “purchase” widget on the catalog details page layout is not displaying. I have opened tickets with support, but this issue seems sporadic and we cannot pinpoint why or how this keeps happening. Does anyone else have this issue? Thanks!

Hi, 

We had an issue whereby the “Start | Enroll” button was disappearing on some of our courses and live events (VILT).  We have opened a support ticket with TI to investigate.  

To resolve, we noted that the enrollment start date is blank on the impacted events.  updating this to set a value resolves the issue. Is that the same as what you are seeing?

It is not possible for an admin to delete the enrollment start date manually so we’ve asked TI to investigate if something is happening in the backend.

Thanks,

Jeananne 

Hi Jeananne, that is super helpful. I remember this being the issue for us when we had this problem with ILTs/VILTs - thank you so much for refreshing my memory! I checked the course where the error is occurring and you are exactly correct - there is no start date for the enrollment. Of course, also as you mentioned, I tried to update it myself and it would not let me (so I see this is where the problem lies). But what is interesting… if I copy the course, the enrollment start date automatically populates and the course purchase/start button works on the copied version. 

I am just curious why some courses the enrollment date gets automatically set to the date you make the course, and while other times it does not. Seems like an issue on the TI side.. for now, I will tell my team to double and triple check that enrollment start date is populated before saving the course for the first time. 

Appreciate the help! Have a great day!

Kristin

I’ll share this update with our CSM also to see if it helps their analysis.

We’ve noted this for new content that was just created but also, we had one instance where >30 people registered to the event and then the button “disappeared” so you need to keep a close eye on this!

Great to know we aren’t alone with this issue….