The first step is to determine where to install the plugin.įor more information on the process, open the database with this fmp URL fmp:///AutoUpdate360WorksĪs long as your system meets the recommended minimum requirements set by FileMaker then you meet the requirements to use 360Works Plugins Follow the instructions below only if you choose not to use automatic installation for some reason. If you are running FileMaker Pro, then you will need to install the plugin for FileMaker Pro. If your database utilizes the "Perform Script on Server" script step to run scripts that call plugin functions (from FileMaker Pro, Data API, or Web Direct), or if you intend to use the plugin in a scheduled script, you will need to install the plugin for FileMaker Server If your database is hosted on FileMaker Server AND uses the "Perform Script on Server" to run scripts on the server that call plugin functions, then you will also need to install the plugin on the server. Leave this Finder(Mac) or File Explorer(Windows) window open If users will be accessing the database through Web Direct then the plugin needs to be installed into the FileMaker Server Web Publishing Engine.ģ60Works plugins cannot be installed on iOS, but you can install them on FileMaker Server and then use "Perform Script on Server" to run them. On Mac this is under the FileMaker Pro menu. This will open another Finder(Mac) or File Explorer(Windows) to the FileMaker Pro installation location Step 4: In the Preferences window, click on the plugin tab and then click on the button that says "Reveal plug-in folder". Step 5: On the window from Step 1 navigate into the folder that corresponds with your operating system. If you are using a Mac go into the "MAC" folder, a Windows go into the "WIN" folder.įor Mac: Copy/paste or drag/drop the. But once it's working, it works - at least that's my experience.Fmplugin file that is inside the MAC folder into the folder that was opened in Step 4įor Windows: There will be two files inside the WIN folder. The only solution I know of is restarting things. Getting the "host's capacity" message is something that has happened to me when installing plugins some times. You'll then want to restart the database server and possibly the script engine. Now scan the listings to make sure everything is fmserver:fmsadminįor any you find which are not set with the fmserver owner and fmsadmin group then you'll needed to change them with chmod (run 'man chmod' for more info) Within the Terminal you would check this by using the following commands (this is for Mac - Windows would be different)Ĭd /Library/FileMaker\ Server/Database\ Server/Extensions You may not be able to update it if it isn't owned by the fmserver:fmsadmin user and group. You mention the plugin was "installed manually" and if it was copied then you need to check the permissions and ownership on it. FileMaker Server is probably very permissions sensitive - as is the case with most daemons. I have come across similar issues and I don't know what the reproducible steps are. This video provides all the critical know-how in order to start working with PSoS and it will get you going fast! You can update hundreds of thousands of records with lightning speed or generate a hundred page report as a PDF within minutes instead of hours. You can send hundreds of thousands of emails without ever seeing a spinning waiting indicator. With PSoS, you can import hundreds of thousands of records in mere seconds. If your solutions are stuck in versions prior to 13, then you might want to beg, borrow or steal (ok, not steal) to start using this feature. Changing the way you think about FileMaker development, using PSoS for short, is inevitable. Until you start using it, it "seems" like it's just "another feature". This is essentially what this new script step does, but with all the power of what FileMaker can do. Your client, a web browser, makes a request to some beefy server and it wrangles the data and then reports back with the compiled results. This is fundamentally why the web is so popular. There's so much power in how it can be used, that it truly is a game changer. Yes, I said that with all caps! This is exciting! Perform Script on Server is the one step which will change how you develop FileMaker solutions FOREVER.
0 Comments
Leave a Reply. |