Thanks for reaching out. I’d be happy to help.

The fact that the links are already used means that there’s a email security system that’s installed on the recipient’s email. Such security systems open emails and click on the links to ensure that they’re safe, which registers the magic links as used.

We have a solution for this, and I’ve enabled it on your project. After clicking the link from the email, the user must click a button on the page to gain access, this action registers the magic link as used. No action is needed from your side.

Regarding the delay, the email security system must also be responsible, as it opens all the links and waits for page content to load. Our system sends emails instantly; they should arrive in the inbox within seconds.

Let me know if you have any other questions!

I am an admin for my companies api docs and when I try to access the public docs that are managed by a list of emails that get magic links I am finding two issues.

1. It takes about 3-5 mins to get the email.
2. When you click the link it says the magic link has already been used.

Can you please assist with a way to fix this issue?

Thanks for your suggestion. Unfortunately, it’s not possibly to do that since we sync from DeveloperHub to GitHub when a page is published, not on every draft edit. Thus, when the the page is published and is updated on GitHub, there could many commit messages and many different editors.

Apologies about that!

• The author could be listed in the changeset (at least the name or email)
• The description that we are asked for when we are saving our changes to the page

Unfortunately not, we only provide the editor within DeveloperHub website.

path items, path operations and many other feature can not autocompletion.

Do you have VSCode extention or desktop editor?

Thanks for trying the API editor. We support autocomplete for component names. What other code autocompletion features do you wish to have?

But this editor don’t support code autocomplete, how to solve?

Do you have developed a editor for desktop that support code autocomplete?

Indeed the size of the PDF is big since we do not compress the PDF or modify the quality at all - to keep your images (specially screenshots) readable.

I’ve tried compressing a PDF generated by DeveloperHub using online compressors and other tools, at normal compression, and I’ve seen 70% reduction in file size - however many screenshots were no longer legible. Image quality really deteriorated.

We’ve implemented now light compression, which barely reduces image quality. The reduction in size could be somewhere between 30% to 60% in our tests, but keeps the images readable.

We’ve implemented automatic measures to ensure no PDF gets stuck again while building.

Thanks for reporting this!

The issue has been resolved. It was a technical glitch. The PDF is rebuilding at this moment.

Thank you for reporting this - we’ll be working on eliminating such glitches.

Today, the PDF export has been running for 1 hour. It usually takes 30-40mins. Please help check and resolve this situation.

Link: https://app.developerhub.io/metadefender-core/v5.14.2/installation/metadefender-core-documentation

Thanks,
Dung H. Nguyen

I’ve just tried again, but it seems the cache has not been cleared yet.
Furthermore, it failed to generate.

Could you please add me to the loop? I’d like to follow up in that thread so that I can export new PDF soon. We have a high priority document submission today.

Thank you.

Thanks for reporting this. A fix has been released just now, but since your docs are cached on your side - it might take a while for the effects to show. I’ve sent a colleague of yours a request to clear the cache.

I’ll keep you updated.

Thank you!

As the title, there’re many duplicate pages and sections in PDF generated today; for example, chapters “MetaDefender Core Documentation” and “Recommended System Configuration”.

Furthermore, the PDF of MD Core v5.14.2 also includes pages from newer version (v5.16.0).

https://app.developerhub.io/metadefender-core/v5.14.2/

We’ve also encountered the same issues in MD Kiosk documents.

Please check and fix soon.

Thanks.

I can see that you’re on the Original UI which is our previous UI. We’ve added Next UI in 2023 which gets first all the updates and bug fixes.

I’ve tested it and it seems that moving categories has a bug on the Original UI. At the moment you’re able to move categories by:

1. Switching temporarily to Next UI (you don’t need to save the setting, it would just appear momentarily in the editor).
2. Moving the category.

I’ll have it tasked for moving the categories to be fixed for Original UI, but in the meantime you can use the temporary solution above or upgrade to the Next UI.

I’ve already taken the freedom of moving Use Cases category below Getting Started.

Let me know if you’re able to move categories as needed using the solutions above. Thanks for your understanding!

For example, we are trying to move our Use Cases category from the bottom of the navigation bar to nearer the top, after Getting Started.

https://app.developerhub.io/trustx/preview/trust/Welcome

Attempting to move it will result in the error showing.

Thank you again!

Thank you for your quick reply. Unfortunately I still seem to have the same issues when I try to move a category to a new position in the navigation bar. I get a “fail to move category” response.

I can see the image on that page fine on both my phone and laptop on different networks.

Can you please try to load this page on another device, or on another network?

Otherwise, please capture a HAR file so I can investigate further.

not showing images when published:
https://docs.adara.com/managed-media/image-pixel-implementation-guide

I’ll check with our internal teams on whether we can update to the latest version in the meantime.

I’d be happy to help.

We do not serve the images from the editor vs reader side any differently. They’re served directly from AWS CDN.

Can you please send me a reader link(s) where this is happening?

If it is intermittent, do you mind following the steps here to capture a HAR file which can help us understand the issue? Please send the exported HAR file to [email protected].

Kindly note that your organisation is using a a very old version of DeveloperHub from 2022. We’d highly recommend that you move to the latest version to get latest updates and fixes. Please see the instructions here and here.

Waiting for your reply,

Thanks.

Apologies about that. Can you please try again now? It seems the index went out of sync - I’ve just refreshed it for you.

Please let me know if this ever happens again.

I hope you are all keeping well.

I am experiencing difficulties while reordering categories and documents contained within. For example, when I click and drag a category to a different position in the navigation bar, I receive the following error and the category is not relocated as expected:

This also seems to be the case when moving documents from one category to another.

Thank you!

Welcome to the community forum.

I understand that using underscores in text is confusing. This is because the markdown notation for italic is surrounding text by underscores.

On DeveloperHub, any text that contains underscores should be placed in inline code, since anyway it usually is not “usual text”.

For example, if the text was “hello_beautiful_world”, to write that with markdown enabled:

1. Write hello_beautiful
2. Highlight hello_beautiful and set it as inline code
3. Continue typing inside the inline code “_world”.

Similarily, you can do it by:

1. Write `hello_beautiful`. This will create inline code automatically.
2. Move cursor inside the inline code, and continue typing “_world”.

If markdown was disabled from account settings as you mentioned, you can do it directly by typing:
`hello_beautiful_world`

Note that if you do not enclose the text within inline code, upon saving and refreshing the page, it will still render italicised regardless if you have disabled instant markdown rendering or not - because eventually, underscores denote italics unless it is inside inline code.

Let me know if you need further help.

Apologies for the late reply.

You can now hide the AI search by applying the following Custom HEAD tag:

<script>
  window.settings.apply({
    search: {
      hideAiSearch: true,
    }
  });
</script>

From the docs.

Apologies! The issue is fixed now. The scrollbar should show up again.

However, when we turn it off, the vector store is also deleted, so we can no longer use it.

Can you please make it possible to keep the vector store around (and automatically update it when changes are published) without enabling the AI search front-end experience?