You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been brought up a couple times and our implementations tend to utilize the use_only_x_path quite a bit and when a page is published it prompts the login overlay within the CMS.
We're reviewing how the code acts with use_only_x_path enabled from a session perspective, mainly surrounding the use of Directory::test() however we have not identified the core issue. Not implementing the `use_only_x_path config option results in normal CMS activity.
The text was updated successfully, but these errors were encountered:
I came across this comment silverstripe/silverstripe-sharedraftcontent#153 (comment) when looking at an unrelated issue and thought it may have some insight into how the session could be invalidated causing the user to have to re-auth.
It would be nice to solve the issue with Director::test(), but in the meantime would it be feasible to replace the line $output[] = Director::test($searchLink);
with a different method.
This module does things a little differently. Looks like it creates a separate session and just renders the page with $page->forTemplate() https://github.com/wilr/silverstripe-algolia/blob/main/src/Service/AlgoliaPageCrawler.php
This issue has been brought up a couple times and our implementations tend to utilize the
use_only_x_path
quite a bit and when a page is published it prompts the login overlay within the CMS.We're reviewing how the code acts with
use_only_x_path
enabled from a session perspective, mainly surrounding the use ofDirectory::test()
however we have not identified the core issue. Not implementing the `use_only_x_path config option results in normal CMS activity.The text was updated successfully, but these errors were encountered: