When you are logged into the plugin_target file with privileges that allow you to run scripts, the script that runs from the source file will successfully execute the target_script in the target file.
BASEELEMENTS ERRORS FILEMAKER FULL
And the target file requires a Full Access privilege to use references to it, as you will see in the screenshot below. There is no file reference between them and no prior authorization granted in the target file’s File Access section. Here is the scenario: you have two files that unrelated in any way. It works without requiring prior authorization between the two files.
They can do that without requiring a file reference from the source file to the target file. This is a risk to your solution, considering these plugins can do that from one file and target another file. We will use these two in our examples below. Some popular plugins with this capability are the free BaseElements plugin and the commercial MBS plugin, but there are many others. Plugins can trigger s cripts and use SQL queries to retrieve, add, and modify data. What Kind of Calls Are We Talking About Here? This change in behavior introduced with this feature fits with the overall security approach of disallowing actions until you explicitly allow them. The fmplugin feature helps protect your solutions from exposure to plugins making unwanted calls to your files. And it is an important security feature, so we wanted to make it gets a bit more coverage. In December 2020, FileMaker Pro 19.1.2 introduced a new feature that has not seen a lot of attention, judging by the lack of conversation and content.
0 kommentar(er)
