-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Comments
Can you use |
Hi @estruyf , |
That should not be a problem, but to be sure, what does your log output say? Please verify by: |
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. Could you please suggest if we have any alternative for it. |
I had this issue too. |
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:
VS:
Page: It created one page called index.aspx, however given data is not coming up.
Desktop (please complete the following information):
Additional context
Its working fine when I'm creating a new project using doctor init and doing same steps.
The text was updated successfully, but these errors were encountered: