Skip to content
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

Changes not being sent to sharepoint #137

Open
1 task
SaintsMan76 opened this issue Feb 4, 2021 · 7 comments
Open
1 task

Changes not being sent to sharepoint #137

SaintsMan76 opened this issue Feb 4, 2021 · 7 comments
Assignees
Labels

Comments

@SaintsMan76
Copy link

SaintsMan76 commented Feb 4, 2021

Note: for support questions, please use stackoverflow and tag the post with #spgo.

  • I'm submitting a ...

    • [ *] bug report
    • feature request
  • What is the current behavior?
    I am trying to use the SPGO tool to backup a sharepoint site and move to a different tenant after a spliting off of a part of the company.

SPGO: Populate local workspace works but editing then saving or adding files are not saved to sharepoint. Tried with multiple sites and not working.

  • If the current behavior is a bug, please

    • Your spgo.json file (You may replace corporate PII with "xxx")
    • "sourceDirectory": "src",
      
      "sharePointSiteUrl": "https://axxxs.sharepoint.com/sites/Team2",
      "workspaceRoot": "c:\Users\xxx\Documents\SPGO\xxx",
      "publishWorkspaceOptions": {
      "destinationFolder": "/",
      "globPattern": "c:\Users\xxx\Documents\SPGO\xxx\src\\.",
      "localRoot": "c:\Users\xxx\Documents\SPGO\xxx\src"
      },
      "publishingScope": "SaveOnly",
      "authenticationType": "Digest",
      "remoteFolders": [
      "/SitePages/
      /",
      "/SiteAssets/**/
      ",
      "/_catalogs/wp/",
      "/_catalogs/master
      ]
      }
    • Steps to reproduce
      modify a file and save
      SPGO: Publish local workspace (enter credentials)
  • What is the expected behavior?
    Updates to be copied to share point and be visible in site pages.

  • Please tell us about your environment:

    • OS and Version Windows 10 20H2
    • SharePoint Location (Online vs. On Premise) Online (office 365)
    • Authentication Type (e.g. Digest, NTFS, ADFS) Digest (albe to populate local so know working)
@SaintsMan76
Copy link
Author

More behaviour is that the source file is checked out but is never updated or republished.

Opening the edited page shows the page open for editing but in original state.

No error in VSCode

@chrishasz
Copy link
Owner

Hello @SaintsMan76 - in your spgo.json file, what is the current value of the publishingScope property?

SPGo supports three 4 different values for this:

  1. None - No server changes when you save locally.
  2. SaveOnly - only attempts to save the file to the server, but does not check the file in or publish the file.
  3. Minor - Publishes a minor version of the file
  4. Major - Publishes a major version of the file

You can read more at the documentation page here

Finally, what happens when you manually publish a file by left-clicking the file and selecting the SPGO > Publish <Major|Minor> Version option?

@SaintsMan76
Copy link
Author

Hi Chris i found the issue.

I had to modify a setting on my sharepoint site
• Open Sharepoint online management shell
• Connect-SPOService -Url "https://xxx-admin.sharepoint.com" -Credential $userCredential
• Log in with user with sharepoint admin role should allow MFA support
• Run
o set-sposite "https://xxx.sharepoint.com/sites/MySite" -denyaddandcustomizepages $false

I was then able publish and update changes. Apologies but I couldn't find this in setup documentation.

@roschinsky
Copy link

Hey folks,

Had the same issue as @SaintsMan76 and was able to fix it by setting DenyAddAndCustomizePages to $false on the site in question.

@chrishasz
Copy link
Owner

chrishasz commented Mar 5, 2021

@roschinsky good catch! Thank you for posting this potential solution!

@SaintsMan76 - is your issue still resolved? I think it would be good for me to add a troubleshooting/faq page to the documentation for issues like this.

@roschinsky
Copy link

@chrishasz: actually @SaintsMan76 brought up that workaround. just wanted to confirm the approach. ;)

@chrishasz
Copy link
Owner

Ack! You are correct. So much for my morning reading comprehension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants