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

[BUG] Data is not coming in the pages after running doctor publish command #102

Open
pk091990 opened this issue Apr 2, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@pk091990
Copy link

pk091990 commented Apr 2, 2021

Describe the bug
Data is not coming up in the published pages after running doctor publish command. No error shown in the command prompt.

To Reproduce
1: Run doctor init in my existing documentation repository.
2: It creates one index.md file inside existing src folder and doctor.json file.
3: Update doctor.json url field with newly created communication site url.
4: Run doctor publish with 1.7.0 and 1.11.0 version.
5: Pages have been published with proper navigation structure. However data is not coming up in index.aspx.

Expected behavior
Data should come in .aspx as given in .md file

Screenshots
CMD:
image

VS:
image
image

Page: It created one page called index.aspx, however given data is not coming up.
image

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows
  • Version [e.g. 22] 1.11.0 and 1.7.0

Additional context
Its working fine when I'm creating a new project using doctor init and doing same steps.

@pk091990 pk091990 added the bug Something isn't working label Apr 2, 2021
@estruyf
Copy link
Owner

estruyf commented Apr 3, 2021

Can you use --debug flag and verify the output? That way you should see a bit more details about what it does during the publishing process.

@pk091990
Copy link
Author

pk091990 commented Apr 5, 2021

Hi @estruyf ,
Thank you ! I believe its not publishing the content when my folder exist after 3rd level i.e. C:\Folder1\Folder2\Repo in my local drive. its working fine if my repo exists till 3rd level folder structure i.e. C:\Folder1\Repo.
Same issue is occurring If I'm creating a new project using doctor init after 3rd level folder in my local drive. Is it supposed to work like that only ?

@estruyf
Copy link
Owner

estruyf commented Apr 7, 2021

That should not be a problem, but to be sure, what does your log output say? Please verify by: doctor publish --debug > output.log.

@pk091990
Copy link
Author

Hi @estruyf .. I've tried it out today and it works. Not sure what was the issue though !

However I've another query related to certificate based authentication. We are planning to create pages on one of the sites where we don't have tenant level access and the team which managed it will definitely not give Sites.FullControl.All application permission to our app. Password method is also failing and device code will not work as we are publishing pages using build pipeline.
So for certificate authentication , I was trying with Microsoft Graph Site Collection level permission (Sites.Selected) which has been recently introduced . Its authenticating but failing while processing .md files.

image

Could you please suggest if we have any alternative for it.

@ghost
Copy link

ghost commented Nov 29, 2022

I had this issue too.
When copying the folder content to a new directory it worked again.
It looked like the doctor publish command was also trying to do things with stuff from my other test folders when --debug was on...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants