The Issue (3008) is about broken module updates in environments with a symlink as doc root.
Our problem is, that we can not reproduce the test failures outside Zen.CI, but the same failures always happen inside. And they might be related to the code change.
As long as we can't reproduce it, we can't fix it - so we're stuck.
The bugfix would be important to make Backdrop usable in more hosting environments. Symlinks as document root aren't so uncommon.
I thought it might be the branch, but I tried creating a new branch from scratch and opening a new pull request, and it has the same problem, an Internal Server Error and then the test failures. This is PR 3682.
The bugfix would be important to make Backdrop usable in more hosting environments. Symlinks as document root aren't so uncommon.
I second that. Two common German webhosting providers (1&1 Ionos, and Strato) use symlinks as document root. Which means, you can't update modules, themes, or core via the Backdrop interface. In my case, about 3 out of 10 clients have a contract with one of these providers.
This may not fall under the topic of "dev", but it warrants discussion. Backdropcms.org is infested with spam accounts (spot-checking suggests that the vast majority of the 7K+ user accounts are spam). We need to take more aggressive steps to prevent them.
Hi @ian
If you go on the admin bar to Configuration > Development > Configuration manager > Single Import/Export > Import
Then paste in this:
{
"_config_name": "views.view....
Posted1 hour 7 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Update - this is a long-standing issue in the Drupal realm, with extensive discussion:
https://drupal.stackexchange.com/questions/257926/enable-sftp-for-upgrades
The upshot is...
Posted1 hour 53 min ago by Graham Leach (Graham Leach) on:
I'm currently porting +50K of lines (many custom modules) written for Drupal v7.x to Backdrop 1.x.
In the code I made use of the progress bar as documented here .
I finally found the...
If an insecure configuration is required for the Update manager to work properly, it should clearly state that. IMHO it should either (A) Work or (B) Refuse to proceed if the setup is not...
Posted2 hours 7 min ago by Graham Leach (Graham Leach) on:
Comments
Hi,
this week I'd like to ask for help re a pull request stuck in Zen.CI failures.
The Issue (3008) is about broken module updates in environments with a symlink as doc root.
Our problem is, that we can not reproduce the test failures outside Zen.CI, but the same failures always happen inside. And they might be related to the code change.
As long as we can't reproduce it, we can't fix it - so we're stuck.
The bugfix would be important to make Backdrop usable in more hosting environments. Symlinks as document root aren't so uncommon.
I thought it might be the branch, but I tried creating a new branch from scratch and opening a new pull request, and it has the same problem, an Internal Server Error and then the test failures. This is PR 3682.
I second that. Two common German webhosting providers (1&1 Ionos, and Strato) use symlinks as document root. Which means, you can't update modules, themes, or core via the Backdrop interface. In my case, about 3 out of 10 clients have a contract with one of these providers.
This may not fall under the topic of "dev", but it warrants discussion. Backdropcms.org is infested with spam accounts (spot-checking suggests that the vast majority of the 7K+ user accounts are spam). We need to take more aggressive steps to prevent them.
See this Zulip discussion and this issue.