Page 1 of 1

BUG: Resource Calendar CSV export

Posted: Wed Apr 15, 2009 4:30 pm
by atticusewig
I think I might have discovered a bug when
trying to export the CSV for a Resource calendar.

The error message both I and the stake admin get
when we click on the export to CSV link says that
we are not a member of the ward / stake.

The stake admin is still using his NetID account to
access LUWS, but I have already switched over
to the LDSAccount.

Has anyone else experienced this problem ?

Can someone from a different stake try to replicate
this problem to see if it is limited to our stake or is a
system-wide bug.

Thanks,
Atticus Ewig

Posted: Wed Apr 15, 2009 4:45 pm
by aebrown
atticusewig wrote:Can someone from a different stake try to replicate
this problem to see if it is limited to our stake or is a
system-wide bug.
I can confirm that I see the same thing for all three export options for my stake. I've never tried to export a resource calendar before, so I don't know if it is a new problem or a long-standing one.

Posted: Wed Apr 15, 2009 5:12 pm
by techgy
Alan_Brown wrote:I can confirm that I see the same thing for all three export options for my stake. I've never tried to export a resource calendar before, so I don't know if it is a new problem or a long-standing one.
Same thing here on all three export options. Like Alan, I've never tried to export a resource calendar either.

Same results here

Posted: Sat Apr 18, 2009 7:46 am
by AileneRHerrick
When I tried to export the resource calendar in any of the three formats, I was displayed a page that said, "You must be a member of this ward or stake to view this page." Same results as above!

Posted: Mon Apr 20, 2009 8:41 am
by ShirtsDre
AileneRHerrick wrote:When I tried to export the resource calendar in any of the three formats, I was displayed a page that said, "You must be a member of this ward or stake to view this page." Same results as above!
I will investigate and report back here.

Posted: Mon Apr 20, 2009 10:28 am
by ShirtsDre
BillyBoJimBob wrote:I will investigate and report back here.
Bug confirmed. I have logged this with Local Unit Support.