Change the directory names from 'js_libraries' to 'libraries'

hey skilip? You've marked this as fixed. Does this mean we'll have to rename the directory when the next dev is out? Or if we already have a 'libraries' directory, then should we move all contents of 'js_libraries' to 'libraries'?

If yes, can you please add a warning or something in the site status report to remind us upon upgrade to new version once changes are committed? Thanx in advance.

Thank you for the update skilip and sorry for the late reply.

Your move is a nice step, but it only helps those that will visit the module's page and actually take a look at the warning. How about the people that simply see there is a new version of the module from their site's 'available updates' page and download it from the link provided there?

I think that the module should check for the existence of the js_libraries folder and if that returns true, it would inform the site admin. There are two cases here:

1. People already have both a 'libraries' as well as a 'js_libraries' folder. The warning should in this case be something like 'Releases of jQuery Plugin Handler higher than version 6.x-2.0 now use 'libraries' instead of 'js_libraries' for directories! Please copy your jQuery plugins from the 'js_libraries' directory to your 'libraries' directory. Once you do that, please remove your 'js_libraries' directory and this warning will go away.'

2. People have their 'js_libraries' folder, but no 'libraries'. In this case the warning should be 'Releases of jQuery Plugin Handler higher than version 6.x-2.0 now use 'libraries' instead of 'js_libraries' for directories! Please rename your 'js_libraries' directory to 'libraries' and this warning will go away.'.

That was what I had in mind.

I hate saying 'I told you so!', but... told you so!...

#729640: upgrading to latest version requires a complete uninstall to accept the update

Ignored it back then and now it came back to bite us :)

If ../sites/all/libraries isn't there but ../sites/all/js_libraries is (say after an upgrade from a version that required ../sites/all/js_libraries), how about gracefully falling back to ../sites/all/js_libraries and simply throwing a warning to the admin and in the site's Status report?

The warning should be something like:

[If Libraries API is installed and a ../sites/all/libraries directory already exists]

jQuery Plugin Handler now uses the ../sites/all/libraries directory instead of ../sites/all/js_libraries. Please move all libraries to the ../sites/all/libraries directory. For more information:
#522218: Change the directory names from 'js_libraries' to 'libraries'

[If Libraries API is not installed and there is no ../sites/all/libraries directory]

jQuery Plugin Handler now uses a ../sites/all/libraries directory instead of ../sites/all/js_libraries. Please rename the ../sites/all/js_libraries directory to ../sites/all/libraries. For more information:
#522218: Change the directory names from 'js_libraries' to 'libraries'
Libraries API

It shouldn't use the 'libraries' directory if it is not using Libraries API.

I think it's a good practice for every module to start moving 3rd party libs to ../sites/all/libraries anyways.

I see no harm in moving them out of the modules' folders. If Library API happens to be already installed or planned to be installed at some later point, then that would be a +. I don't thing that Library API should be a requirement though for that process though.