Just to verify, I cannot use $Cache:variable inside my own module’s functions. Is that correct?
Instead, I must find a way to bring the data I want to cache into the pages ps1’s.
I have no idea why the cache isn’t working that foreach-object parallel but here’s a workaround. It accesses the cache directly and bypasses the provider.
This still would not work with the stepper. testing with the bare bones example worked, however. I am just going to remove the stepper (which is fine) and start over from scratch my entire site with 3.6.2 as AT&T won’t open port 445 and I am still seeing table layout anomalies ( and I cant seem to comment out themes without error - I am not sure what files are native and what I copied from cl’s repo prior to being officially incorporated into PSU). Either way, this gives me an opportunity to start fresh - I just need to verify the instructions to use for the Git SQL integration.
gives me the following errors (and dash doesn’t auto start - I can manually start it) when I push a commit:
Is the ForEach-Object -Parallel issue for $Session: (and $Cache:) planned for the next release? IIRC, since $Cache: is system wide, this band-aid works for only one user. After that, the variables begin stepping on each other any time another user uses the dashboard.