View Single Post
06-22-20, 12:32 PM   #38
LudiusMaximus
A Rage Talon Dragon Guard
 
LudiusMaximus's Avatar
AddOn Author - Click to view addons
Join Date: Mar 2018
Posts: 320
Originally Posted by LudiusMaximus View Post
The first upload when creating the classic project had to be manual via the web page. But what happens when I use the API the next time?

Am I allowed to put e.g. '1.13.4' in the 'compatible' endpoint? Its description goes: "If you provide the classic version number it will tag your upload for classic." But will it recognise that my current file is already classic and replace it? Or will it think my current file is retail and add the new API upload as classic, like it seemed to be the case some time ago?
It is as I suspected: My second upload via the API got recognised as "classic", and my initial upload is still shown as a putative "retail" version (but at the same time it is also shown as archived... @Dolby or any admin, is there a way to not show the putative "retail" link any more?

https://www.wowinterface.com/downloa...amClassic.html
__________________
~ Be the change you want to see in the world... of warcraft interface! ~

Last edited by LudiusMaximus : 06-22-20 at 12:47 PM.
  Reply With Quote