When I try to make a session report from my campaign via the "write report" button in the session list, the newly created article immediately fails to save, giving a popup warning. It continues to fail unless I remove the link to the session in the dropdown at the top right of the page. Once that's removed, the page will save without issues, but if I click in that dropdown again to try to relink it, no sessions appear as options to link to. This issue has affected the last four sessions I've created. Sessions before that remain linked without apparent issues, but I'm afraid to mess with those links to test it. This has occurred on both Windows and Mac.
1. Make, play, and finish a new session in a campaign. 2. In the session list in the campaign page, hit "write report" for the new session. 3. The error should immediately pop up. Hit "okay". 4. Delete the link to the session in the dropdown at the top right of the page. 5. The page should now save. There will likely be two copies of the article in your article list, one created by the original "failure" to save and one the version that actually said it saved. 6. If you click in the session report's dropdown to relink the session, no sessions will appear as options.
Hey Evil Atlas, we have deployed a fix tha should resolve this issue and allow you to create session reports - can you please try again and let me know if this is now working as expected?
Hi katerinach, The main goal of the fix worked: Making new session reports does work properly, with the session automatically being linked in the corner with no breaking error. Thank you! I'm still unable to connect the old session reports to their sessions using that dropdown. When I click in the dropdown, no sessions show up, and searching by name doesn't make anything appear. I am able to link them if I switch to the legacy interface.
Hey, thanks for the confirmation and additional info! I have located the case that is probably causing this and will be releasing a fix for this very soon.
We have just made a release which includes a fix for this - please try again and let me know if it now works as expected or if there's still an issue!
It looks to be working perfectly now. Thank you!