Richard Arch Posted January 13, 2023 Share Posted January 13, 2023 I haven't noticed this before, is it expected that its logged as an error? Note: dd/mm/yy date format, the recent error occurred using v4.7.6. Link to comment Share on other sites More sharing options...
Daniel F Posted January 13, 2023 Share Posted January 13, 2023 2 minutes ago, Richard Arch said: I haven't noticed this before, is it expected that its logged as an error? Note: dd/mm/yy date format, the recent error occurred using v4.7.6. It depends on your configured logging error level. You can define it by clicking on the settings button at the top on this page. Link to comment Share on other sites More sharing options...
Richard Arch Posted January 13, 2023 Author Share Posted January 13, 2023 Ah Interesting, would it be expected at level 3? Link to comment Share on other sites More sharing options...
SeNioR- Posted January 13, 2023 Share Posted January 13, 2023 (edited) This level is the most recommended. Edited January 13, 2023 by SeNioR- Link to comment Share on other sites More sharing options...
Richard Arch Posted January 13, 2023 Author Share Posted January 13, 2023 hmm, logged in as that last member and this is what they see for that event. I wonder how they accessed a link to try to say they are going? Ahh... he was a Maybe before the event filled up. Link to comment Share on other sites More sharing options...
Jim M Posted January 13, 2023 Share Posted January 13, 2023 Did someone RSVP after they loaded the page but before they RSVP'ed? Plausible. Link to comment Share on other sites More sharing options...
Richard Arch Posted January 13, 2023 Author Share Posted January 13, 2023 Yes, that's possible. This member was a "Maybe" before he tried, I've add an event to play with on my local install but cant get the "Maybe" option. Has it been removed? Found the "Maybe" option, it appears when the event has no RSVP limit. Link to comment Share on other sites More sharing options...
Richard Arch Posted January 13, 2023 Author Share Posted January 13, 2023 Yes, its an error and could be a bug. Here are my steps to reporduce. Create an event with the RSVP set to unlimited (the default). Add Members, 1 as Going and 1 as Maybe. Edit the event, set the RSVP limit to 1. Now sign in as the Maybe member, this is what they see which allows them to click on going. Signing in as yet another member who has never responded to the event, this is what the "Maybe" member should have seen. The "Maybe" members should have been removed when the RSVP limit was reached, so that they couldn't press the Going button. I think this is a bug? Just to add, when the "Maybe" member presses that Going button the get the error message that is logged. Link to comment Share on other sites More sharing options...
Jim M Posted January 13, 2023 Share Posted January 13, 2023 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. Link to comment Share on other sites More sharing options...
Solution Marc Stridgen Posted March 10, 2023 Solution Share Posted March 10, 2023 Just a quick update to let you know that this issue was resolved in the recent 4.7.8 release of our platform. Please upgrade your site to resolve this issue. If you are still seeing any issues after upgrading to this version, please let us know. Richard Arch 1 Link to comment Share on other sites More sharing options...
Richard Arch Posted March 10, 2023 Author Share Posted March 10, 2023 Works like a charm. As a further test, reverting RSVP back to unlimited afterwards and the Maybe members reappear 👍 Marc Stridgen and Charles 2 Link to comment Share on other sites More sharing options...
Management Charles Posted March 10, 2023 Management Share Posted March 10, 2023 Thanks for confirming everything is working! Link to comment Share on other sites More sharing options...
Recommended Posts