Hi
To update modules you must follow the procedure described here: https://drupal-tools.web.cern.ch/update-modules-webdav
Then if you have still problems, do not hesitate to come back and post in Drupal community.
Thanks
regards
Almudena
If you rely on community contributed modules, you need to find an updated and compatible release through https://www.drupal.org/project/project_module. You can download an appropriate release, unzip it, and otherwise paste it in the correct folder to overwrite the current installation. We appreciate that this is a rather cumbersome approach to updating modules: We are keenly aware of this and are looking into ways in which we can ease this process substantially.
Please let us know if you face any problems doing the above.
Hello,
I followed the instructions on updating the modules “the new way”, but got stuck at the last step, i.e. I am not able to upload the unzipped folder to the current installation. I am accessing the webdav via a browser, and drag and drop doesn’t work. Please see my screenshot:
The web interface does not allow you to upload entire folders. If you are on MacOS or Windows, we recommend using and connecting through CyberDuck (on Windows specifically, you can also just use the built-in Explorer), see more information here: https://drupal-tools.web.cern.ch/access-webdav-in-openshift-macos. If you are working on Linux, have a look at Nautilus instead.
Thanks for the tips. I used CyberDuck to update 4 modules (entity print, swift mailer, pdf generator and date popup). There was no window asking me to confirm the overwrite since the modules folders have different titles, I guess. Please see the screenshot.
When I go back to the website, I still see these modules requiring update (both under the Extend-update tab and under Upgrade reports). Is this normal?
The main reason of my attempt to update these modules is that the entity print module stopped working properly after the migration (the generated pdf stopped rendering the content, and remains blank).
The reason why you are not prompted to do an overwrite is because you are moving a module (folder) with a different name; e.g. pdf_generator and pdf_generator-2.0.1. When you download and unzip the modules from https://drupal.org/, you get a folder with the machine name of that module. In the above example, that would be pdf_generator. Inside that folder would then be the code for the corresponding version, in this case 2.0.1.
As such, I suggest you go ahead and remove the new modules you have uploaded (as these are essentially new modules!), ensure you download and unzip the correct versions and then otherwise check the name of the folders match the machine name such that you can actually overwrite.