Trc4 I don't think Firefox should be blocking iframes unless your site has a Content Security Policy header that disallows it or the iframe points to an insecure page (http from https). I'm sure there's other scenarios (such as the destination site itself disallowing embed) but it is likely different depending on what you're trying to use an iframe for.

HendyTurtle Looks like someone above recommended using an iframe with a JS tag inside srcdoc. Not sure if that'll work.

A more reliable version that wouldn't need iframes would be custom web components (though this is way more complex). Creating a web component in a script tag in head and then using it in the fof page so that it calls that original code, for example. This would make sure the code always runs as intended, no matter how the page loaded.

      2 months later

      I've been using Fof pages to add new pages but I can't find a way to show the pages on the forum for users.

        Merged 1 post from Fof pages.
        16 days later

        This plugin creates abnormal spaces between paragraphs, headings, lists, in short, between everything. Especially when you want to write in markdown.

        We create most of the legal pages of our site with this plugin and I definitely demand that this plugin be given importance. At least it should provide more correct text formatting (nonsense gaps) or move the editor used when opening a topic here.

        Please confirm this thought of mine.

          7 days later

          Umutcan This plugin creates abnormal spaces between paragraphs, headings, lists, in short, between everything. Especially when you want to write in markdown.

          Was afaik discussed here and in this Github issue.

          You also liked the workaround. I think, the current behavior of the extension with the huge spaces is wrong too. But in the Github issue the valid point was raised, that a "fix" would most likely affect existing pages.

              wolfman I think it's wrong to solve it with CSS without taking any action yet. I think the Flarum team should take action on this issue, I'm very sorry that a software that attaches great importance to its interface design hasn't addressed such an issue for 2 years.

                a month later

                Please make an update where the "Hero" the page title area can be hidden
                like it is when setting a page as homepage

                a month later

                Is it possible to use plugin to create a drop down menu of pages? like in this forum under the "Legal" drop down above?

                  I have them both, can you give me hint how to put inside menu subitem?

                  • abg

                    • Post #486
                    • Edited

                    Good extension. There is one downside. Interline. How do you write e.g. privacy policy and regulations so that it looks nice and does not have line spacing? I have it beautifully done in txt and docx, but when I paste it, it looks terrible.

                    SOLVED

                    12 days later

                    Whose idea was it to make the URI paths /p/{id}-{slug} instead of just /p/{id}/{slug} so very annoying, I could create a slug driver for discussions to change this structure but this add-on is not as adjustable

                      aaron-tundrapeaksstudios I agree that FoF Pages should support custom sluggers like users and discussions. The reason this is not currently part of the extension is probably because this extension was originally created prior to sluggers being added to the Flarum API, and nobody has added them afterwards.

                      Looking at the source code, it seems like the extension might support accessing pages through /p/{slug}, if this works this should give you cleaner URLs without needing to change anything else.

                      Unfortunately, even if the extension implemented the slugger API, /p/{id}/{slug} would simply not be possible, because a slug cannot contain /.

                      The only way to add an additional slash in the URL would be to use the PHP and javascript extension API and change the route definition in both the backend and frontend.