- 07 Feb 2023
- 2 Minuten te lezen
Troubleshooting - Managing content
- Bijgewerkt op 07 Feb 2023
- 2 Minuten te lezen
1. PDF preview grayed out
PDF previews of files would be grayed out in some articles. This issue can be observed in the Chrome browser when the width of the PDF is higher than 700.
Change the width of the PDF to less than or equal to 700
Markdown - In the editor, change the width of the respective PDF file in the Markdown syntax
- In the editor, click Code view and find the width of the respective PDF file
- Update the width. Press 'Ctrl/Cmd + S'
2. Discussion icon is disabled
When you don't have permission to view Discussion, it will be grayed out and cannot be accessed. To confirm this:
- Click Profile image at the bottom left → View access permissions → Content role. Expand the Categories & Articles section
- Under Article, check whether Post comments in discussion permission is available
- If you don't have this permission, contact your project owner
For project owner:
To update the content role of a team account:
- Go to Settings → Users & Security → Team accounts & groups → Team account
- Hover the mouse pointer over the desired team account, and the Edit (pencil) icon appears on the right
- Click Edit → Manage content roles & permissions, and the Content access blade appears
- Update the content access
- Click Save
3. 404 error appears for folder category redirection
The redirect rule will be added with no errors when you add a redirect rule with a folder category slug as the destination path. But when you try to hit the article URL, it results in a 404 page. This error is because the folder type category does not have a valid slug to preview.
Change the category type to Index.
- Hover your mouse pointer over the desired category in the category manager
- You can find the ••• (More) option adjacent to the category name
- Click ••• (More) → Change category type
- Select the Index category type and click Update
4. Error: The given source is already part of an existing destination
The source URL of a redirect rule cannot be the destination URL of any redirect rule. Cyclic redirection is currently not applicable in Document360.
To overcome this error, update the current destination URL with a new destination URL.
For example, the current redirect rule has the source path as slug-A and the destination path as slug-B. You want to redirect slug-B to slug-C.
- Replace the current destination URL as slug-C. So the current redirect rule would have the source path as slug-A and the destination path as slug-C
- Create a new direct rule with the source path as slug-B and the destination path as slug-C
- Now, both slug-A and slug-B are redirected to slug-C
5. Error: Your browser does not support PDF
In the Knowledge base site, the PDF document embedded in an article is not rendered, and the following message appears instead of the PDF document: "Your browser does not support PDF.click here to download"
This error is a browser-specific one that occurs in Chrome due to the PDF documents setting.
- Open Chrome on your device
- Click the '⋮' icon at the top right next to your avatar icon
- Click Settings in the menu
- Click Privacy and security in the left menu bar
- Click Site settings
- Scroll down to Additional content settings and select PDF documents
- Select the Open PDFs in Chrome checkbox
- Refresh the article in the Knowledge base site. The PDF document should now be visible
For further assistance, please get in touch with our support team at firstname.lastname@example.org