I have a zip file with my addon. I want to upload it to CurseForge via a script. Simple. I've been doing this for many months, until the recent CurseForge update required me to change my script.
That page indicates that an upload should be under 5MB. My addon is around 30MB.
Can you increase the max upload size for your API? If not, can you tell me another simple way to upload a zip file to CurseForge unattended, without using a separate repository and your packager?
a bit off topic ... but why keep around on the Curse server the price database files that are older than the current expansion (or more than 6 months old)?
i think that for historic statistics reasons probably only one such database file every 6 months or around major events (new patch/xpac) should be enough... the rest are just using server storage space imho... if people want more detailed statistics data they can visit The Undermine directly.
@Curse admins... can you please publish some overall storage space usage statistics for projects? e.g. top 10 projects by storage space used... i think DBM would probably top the charts here but TUJ can't be far behind.
You should encourage the project admins to clean up some of their old versions... DBM has 310 pages of file lists at the moment.
a bit off topic ... but why keep around on the Curse server the price database files that are older than the current expansion (or more than 6 months old)?
I would delete old versions of the addon if Curse provided an API to do so. I'm not gonna log in and click a couple buttons twice every week.
Normally I'd use my curl-based HTTP class but I commented that out at the end, instead falling back to calling wget so I see the response and narrow down the cause of the issue.
make sure you also compare what the server is publishing as addon with what you're intending to publish... i found out that sometimes it doesn't publish exactly what you intend to publish..
the curseforge server now modifies the files, (during localization processing) it changes at least the EOL from LF to CRLF.
It turns out this is caused by using the URL slug in the API request; we currently only accept the project ID. The API call should be using 29546 instead of undermine-journal.
It turns out this is caused by using the URL slug in the API request; we currently only accept the project ID. The API call should be using 29546 instead of undermine-journal.
Thank you. The API accepted my 29MB file this morning with this change.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I have a zip file with my addon. I want to upload it to CurseForge via a script. Simple. I've been doing this for many months, until the recent CurseForge update required me to change my script.
I followed these instructions: https://github.com/curseforge/api
When I post the form to https://wow.curseforge.com/api/projects/undermine-journal/upload-file, I get forwarded to https://wow.curseforge.com/error/request-too-large
That page indicates that an upload should be under 5MB. My addon is around 30MB.
Can you increase the max upload size for your API? If not, can you tell me another simple way to upload a zip file to CurseForge unattended, without using a separate repository and your packager?
Could you try again, please? Let me know how it goes.
a bit off topic ... but why keep around on the Curse server the price database files that are older than the current expansion (or more than 6 months old)?
i think that for historic statistics reasons probably only one such database file every 6 months or around major events (new patch/xpac) should be enough... the rest are just using server storage space imho... if people want more detailed statistics data they can visit The Undermine directly.
@Curse admins... can you please publish some overall storage space usage statistics for projects? e.g. top 10 projects by storage space used... i think DBM would probably top the charts here but TUJ can't be far behind.
You should encourage the project admins to clean up some of their old versions... DBM has 310 pages of file lists at the moment.
I would delete old versions of the addon if Curse provided an API to do so. I'm not gonna log in and click a couple buttons twice every week.
Do you have your code online? I'd like to compare it with mine, as I'm having similar issues with the curseforge update
make sure you also compare what the server is publishing as addon with what you're intending to publish... i found out that sometimes it doesn't publish exactly what you intend to publish..
the curseforge server now modifies the files, (during localization processing) it changes at least the EOL from LF to CRLF.
https://www.curseforge.com/forums/wow-sites/wow-sites-feedback/127329-file-checksums-and-timestamps-changed-after-upload
Ty!
This has nothing to do with how much your project is using, we will be looking into why it thinks you are uploading a file too large. Thanks :)
It turns out this is caused by using the URL slug in the API request; we currently only accept the project ID. The API call should be using 29546 instead of undermine-journal.