Voting starts in March for the Drupal Association Board election.
Using FTP or SSH to install modules in Drupal 8 is broken. It is trying to change immutable config and the form throws an EnforcedResponseException that is not handled as expected by authorize.php.
This is a critical bug because installing modules is one of the first tasks new users want to do. Whilst experience Drupal user or web developers are unlikely to use this method to install modules other types of users are and it is completely broken.
Stop saving transfer details in system.authorize config. These settings should not be deployed between environments and these details will be remembered by a user's browser - storing them in Drupal is wrong really.
Fix authorize.php to handed EnforcedResponseExceptions.
Add tests so we don't break this ever again.
User interface changes
Data model changes
system.authorize config is meaningless. Filedto remove it in 8.2.x.
The original bug this issue was meant to solve has moved to...
I'm testing the latest HEAD on a Ubuntu server, and I've tried installing Views by pasting the url into the update manager.
After I input my ftp info (which btw, it doesn't ask for in my Windows install?), it downloads the file, but fails in the end with the message:
# Failed: Error installing / updating
# Failed: File Transfer failed, reason: Cannot create directory /home/bojan/public_html/drupal/sites/all/modules/views
The modules/ dir is chmoded 777. The owner is my user, "bojan".
What could be the problem? Might be good to have a note in the documentation...
NOTE: A very similar problem can be caused by a host configuration error on your file permissions and/or ownership. However, in rare circumstances, it can also happen when all the permissions and ownership appear to be correct. The root cause of this bug has not been found.
If you are having this problem, please read through this issue and fix any permission/ownership issues you find. If that doesn't fix the problem, then report any troubleshooting information you have. Don't bother to report that fixing permission problems solved the issue for you.