When I try save configuration with path:
sites/all/libraries/processing.js/processing-1.0.min.js
I get the following:
Could not verify the location of sites/all/libraries/processing.js/processing-1.1.0.min.js
and I am not able to save configuration.

Opposite to that I do can save any cofiguration without slashes characters e.g.
processing-1.1.0.min.jssssss
.

Comments

mradcliffe’s picture

Please check where you placed the processing-1.1.0.min.js file within your web server's web root path.

Anonymous’s picture

My location of processing-1.1.0.min.js is:
sites/all/libraries/processing.js/processing-1.1.0.min.js

Thanks for your reply.
I have the following message cannot save configuration:

Could not verify the location of sites/all/libraries/processing.js/processing-1.1.0.js
Processing.js Path:

Provide the relative path to processing.js that you downloaded from processingjs.org. This will usually be sites/all/libraries/processing.js/processing-VERSION.js

But I can save location like this:
processing-1.1.0.min.js
or everything else, even:
black-sheep
so it looks like adress verification issue.

mradcliffe’s picture

The module uses Drupal's standard file_check_location() function to make sure the file exists in the path that you specify. If it's throwing the error, then PHP cannot find the file in the directory specified.

I also notice that your error says "processing-1.1.0.js", but you say you are using "processing-1.1.0.min.js". Make sure that you have entered the relative path to "processing-1.1.0.min.js", not "processing-1.1.0.js" if that is in fact the processing library you're using.

Anonymous’s picture

Assigned: » Unassigned

Hi Matt
I had all kinds of processing.js in that directory so it was just my misspelling.
Thanks anyway.

I tried to figure out why file_check_location equals zero.
I looked inside file_check_location to see what's wrong.

I had symbolic link in my drupal installation directory - sites pointing to folder up
I that case the realpath of processing.js was
mysite.com/sites/all/libraries/processing.js/processing-VERSION.js
and drupal path was
mysite.com/public_html

Since file_check_location tries to match this two paths
if ($directory && strpos($source, $directory) !== 0)) // the $directory is realpath(''), and $source is realpath of processing.js
the function file_check_location returns 0.

I've moved my sites folder into drupal folder so realpath of processing.js became:
mysite.com/public_html/sites/all/libraries/processing.js/processing-VERSION.js
and all start working.
So this issue may be closed.

I only think about the symbolic link I used for sites. I never had any problem with sites til then.

mradcliffe’s picture

Status: Active » Closed (works as designed)

I actually ran into the issue you have with file_check_location() with imagecache. Drupal has a hard time with aliases because it uses the realpath() function or drupal_realpath() function.

niteshade’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Closed (works as designed) » Active

I'm having this problem as well.

getting this error: "Could not verify the location of sites/all/libraries/processing.js/processing-1.2.3.js"

even though, right below, it says "This will usually be sites/all/libraries/processing.js/processing-VERSION.js"

is this a bug, or am I doing something wrong? Is there an established workaround?

thanks

mradcliffe’s picture

Status: Active » Postponed (maintainer needs more info)

I guess the error message is confusing. It is just spitting the path that you entered in the form back out at you when Drupal says the file doesn't exist at that path. Can you double check the file name and try again?