Compatibility:
SharePoint 2010 Foundation (SPF) and Server (SPS) Windows SharePoint Services (WSS) 3.0 Microsoft Office SharePoint Server (MOSS) 2007
SPF/SPS 2010 • WSS 3.0 • MOSS 2007
User Voices
(Loading...)

FilterZen: Feedback Forum > Version 3.8 gives a Invalid procedure call or argument jQuery.js

Hello,

After upgrading to version 3.8 we get the following error. Also in one filter web part one of the filter control fields is not rendered.
Please advise.

Kind regards,
Mario

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; Tablet PC 2.0; InfoPath.3; .NET4.0C)
Timestamp: Wed, 11 Aug 2010 19:26:28 UTC


Message: Invalid procedure call or argument
Line: 48
Char: 227
Code: 0
URI: https://pietersenbloklands.on-l-i-n-e.com/_layouts/roxority_FilterZen/jQuery.js

August 12, 2010 at 3:31 | Unregistered CommenterMario

Hello,

Just hold on. It appears we have to look for it on our side.

Kind regards,
Mario

August 12, 2010 at 3:47 | Unregistered CommenterMario

OK... BTW when in doubt, always try clearing your IE caches after an upgrade, specifically because our JS script files also get cached client-side.

August 12, 2010 at 3:59 | Registered CommenterROXORITY

Hello,

We also call a Jquery.js file when loading the pages. So it appears the code is conflicting.
We have to figure out how to overcome this issue. Or make sure we use the same versions.

Kind Regards,
Mario

August 12, 2010 at 4:49 | Unregistered CommenterMario

FilterZen always uses the newest (1.4.2 right now) but even so duplicate jQuery loads sometimes CAN mess things up, even though it was designed not to. If you're loading by yourself jQuery on each and every page that also contains a FilterZen you can simply disable its jQuery loading, either on a per-Web Part basis (see Misc section) or on the Site Collection or Farm level via Site Settings / FilterZen / Configuration.

August 12, 2010 at 4:53 | Registered CommenterROXORITY

Hello,

We use the same version as you do 1.4.2
Can you tell us if you used another version in the 3.6 release?
Because we did not have this issue in the 3.6 release.

Kind regards,
Mario

August 12, 2010 at 7:32 | Unregistered CommenterMario

This problem has now been resolved in release 3.8.0.2.

August 12, 2010 at 7:52 | Registered Commenterгoхoгiтч