Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Have 7.x-2.0 installed - upload of 7.x-2.3 does not register and change version from out of date status as "available updates"
Commented out project in info file so it would not continue to display the out of date error, but unlike any other Drupal module - it continues to display the out of date error
Is something special needed to be done
Comments
Comment #2
bobburns CreditAttribution: bobburns commentedComment #3
tstoecklerNo, there is nothing special that needs to be done.
Please make sure that you have removed the module completely and then uploaded the new version successfully so that all the files are where they should be. If that is the case, the version should be showing up correctly.
Comment #4
bobburns CreditAttribution: bobburns commentedYes I did that - and even on a new installation of drupal 7.52 - uninstalled it reported version 7.x-2.0 before install and after. If I uninstalled it after disabling the module and removed it from the system and then upload the dev version and install it - it still reported version 7.x-2.0
Also I could not find it in the system table in the "l" section - I found only sites/all/modules/libraries/tests/modules/libraries_test_module/libraries_test_module.module
So I dumped the system table as an sql file and searched it and found it in sites/all/modules/contrib/libraries/
All the documentation I see says at https://www.drupal.org/docs/7/modules/libraries-api/the-ideas-and-design...
The best practice is to place libraries into a sites/all/libraries directory. All possible locations are:
sites
Similar to how core module and themes are in a top-level modules resp. themes directory. To be used for distributions, who want to make the libraries available for all sites and all profiles.
profiles/$profilename/libraries
Similar to profile-specific modules and themes, libraries can also be profile-specific.
sites/all/libraries
To be used for multi-site installations, if a library is to be available to all sites. This is the default location that should be used in most cases.
sites/$sitename/libraries
In multi-site installations for libraries that are site-specific.
Is this a left over from version 2.0 or how did this happen because I did not intentionally do it
sites/all/modules/contrib/libraries/ is not among the suitable location and there was no libraries report showing up
( I also had and still have the same issue with ctools - needing to move it and it does not move well - see https://www.drupal.org/node/1221048 )
I moved the folder with WinSCP, cleared the caches, visited the modules page to rebuild the system table - and THEN the libraries report showed up and it all worked
Comment #5
tstoecklerAhh I'm glad that it worked in the end.
Note that I think you are confusing the place to put the Libraries API *module* and the *libraries* itself. In any case, glad that it worked.
Comment #6
bobburns CreditAttribution: bobburns commentedNo, not confusing the two - and i have a bucket load of libraries. the Libraries API *module* was found in sites/all/modules/contrib/libraries/ - and i never put it there - which was the only module there and which is of course now a completely deleted folder after the move
Comment #7
bobburns CreditAttribution: bobburns commented