• Content not permitted (‘’). gets displayed (using version 1.2)

    By Andrew Magerman 2 decades ago

    the perils of beta versions - I have signed the version (btw you could also update the template name in the database properties.)



    I'll just wait until the official release and stop bugging you.



    Laters,

    Andrew

    • No, that's fine

      By Benedict R Poole 2 decades ago

      Any more detail? i.e. what did you do to see this issue, just so I can ensure I fix it!

      • By Andrew Magerman 2 decades ago

        have a try on:



        Edit a document, enter any content, save, and a white page with that error message gets displayed.

        I downloaded version 1.2 as an ntf, changed the design properties of the productive database to accept the ntf as a mummy, did a design update, and run the agent "migrate from 1.1". Could it be an extra configuration document?





        have a try on:

        http://www.magerman.com/A55BAE/FamilyWiki.nsf/



        Cheers,

        Andrew

        • Weird

          By Benedict R Poole 2 decades ago

          That's not a known DominoWiki error… I notice your Domino server is using "!" rather than "?" in the URLs it generates, but that shouldn't cause a problem. My one thought was that this had something to do with the spam protection I've built into 1.2, but I don't use that text in any of the error messages, and the error message would be styled in any case.



          It looks like the Domino server is configured to reject the content being sent to it, but I can't tell you more than that at the moment – do your logs shed any light?

          • sorry, I have not access to the server logs...

            By Andrew Magerman 2 decades ago
            • By Luis C Contreras 2 decades ago

              I had same issue and resolved it by putting:



              191.3.3

              85.255.117



              in the Banned IP Addresses



              and



              LotusDomino

              SpamTest

              TestSpam



              in the Banned Page Titles.



              Not sure which fixed this, but it works now without that Content error.



              Luis

              Luis@goAzTech.com