-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Populate workspace stopped working #112
Comments
I am experiencing the same issue. |
Thank you for bringing this to my attention. I will take a look this week and get you a response soon. Also- I appreciate you posting your SPGo.json file, it is helpful. |
Hey Everyone- I am able to replicate this issue. I will have a fix out to the marketplace in the next day or so. |
@billr-stcu, @yanivoh - I have found and fixed a bug with file parsing, but I had a separate question about the glob pattern you are using in the Are you looking to download all files within the specified folder? If so, the correct glob pattern would be I will publish the fix to the marketplace soon, but you may want to try the above as a workaround until then. |
I have been using |
@billr-stcu the That said, I was still not handling the Thank you for catching this! |
Thanks you for your quick turn on this. |
(Belated) Thanks @billr-stcu! I will close this issue now. |
Hi,
Populate workspace stopped working for me few weeks a go.
Configure workspace works and creates SPGo.json file, but the populate workspace doesn't do anything.
Tried on multiple sites and document libraries.
This is my SPGo.json file:
{
"sourceDirectory": "src",
"sharePointSiteUrl": "https://sampletenant.sharepoint.com/doccenter",
"publishingScope": "SaveOnly",
"authenticationType": "Digest",
"remoteFolders":
[
"CustomScripts/**/."
]
}
Output says:
[7.4.2020, 16:06:20] ================================ ERROR ================================
[7.4.2020, 16:06:20] Cannot read property 'toString' of undefined
[7.4.2020, 16:06:20] Error Detail:
[7.4.2020, 16:06:20] ----------------------
[7.4.2020, 16:06:20] {}
[7.4.2020, 16:06:20] ===============================================================================
The text was updated successfully, but these errors were encountered: