yeah, ok so here’s some info
if i do
<CoverPath>./toolspath/paketti_cover.png</CoverPath>
it gives an error saying didn’t find it.
if i have it without the ./ then it just uploads but without an error - and doesn’t update the cover.
i could remove the CoverPath and just put cover.png in there. that’s fine too. i’ll try it.
btw!
when linking to a specific tool, the title says “Home | Renoise” - any chance it could say something like <toolname> | Tools | Renoise ?
ok. i opened the same path on safari and it showed the cover. i don’t know if it’s specifically now from cover_paketti.png or cover.png, i’ll give it a shot later with the thumbnail too. is the thumbnail just called thumbnail.png ? 
Yeah, I couldn’t reproduce the path issue, so I think the image does upload, but your browser is showing the cached version, we’ll have to fix this as well.
The images are expected to be called cover.png and thumbnail.png and at the root, but if you have the <Cover/ThumbnailPath> fields present you can change that.
Yes, I’ll do that!
New webpage looks nicely minimalistic! I like it.
Only problem is that a lot of detail tool descriptions seem to be gone, I guess nobody will understand my tools now (including me). Sadly I also didn’t save the description locally. Login to tools section doesn’t seem to work currently.
For example here, EQ Helper actually is quite complex in some regards:
https://www.renoise.com/tools/eq-helper
This text might read better by also mentioning VST3:
Plugin Support
Plugins provide you with a vast array of effects and synths. With Renoise, all of that is within reach. Renoise supports VST, AU, LADSPA and DSSI.
Hmm, I’m sorry, I tried migrating all tool descriptions by converting the html to markdown, but this was done in a semi-automated fashion, it seems to me that here the description was taken from the manifest inside the tool.
You can of course update your tool once you log in, what is going wrong with the login for you? I found that the “missing nonce” error goes away on second try, or that the error is shown but you are logged in behind it, still looking to fix this but I haven’t been able to even reproduce it lately.
You can find the old tool pages still
I found the issue with the readmes, let me try fixing it.
Oh nice, thanks! Login works now.
Should be fixed now, with all the previous readmes restored (except for tools which contain README.md files, as those take precedence, or those that have been changed since we deployed the new site).
Note, the html to markdown conversion could have resulted in some things not translating well or being dropped, so it would be best if devs could verify their tools and fix mistakes or unintented formatting here. For the most part though, it should be fine.
Also, right now you can only change the readme on the tool’s page by having a README.md file inside an uploaded xrnx, this is to be able to keep this data in sync with the files (friendly to version control as well) instead of having to deal with editing the pages on the site.
With the addition of this feature the goal is to make the .xrnx file the main source of truth here, so even if the website changes in the future, all the information is encoded in the tool’s archive, and when you update your tool, you can update the readme in your editor in the same step. The migrated tools from the old site have been “grandfathered in” in a sense that some doesn’t actually have a README.md but still have the readme show up on the page.
Thank you, looks pretty good already. Yes, you are right, readme.md sounds much more reasonable. Will update later.
I don’t know if this is important, but the converter still missed:
[s]stroked text[/s] to be converted to <s>stroked thru</s> or siimilar> for >Example here: Multijump From/To Send | Tool | Renoise
Doesn’t need to be added for me, I just wanted to mention it
True, unfortunately I don’t think we will patch this.
Strikethrough is not available in common markdown, this will be unsupported.
The xml escape strings would have been nice to convert, but I suppose they will stay as is now, hopefully not many readmes are affected, if this is a big problem we can look into doing another pass here.
For this specific case, you should use the enumeration/list feature in markdown, so instead of
-> Select a track with one or more sends, call “Jump to send” (key or track context menu)
-> first send will be selected
-> again call/press “Jump to send”
…
it could be formatted like
- Select a track with one or more sends, call “Jump to send” (key or track context menu)
- first send will be selected
- again call/press “Jump to send”
…
Actually, we already support strike-through but the converter used to migrate the readmes has not been supporting it. If you want such text in your readme you’ll need to use the double-tilde syntax.
~~some text~~
will become
some text