September 15, 2018 at 3:25 am #75181
Windows 10, 64bit / FileMaker 17 Pro Advanced / soSIMPLE 3.8 standalone
In the past we used FileMaker 14 and soSIMPLE 3.4. All was OK.
No we use FileMaker 17 and soSIMPLE 3.8.
When we start the calender programm, the webviewer ist “emty” – he doesn`t show anything.
When I click “Redraw” the webviewer shows “Die Webseite kann nicht angezeigt werden / The website couldn`t be shown”.
When we open “soSIMPLE Calendar Settings” and after that we click on “Redraw” than the calender ist showed correctly.
To click forward (one week) goes correctly.
To click back (to the last week): the calendar ist shown correctly, but after that, soSIMPLE calendar settings pops up shortly, after that the webviewer pops up (blank/empty). After that the calendar ist shown correctly again.
When I click on a event on calender for editing, ther is the same problem (pop up soSIMPLE calendar settings and webviewer) but I can`t edit the events.
When I want to create a new event (drag to create) FileMaker crashes completely.
We need the calendar daily, it is realy importent for us. We hope, anyone can help us.
September 18, 2018 at 1:09 pm #75182
September 18, 2018 at 3:23 pm #75183
We’ve integrated it in our own solution.
At first we’ve upgraded from a revision of soSIMPLE Calendar, but it did’t work.
After that we followed the video “Five Minute Integration”.
But there was the same problems.
September 19, 2018 at 8:45 am #75184
You might need to run through all the steps again with a fresh backup. Before you start:
– backup your file so you don’t lose anything
– delete all of the sosimple scripts (if you made modifications you’ll need to add them back in later)
– delete the web viewer on your calendar layout (otherwise the name of the calendar object will be “web calendar copy” instead of the expected name).
– Then walk through each step of the integration article for Standalone, making sure that the scripts are named properly (not “soSIMPLE 2”, for example), and that the export step references the correct data.json field.
Make sure you’re following the standalone integration article.
You must be logged in to reply to this topic.