ParamQuery grid support forum
General Category => Help for ParamQuery Pro => Topic started by: Webauthor on March 20, 2016, 07:31:08 am
-
Hi, I'm getting the following error when I switch to version 3.3.0.
pqgrid.min.js:297 Uncaught TypeError: b.cGroupView is not a constructor
The same code works on version 3.2.0
Any ideas what could be causing this?ß
-
Row Grouping is changed in 3.3.0 and is not fully backward compatible.
Please read through the upgrade guide for 3.3.0 and share a small test case if the error is not resolved.
-
We're not setting the group model, which is why this is strange.
See these two URLs showing examples:
3.2.0
https://csc.webauthor.com/go/test-grid.cfm?version=3.2.0
3.3.0
https://csc.webauthor.com/go/test-grid.cfm?version=3.3.0
-
I could see the error on your url but am unable to check what's causing the error.
Please share an isolated test case in jsfiddle.
http://jsfiddle.net/6h47hL9n/
-
Found the issue. One of our script libraries used $ as a function, that was different than jQuery. Looks like the new update doesn't make it safe to use $ for other functions like it did before.
-
New issue. Do you have an example that uses remote data and sets grouping after initialization? I'm not able to get this to work.
-
Remote data is used in both these demos:
http://paramquery.com/pro/demos/group_rows
http://paramquery.com/pro/demos/group_remote
groupModel: { on: false } can be set initially ( use Edit and Run button ) and when Toggle grouping button is pressed, it sets groupModel.on = true after initialization.
-
Excellent. That works great. Only thing I see is that the grouping only shows the number of rows summarized locally. How can we get the summary number to reflect the full remote count?
-
Didn't get your complete question but in case of paged data ( with either local or remote paging ), grouping and summary takes place only for current page.
-
Got it. Thanks so much.
-
Curious about the status of the original problem mentioned in this post (the cGroupView is not a constructor script error). Is there a fix planned or a workaround? I'm trying to evaluate ParamQuery for use at my company and this script error is blocking me.
Thanks!
-
With v3.3.0, the workaround is not to overwrite $ variable. You might have some scripts which use and modify $ variable.
It has been fixed in the upcoming version, so that it won't be an issue to use $.
-
Thanks for the prompt reply. Unfortunately, there are no scripts overwriting $ in my application. I even wrote a quick test file with nothing but jQuery, jQuery UI, ParamQuery Pro 3.3.0, and a constructor for a table. Even with just this I was able to reproduce this issue. I also tried running jQuery in no conflict mode, but that just broke ParamQuery entirely (which is it's own problem - we need to use no conflict mode, but that's another issue).
Is there a way I could get a build of 3.2.0 for evaluation?
Thanks!
-
Please check the demo: http://paramquery.com/pro/demos/group_rows
and jsfiddle which I created to double check: http://jsfiddle.net/xdmf56Lv/
I don't see the mentioned issue.
-
Ok, it looks like some of the scripts weren't loading before it tried to execute the constructor. Odd, but fair enough. I've got it working now using jQuery(document).ready(). Thanks for the example.
-
This issue has been fixed in v3.3.1