Wiki inaccessible (1 Viewer)

[High_Five]

This is a well-organized and important collection! I had a problem where the Extensions plugin offered on the MP plugin download page no longer worked with MP 1.38 (x86), but after some searching, I found the updated plugin at [WiP] - 5154: MediaPortal 1 - x64 - SharpDX!
It would certainly be easier for all users to always have easy access to all updated plugins. That’s why, in my opinion, it would be worth considering making these plugins available primarily through the official download page as well!

 

[ajs]

That’s why, in my opinion, it would be worth considering making these plugins available primarily through the official download page as well!

All plugins are available through the MPE Installer, which is included with MediaPortal. Just launch it, select a plugin, and install it.

 

[High_Five]

Do you mean the MediaPortal Extension Manager? For me, it shows a maximum version of 1.2.2.199 for the Extension plugin in MP (x86)!

 

[ajs]

For me, it shows a maximum version of 1.2.2.199 for the Extension plugin in MP (x86)!

If I update the links (I don't remember the exact name of the menu option), does there still not be an update? I need to check, but I think I already updated the link. And if it's installed, it shows the installed version.

 

[ajs]

For me, it shows a maximum version of 1.2.2.199 for the Extension plugin in MP (x86)!

There were no changes there; all those plugins were simply recompiled to support x64, and only a couple of them were updated, but they're all available in MPE.

 

[ajs]

For me, it shows a maximum version of 1.2.2.199 for the Extension plugin

 

[high]

Can we export the content in some format (such as Markdown)?
We could try migrating to GitHub Pages...
Like this: Mediaportal Plugin Team

our wiki is pretty huge and highly customized, many content went trough at least 3 imports to different wiki software over the years. You would need to manually edit/update/clean every single subpage from Atlassian macros aso before exporting it to markdown.
I'm still working from time to time on a move to Confluence Cloud some day but even thats a true nightmare to port.

 

[ajs]

I saw some scripts on GitHub that upload Markdown automatically, either via an API or through direct access. Maybe it's worth a try.

 

[high]

I saw some scripts on GitHub that upload Markdown automatically, either via an API or through direct access. Maybe it's worth a try.

that's not the tricky part. But having thousands of pages mixed between html, editor language and Atlassian macros to generate a specific layout. The markdown you upload will not work as before. Neither will attachments nor any link to the sub pages nor page restrictions nor users. Technically you need to touch every single page manually.

 

[ajs]

that's not the tricky part.

Here's what I found off the top of my head. But then again, we can always give it a try—if it doesn't work out, it doesn't work out. And we can always fix what we have.
The main thing is not to publish any sensitive information.

GitHub - Spenhouet/confluence-markdown-exporter: Export Atlassian Confluence pages as markdown files.

Export Atlassian Confluence pages as markdown files. - Spenhouet/confluence-markdown-exporter

github.com

pip install confluence-markdown-exporter

Markdown Exporter for Confluence | Atlassian Marketplace

Export Confluence pages to Markdown. Export single pages or bulk export full page hierarchy with child pages, images & attachments

marketplace.atlassian.com

Easy Markdown Exporter for Confluence | Atlassian Marketplace

Easily export Confluence pages or entire spaces to clean Markdown with preserved hierarchy, images, and attachments

marketplace.atlassian.com