I have all email notifications disabled, yet I still receive "Files Update" emails. How do I stop Curse from sending these emails?
- Curse Premium
Member for 8 years, 5 months, and 15 days
Last active Fri, Sep, 20 2019 22:03:46
- 0 Followers
- 10 Total Posts
- 0 Thanks
Dec 7, 2016Posted in: WoW Sites Feedback
First, put your checkboxes along the left side in front of their descriptive text. When they're across the screen along the right side, it's difficult to line up which text go with which checks.
Second, your "New files by followed authors" text selects the "New files in followed projects" checkbox. Probably just a copypaste thing.
Nov 22, 2016Posted in: WoW Sites Feedback
With every zip file uploaded, CurseForge opens the zip, edits the lua, saves a new zip, and serves that new zip to users. This is unacceptable. Do not modify the files we send to you. Every byte is there for a reason. I understand you want to open the zip and look around, and that's fine. But if it passes your filters, you should post the file we sent you, unedited.
This was already noticed in this thread, but I have further details that go beyond line endings.
Specifically, CurseForge edits lua and toc files, changing line endings from 0x0A to 0x0D 0x0A, and replacing all bytes over 0x7F with the Unicode Replacement Character (0xEF 0xBF 0xBD).
News flash: not all strings are Unicode text! My addon stores data in lua strings in binary format to save space. A price for every item on every realm in the US and EU is already a lot of data; encoding it in non-binary strings would be very slow and inefficient.
Here is a valid-for-WoW lua file with every 8-bit byte: https://addon.theunderminejournal.com/curse/good.lua
Here is what it looks like after CurseForge edits it: https://addon.theunderminejournal.com/curse/bad.lua
Please post our zip files unedited as we sent them to you. My addon cannot be hosted on Curse until this is resolved.
Nov 22, 2016Posted in: WoW Sites Feedback
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.
Nov 21, 2016Posted in: WoW Sites Feedback
Do you have your code online? I'd like to compare it with mine, as I'm having similar issues with the curseforge updateIt's a WIP and not the prettiest thing, but: https://github.com/erorus/newsstand/blob/master/scripts/addonupdater/curseupdater.phpNormally 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.
Nov 20, 2016Posted in: WoW Sites Feedback
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.
Nov 19, 2016Posted in: WoW Sites Feedback
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?
Apr 11, 2011erorus_curseforge posted a message on Uploading through a script: 422 unprocessable entityI'm following http://kb.curseforge.com/projects/uploading-through-a-script/ to automate uploads to my first experimental addon here. No SVN is involved.Posted in: Need Help?
I submit the form post and get back "HTTP/1.1 422 UNPROCESSABLE ENTITY" even though I'm fairly certain that I have all the fields and mime encoding correct. The KB page says it should include a json response to point me to which field failed, but the server does not respond with any body of content.
Any hints, or perhaps differences between the KB page and reality?
Edit: Never mind, doing manual updates isn't so bad.
- To post a comment, please login or register a new account.