Why are entities saved in config ?

Agree, report data should not be stored in configuration, as on each deployment it will be reset.

I've had a stab at moving this data to be stored in state data instead, including having an update hook to migrate this data.

I'll try running this on a few different sites shortly, if there are any issues I'll update the patch accordingly.

@thomwilhelm,

Your patch doesn't apply cleanly against 2.x. I'm not sure, but you may have made the patch against 8.x-1.x?

In any case, I took my best attempt at merging what you had with what I had come up with before I found this issue. I added a configuration schema to square things away a bit too.

Care to give it a try? I used a different key name than you did when I initially did my changes. Let me know if it looks like I missed anything you had implemented.

@thomwilhelm,

I think your patch contained parts of 🐛 update report data permission not working Fixed .

Rerolled with what was in 2.x

Hey @generalredneck just gave PR 17 a test and all worked nicely for me, thanks for rerolling, apologies for including those lines from the other ticket.

No problem. When I get a chance I'll get it merged in.

I'd love to get this merged and deployed as soon as it's reasonable. Without this patch, this module has the risk to white screen on different environments that share config but may have a different database (e.g. local vs dev vs prod)

Automatically closed - issue fixed for 2 weeks with no activity.