Graham Leach: Has anyone got any experience with the assets in this area of Backdrop CMS?
filetransfer.inc
ftp.inc
local.inc
ssh.inc
If you do, I'd love to chat with you...
Graham Leach: It all starts here:
/core/includes/filetransfer/filetransfer.inc
<?php
/**
* @file
* Base FileTransfer class.
*
* Classes extending this class perform file operations on directories not
* writable by the webserver. To achieve this, the class should connect back
* to the server using some backend (for example FTP or SSH). To keep security,
* the password should always be asked from the user and never stored. For
* safety, all methods operate only inside a "jail", by default the Backdrop
* root.
*/
Graham Leach: How I would approach this challenge:
A) A reference base system should be selected (my preference is Ubuntu, due to market share)
B) The system should be described as a whole, explaining the relationship(s) between its constituent parts
C) A series of visual aids should be developed to support the explanation, to help people who think visually
D) A workflow (step-by-step) should be developed to describe how the system dynamically unfolds
E) A HOWTO discussing the installation and configuration of supporting (FTP and SSH) sub-systems need to offered
F) A HOWTO regarding firewall settings need to be offered
G) A discussion and HOWTO regarding User and Group Ownership & Permissions need to be offered
H) Multi-channel demonstrations of use (Narrative, Screenshots, Video) should be developed
I) A place where people may go for additional information or help should be offered
With the above in place (pre-conditions for success) the system should be achievable.
https://www.drupal.org/project/views/issues/1266388 shows that this is an architectural issue, and requires another 2 hooks being adjusted.
It would be really nice to add comments/notes to...
Hmmm, from D7 ancient tomes:
from https://drupal.stackexchange.com/questions/7056/limit-which-roles-can-view-a-node-basing-on-its-content-type
yet https://docs.backdropcms.org/api/...
I also note on this screen:
"Furthermore note that content which is not published is treated in a different way by Backdrop: it can be viewed only by its author or users with the...
I am seeing via dpm debug that the nodes that are authored by someone else are not even being interrogated at the view level; they are simply avoiding the hook_node_access call.
Yet the...
One suggestion would be to "fail early". It looks like if the user does not have the organisation field set, none of the other code matters.
if ($role == "organisation") {
$u = user_load($...
Comments
Graham Leach: Has anyone got any experience with the assets in this area of Backdrop CMS?
If you do, I'd love to chat with you...
Graham Leach: It all starts here:
/core/includes/filetransfer/filetransfer.inc
Graham Leach: How I would approach this challenge:
A) A reference base system should be selected (my preference is Ubuntu, due to market share)
B) The system should be described as a whole, explaining the relationship(s) between its constituent parts
C) A series of visual aids should be developed to support the explanation, to help people who think visually
D) A workflow (step-by-step) should be developed to describe how the system dynamically unfolds
E) A HOWTO discussing the installation and configuration of supporting (FTP and SSH) sub-systems need to offered
F) A HOWTO regarding firewall settings need to be offered
G) A discussion and HOWTO regarding User and Group Ownership & Permissions need to be offered
H) Multi-channel demonstrations of use (Narrative, Screenshots, Video) should be developed
I) A place where people may go for additional information or help should be offered
With the above in place (pre-conditions for success) the system should be achievable.