1 of 1 people found this helpful
It's not a big ask IMHO; many of us have been saying this for many years: if you are going to do any kind of integration and web publishing, stick to safe naming conventions. a-z, A-Z and the underscore.
FM has been very lenient in this way for many years but it has made it a 'bad citizen' in the overall landscape and causes major headaches for integrations.
I can appreciate that regarding database names and variable names. Maybe even script names. But is it really true that many have been saying for years we should have no spaces in variable values?
I think there may be confusion with "variable values" and perhaps the documentation need changing/clarification.
Just keep in mind that an URL, passed however on the internet, but be encoded (most of the time).
If you are calling a page and passing parameters and values, then what you may type into a browser line (or via a form) will be "ok", but make no mistake, the browser is encoding for you before passing to the web server being called.
I wonder if the "variable values" is something being passed this way and causing the issue.
IDK, I'm just musing what needs to be clarified in the KB article 16449.
Yes all that makes sense regarding the URL. But if they are only talking about the URL, it should say that. And if they only meant the URL, why would that even be newly mentioned in the 16 release notes? So I don't think we can assume that.
'xactly! clarification on the documentation is needed.
3 of 3 people found this helpful
Sorry for any potential confusion that the wording of this item has caused. It simply means that when these elements (database names, script names, script parameters, variable names, & variable values) are used in a WebDirect URL, they must be encoded within the URL itself. They do not need to be made URL-safe within the schema of the database. I'll recommend this be potentially amended in future ReadMe's.
Same for this item from Linking to a database from an HTML page section of the FileMaker 16 WebDirect Guide: "If a database name, script name, script parameter, variable name, or variable value contains spaces or other special characters, replace the characters with the corresponding encoded values required for valid URLs. For example, replace a space character with %20."
Yay that's great news! I'm so happy to hear this, thank you.
Thank you for the clarification!
Sent from miPhone