Hi Ismail, what version of nuPickers are you using ?

Hi Ismail,

I think you need to whitelist your domain for client dependency

See this post for more information : https://our.umbraco.org/forum/umbraco-7/using-umbraco-7/61145-Packages-only-work-in-debug-mode?p=0#comment207470

Dave

Have you updated to latest versions of Client Dependency and NuPickers? That fixes it for me (non azure). 

@Hendy using 1.3.0

@Dave will take a look at that

@Dan if all else fails may try that.

Cheers

Ismail

Dave,

Whitelist is up to date so its not that. The latest version of clientdependancy is 1.8.3.1 which is what I am on.  I will look at updating nupickers but I dont think that is the issue as I have other property editors which are causing problems as well.

Regards

Ismail

Have you cleared the client dependency cache, forced a reload? Does it work in debug?

Dan,

Yup no joy, however it all works fine in debug. I am just building out an upgraded nupickers see what that does will report back shortly.

Regards

Ismail

What other packages are you using ? I've seen problems like this when a package uses embedded resources for js and css. And some I have seen that use a version querystring in the packagemanifest for the client side resources.

Dave

Hendy,

I upgraded to latest nupickers and that has fixed the issue just doing a bit more testing.

Regards

Ismail

Hi Guys,

I am having a similar client dependency problem. I inherited a site that was an upgrade of an old v4 site.

The upgraded v7 site had nupickers installed and everything worked fine. We then did some development on it and at some point the nupickers stopped working and began displaying behaviours similar to what is described in all the posts where people have problems with client dependancy.

From what I have read the best practice is to add in a whitelist of the domains into the client dependency. However I have tried this a few times and it never works. I am working on a local site and even if i turn debug to true in the web config i still get problems.

I noticed that the files that are 404ing have an extension of .nu on them which having looked into the source of the nupickers should get removed by the package.

I am really really confused by this and any light you could shed on this would be very welcome.

I am running nupickers 1.5.2 and Umbraco version 7.2.8 assembly: 1.0.5675.23466

Update If i turn debug to false. I dont get the 404 errors any more but i just get a bit 500 error for /umbraco/backoffice/nuPickers/XmlDataSourceApi/GetEditorDataItems

But i cant seem to get an error message.

L

Hi Lachlann,

I'm guessing you've tried all the usual things: deleting the Client Dependency files, clearing caches...

At a guess, can you identify any changes in web.config that might have an effect ?

Is there anything in the UmbracoTraceLog file about the 500 error ?

Thanks, Hendy

Hey Hendy, Thanks for the reply. I have tried all the usual things as you say.

I cant think of any changes in the web config that could affect it, But i will do a win merge comparison to find out exactly what has changed..

In the Umbraco Trace Log file the only error I get is:

ERROR Umbraco.Web.WebServices.ScheduledPublishController - [P20284/T1/D29] Error executing scheduled task System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) ---> System.ComponentModel.Win32Exception (0x80004005): The specified network name is no longer available

I don't think this could be related could it?

Perhaps the web config will shed some light. cheers L

Thanks for your response Hendy, embarrassingly enough for me this was traced back to a rogue poorly written URlRewrite rule.

L

Good to hear you've got it working :)

is working on a reply...