Do you see a GET hitting your service for view.js? Is it sending a 304 or a 200? Are you on Premise and your CDN caching?
There is no view.js in this example. I'm using jive-sdk create tile-app-simple to create the tile.
I also removed the below line from definition.json, so that it fetches the html from the nodejs server.
Per what I see in the tile content is loaded as an iframe using the src URL: http://<nodejs server>/mycustomviewtile/view.html?features=responsive,tile&ts=1489975184205&syn_app=rm025&ref_rm025=tileInstance:7157
So, updates done to the view.html on the server should reflect in the tile upon jive page refresh, right?
Are you on Premise and your CDN caching?
Yes, I'm testing on an on-prem instance, but there is no CDN caching.
Any further hints on this?
1 person found this helpful
I was able to work around this using ajax to update the html elements after load.
2 people found this helpful
To loop back on this thread.
Tile assets, specifically the HTML, are cached heavily. In our Node SDK, you will see how we add cache busting timestamps into the generated definition.json to insure that Tiles in newly installed add-ons refresh older versions.
Your workaround to use AJAX is appropriate. As a tip, I try to get the HTML DOM skeleton locked as much as possible prior to my first deploy and externalize my JS/CSS into pre-linked external files. This way you can update/iterate on the fly as needed.