Skip to content

Error updating Navigation #39

Closed
Closed

Description

@P3N-101

Getting this error on both 1.4.0 and 1.5.0 beta

× Updating navigation
→ Error: 'https://tenant.sharepoint.com/sites/DocsTest' is not a valid SharePoint Online site URL
ERROR: Command failed: localm365 spo navigation node list --webUrl 'https://tenant.sharepoint.com/sites/DocsTest' --location TopNavigationBar -o json
Error: 'https://inspectplus.sharepoint.com/sites/DocsTest' is not a valid SharePoint Online site URL

Activity

  1. P3N-101 commented on Feb 4, 2021

    @P3N-101
    Author

    If I run the same command directly in the console, ie localm365 spo navigation node list --webUrl 'https://tenant.sharepoint.com/sites/DocsTest' --location TopNavigationBar -o json

    It works fine... and I get the json response

  2. estruyf commented on Feb 5, 2021

    @estruyf
    Owner

    What version do you have locally installed @P3N-101?

  3. estruyf commented on Feb 5, 2021

    @estruyf
    Owner

    Seems that this error is only returned in the CLI for Microsoft 365 on the SPO Command argument validation. The only thing I can think of is a difference in a local version.

  4. added a commit that references this issue on Feb 5, 2021
  5. estruyf commented on Feb 5, 2021

    @estruyf
    Owner

    Seems I found the issue. There was a single quote used in the URL and this causes issues on Windows. Released a new beta version. Feel free to give it a try.

  6. self-assigned this
    on Feb 5, 2021
  7. added this to the 1.5.0 milestone on Feb 5, 2021
  8. P3N-101 commented on Feb 5, 2021

    @P3N-101
    Author

    localm365 --version v3.6.0-beta.3066a8
    m365 --version v3.5.0

    It seems to be the Menu element of the Doctor.json file that causes the error, without that section it runs without error but still doesnt update the navigation.

    I was testing with a comms site thinking the TopNavigationBar was the correct element, nope it returns nothing but QuickLaunch does return so changed it to QuickLaunch but still the same error

  9. P3N-101 commented on Feb 5, 2021

    @P3N-101
    Author

    Just ran the new beta this is now fixed awesome thanks... I have another one to raise though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions