Hi Akeeba Backup developer,
We are a company using the Dropbox Business solution. The last couple of months we have been in contact with the Dropbox developer team, because we experience an issue connecting to the "team folders" (blue) in the business solution. The problem is, that when trying to navigate to the dropbox root with all our folders, it goes directly into the "member folder" (purple).
After a long time corresponding back and forth with the Dropbox developers, they have admitted that they a able to reproduce the issue.
Dropbox said: "With the introduction of team member folders the effective directory root defaults to the members team folder and all relative paths now reference this root. To overcome this the developer needs to specify the 'Dropbox-API-Path-Root' header and reference the namespace of the teams root. This then sets the effective path to be the expected teams 'root' folder."
Later on they gave us this IMPORTANT information: "All 3rd party developers need to implement the 'Dropbox-API-Path-Root' header flag to allow access to the teams root folder. Without this flag the API will default to the members home folder and users cannot navigate up to the root namespace. The following guide shows the required header and its implementation - https://www.dropbox.com/developers/reference/namespace-guide "
We hope to hear from you soon, since this is a major problem for us and everyone else using your product with Dropbox Business.
Best regards
Danny Wisholm
We are a company using the Dropbox Business solution. The last couple of months we have been in contact with the Dropbox developer team, because we experience an issue connecting to the "team folders" (blue) in the business solution. The problem is, that when trying to navigate to the dropbox root with all our folders, it goes directly into the "member folder" (purple).
After a long time corresponding back and forth with the Dropbox developers, they have admitted that they a able to reproduce the issue.
Dropbox said: "With the introduction of team member folders the effective directory root defaults to the members team folder and all relative paths now reference this root. To overcome this the developer needs to specify the 'Dropbox-API-Path-Root' header and reference the namespace of the teams root. This then sets the effective path to be the expected teams 'root' folder."
Later on they gave us this IMPORTANT information: "All 3rd party developers need to implement the 'Dropbox-API-Path-Root' header flag to allow access to the teams root folder. Without this flag the API will default to the members home folder and users cannot navigate up to the root namespace. The following guide shows the required header and its implementation - https://www.dropbox.com/developers/reference/namespace-guide "
We hope to hear from you soon, since this is a major problem for us and everyone else using your product with Dropbox Business.
Best regards
Danny Wisholm
