Neriderc
commented
5 months ago I haven't managed to reproduce this, these settings work fine for me. I updated my production site and went straight to that setting and it's working fine. I had a look back through the code changes and there's nothing major that could cause this (no database or browser storage changes), so I'm not sure what the issue could be.
Since you mention deleting the setup data, I presume this means you aren't able to trigger the issue again? It would have been helpful to know the error in the browser console.
I'll leave this open in the hope someone else has the same issue. If you're reading this and you have had this issue, before re-installing could you try the following things:
First, right click on the page and choose "Inspect", then in the panel that opens, choose "Console". Look for anything in red, and reply here with the error message it shows (a screen shot would be great). Note that not all errors come from GVExport (often they are from browser plugins), but it's a good starting point.
Additionally, if refreshing the page doesn't resolve the issue, it would be good to know if Shift+Refresh helps, or if opening in a private window helps (called InPrivate in Edge, Incognito in Chrome, Private window in Firefox - accessed from the menu at the top right of the browser with three dots or lines). These things are all subtly different and help to narrow down the source of the problem.
marwelin
Overall, GVExport 2.1.20 works smotth together with webtrees 2.1.19, except of this issue I noticed.