-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loading data via 'url' not working #316
Comments
Hello again, I found out that there are some js inclusion at the end of the page:
Those are missing when I remove the question marks from the url. After I added
in the jsp and overwrote the included jquery (old version 1.11.3 wtf), there are a few js inclusions in the renderer html (without question marks in url):
As you can see the (generated?) /myApp/dandelion-assets/bbf6b3372d2dcfbb8686fe17b33cdf91/js/dandelion-datatables-311a8e67d0b412ebcd1b6db403737fd0.js is missing. Thanks in advance |
Hi there, problem was about nested jsps and caching. Disabling caching in dandelion_prod.properties solved the problem. |
Hi there, disabling caching was actually no good solution. Client says that website is loading too slow now, so we have to enable caching again... |
would you happen to know a good alternative? since this project seems to be dead we would like to migrate to something that is under active development but haven't found something yet |
We are using https://datatables.net/ and a custom implementation now... |
aah shoot, hoped i could prevent having to do that, thanks anyway |
Hi,
our table remains empty when we try to load data via 'url' attribute. We tried absolute and relative urls.
Version:
Table:
Everything is fine when we are using 'data' attribute. Also it's working when we use 'url' attribute and add some question marks to the end of the url (in this case: "krankenkassen/list????"). I see that the method behind the rest interface is called twice then. Without question marks it's called once, but the table remains empty.
I think it's a bug, or does anyone have a hint how we could fix this?
The text was updated successfully, but these errors were encountered: