Tech Forum

I am also experiencing this error. Will a notification be sent once it is fixed or do we just have to keep trying throughout the holidays?

Thanks!

jbb89777 wrote:I am also experiencing this error. Will a notification be sent once it is fixed or do we just have to keep trying throughout the holidays?

We'll send out a notification to the forum when the issue is fixed, for sure.

jhowell2000 wrote:I wanted to delete classes, then add events and recreate classes to have lessons schedule around events.

As a work-around, I'm creating new classes titled "2013 ..." after inputting conflicting event dates. If this issue isn't resolved by the beginning of the year I can simply inactivate all the 2012 classes.

preston.baxter wrote:As a work-around, I'm creating new classes titled "2013 ..." after inputting conflicting event dates. If this issue isn't resolved by the beginning of the year I can simply inactivate all the 2012 classes.

There seems to be a misperception that 2012 classes will roll into 2013. This will not happen. 2013 classes must be created. You can check this by navigating to January 06, 2013. If you have not created any classes there will not be any classes. There is no need to delete any 2012 classes.

The "cannot delete classes" issue arises when you realize after creating a class or two for 2013 that the lesson postponing feature has not been developed and you have to enter events for the year and now go back and create the classes again to have lessons postponed. The classes originally created will still be there. Just rename these unwanted classes something like Delete, Delete 1, and so on. Mark them as inactive, no check mark, and they will not be available. When the issue is fixed and deployed the unwanted classes can then be deleted.

If you are still seeing 2012 classes while trying to add 2013 classes you have forgotten to select 2013 in the year selector box. Since we are still in 2012 it defaults to the current year, 2012.

When 2013 is selected, all the "current" classes still appear. That was driving the "misperception" for me. Inactivating them and creating new ones for 2013 will work fine.

jdlessley wrote:

preston.baxter wrote:As a work-around, I'm creating new classes titled "2013 ..." after inputting conflicting event dates. If this issue isn't resolved by the beginning of the year I can simply inactivate all the 2012 classes.

There seems to be a misperception that 2012 classes will roll into 2013. This will not happen. 2013 classes must be created. You can check this by navigating to January 06, 2013. If you have not created any classes there will not be any classes.

That's not what I'm seeing. I'm the only one who has done anything with the lesson schedules in my ward. I created 2012 class but no 2013 class. It's true that the 2012 class did not transfer to 2013 but there is a set of default classes in 2013 which I did not created.

That's interesting. I didn't have any default classes in 2013. With the exception of the two classes the HP Group Leader tried to set up there was nothing else.

Looking more closely I guess the list of classes already in my 2013 admin matched what I found in the BETA list, except my test classes did not show up. Most of those matched the class names I was using for 2012 so I assumed they had "rolled over" when I now see a couple of classes in there that I was not using (Primary 1, 3, and 5 plus Temple Prep). Interesting, indeed.

preston.baxter wrote:Looking more closely I guess the list of classes already in my 2013 admin matched what I found in the BETA list, except my test classes did not show up. Most of those matched the class names I was using for 2012 so I assumed they had "rolled over" when I now see a couple of classes in there that I was not using (Primary 1, 3, and 5 plus Temple Prep). Interesting, indeed.

I had a similar experience... looked like I had some that were there by default and it occurred to me that they might have come from beta, but there were Primary classes in the list and I did not create any Primary ones in beta.
I don't think these rolled from beta at all. It really does appear that I had some there by "default". Which of course, leaves me with a list of classes to delete, but which cannot be deleted yet. I too went the route of renaming them with "to be deleted" and deactivated them.

Will someone please let us know when this problem is fixed?