Closed RCheesley closed 1 year ago
Hello, Thanks for raising a support ticket as well, that was helpful for our internal-work ;)
We have fixed the issues, dues to a misconfiguration decidim->etherpad. The API_ETHERPAD_VERSION was wrong (1.9.1
instead of 1
).
Now the https://community.mautic.org/assemblies/community-team/f/5/meetings/26 display the pad in read-only
mode correctly.
I've also check if this correction fixed by any luck the related issue raised here: https://github.com/mautic/Community-Portal/issues/15. But it does not, and the routing fix we have to forbid pad creation needs to stay.
Thanks
I think this will also close this issue: https://github.com/mautic/Community-Portal/issues/13 ?
https://community.mautic.org/assemblies/community-team/f/5/meetings/27 this one is still throwing an error.
https://community.mautic.org/assemblies/community-team/f/5/meetings/1 this one too.
https://community.mautic.org/assemblies/mautic-meetups/f/28/meetings/29 this one too.
@froger seems to still be a problem.
Could the alternative option to having the pads domain offline be to implement Auth0 login (or maybe just admin only login for the Etherpad instance rather than preventing people accessing the instance directly? Just a thought if the 404 redirect/access protection is the culprit for this error.
The new events are now saving fine, so closing this one.
I noticed today that all past events are throwing a server error when I was doing a demo video.
I thought initially maybe this was because the event had not been closed but I went to close the event and it still as throwing an error.
Here's the example:
https://community.mautic.org/assemblies/community-team/f/5/meetings/26