Skip to content
This repository was archived by the owner on Feb 2, 2025. It is now read-only.

Version 1.5.7 of Angular Breaks Datatables #781

Closed
martinkoslof opened this issue Jun 28, 2016 · 5 comments
Closed

Version 1.5.7 of Angular Breaks Datatables #781

martinkoslof opened this issue Jun 28, 2016 · 5 comments

Comments

@martinkoslof
Copy link

martinkoslof commented Jun 28, 2016

I updated my applications to version 1.5.7 of AngularJs today and DataTables no longer works. After rolling back to version 1.4.8 of AngularJS everything works properly. I am using the newest distribution version of Datatables and Datatables Bootstrap integration (0.5.5). I am also using version 1.10.9 of the JQuery Datatables plugin and JQuery 1.11.1.

@martinkoslof
Copy link
Author

As a follow up, if helpful, starting with version 1.5.1 of Angular I have this problem. Upgrading 1.4.8 to 1.5.0 works. Beyond this, all future versions break Datatables

@l-lin
Copy link
Owner

l-lin commented Jul 4, 2016

I upgraded the vendors versions in the documentation and I can't reproduce the issue.

@martinkoslof
Copy link
Author

martinkoslof commented Jul 5, 2016

Well, it still isn't working for me :). I will try to create a plunkr or something of the like if I get a free moment. I have mimicked the entire example, even upgrading to JQuery 2.2.4 which I know isn't a part of the problem. If I use the 0.5.5 dataTables release with anything above Angular 1.50 it does not work:

Expected expression in form of "item in collection[ track by id]" but got "{0}". at Object.render

@martinkoslof
Copy link
Author

OK, well this is my problem as well:

#746

For whatever reason, it didn't show itself until I upgraded beyond Angular 1.5 and used Datatables minified releases 0.5.5. Everything works if I comment out my debuginfo line:

//$compileProvider.debugInfoEnabled(false);

You should be able to easily reproduce this now. All my Angular applications have this set as false, so in order to use the newest vendor versions and Datatables I need to remove this which I don't want to do.

Thanks

@l-lin
Copy link
Owner

l-lin commented Jul 5, 2016

Ok, thank you. Closing this issue as it's a duplicate of #746.

@l-lin l-lin closed this as completed Jul 5, 2016
@l-lin l-lin added the duplicate label Jul 5, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants