Hey there! I've got an issue with the signup form due to a custom addition on my end. To fix it, I disabled the signup route. If it is possible to add this as a setting to disable such route, or redirect it, would be awesome!

3 months later

@SychO idk if your aware but this blocks/makes the PWA addon act weird when force redirecting to login page this seems to be intermittent though given I could get it working on Edge(could be caching tbh) but not on brave browser no matter how i ran brave with or without cache logged in already vs logged out

6 days later

LostCat Did you find a solution? I have the same problem.
Thanks.

    6 days later

    @SychO I have the same problem as @cilia

    I'd need non-registered users to have access to a fof page. I set the route to exclude as "pages.page" and also tried with the full URL, but it didn't work.

    How the "Routes to Exclude" option works?

    Thank you!

    I can see that the div is .pages-page , but it still does not work.

    2 months later

    could you be so kind and provide a sample on how to exclude a route so that a page of the fof/pages extension is visible without redirection to the private facade? Thanks! 🙂

      GreXXL it should be pages.page. I'm planning on adding exclusions by url path, but probably not anytime soon.

          SychO thanks - if I enter pages.page to Routes to Exclude From Redirection to Login/Signup Page. - I still get redirected (also with cache cleared).

          Edit Thanks @SychO for the support - the correct value for anybody interested is: pages.page,page

            One thing I did notice when using this extension is that you get the following error in the console:
            Manifest: Line: 1, column: 1, Syntax error.

            I think it also has something to do with why I am not getting PWA to run on this installation - but I have to figure that out separately.

              9 days later

              SychO adding to the previously mentioned error, this extension is incompatible with ianm/twofactor - on login, it results in a JS error.

                  GreXXL it is incompatible with a lot of extensions that offer this type of guest interface. If you thr setting to force redirect is enabled. The extension assumes there is an intention to keep community content private. So it blocks off forum and api requests apart from auth.

                  I usually add the obvious routes from extensions that should be excluded (like fof oauth) but the user exclusions setting exists to allow further allowing by the admin.

                  I remember why the input for that accepts route names rather than a path. Paths do not differentiate between GET and POST and other types of requests. Whereas a route name is precise.

                  I wonder how difficult it would be to build a route selection component. That way options are visible.

                      SychO understood. But I think taking away the possibility to use 2FA authentication is kind of not ideal - especially if you want a closed/secure community. This is not a blocking issue for my use-case, but it would be nice to have. What is more annoying is the other error GreXXL, as it seems to make using PWA a problem.

                          a month later

                          tolgaaaltas no, it's off extiverse temporarily, will try to make it available again this weekend

                              Hi @SychO

                              I just want to ask if the flarum-private-facade will be available again this weekend? Thanks for the answer.

                              SychO will try to make it available again this weekend

                                Now Free

                                This extension is now Free, thank you to everyone who have purchased this before!

                                composer require sycho/flarum-private-facade:*

                                Additions

                                • URL path exclusions from force login redirect.

                                  Wadera you can exclude URLs, for example if you wanted to allow displaying tag pages, you would add /t/* (separate multiple exclusions with commas)