Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
Thanks for the help, I therefore assume that you are packaging locally and then uploading the two zip files to wowace ?
But unlike curseforge, wowace does not allow to upload zips, or maybe i have not found the option.
Can i create a project in wowace only to make tests, would this kind of test project be approved ?, maybe creating an experimental project ?
travis is a cloud CI, so the package gets created on their server automatically every commit and then uploaded as a zip to wowace. wowace only allows zip uploads via their API, which we use.
Any update on this topic ? Any official documentation ? I have seen different approaches, i like the option of two pkgmetas: pkgmeta-retail and pkgmeta-classic like in:
Because with this approach you can use the same code/branch but at the same time it's possible to package different libraries/files.
But i have no idea how Stanzilla is really forcing the wowace-packager to use different pkgmetas to create retail and classic versions (there are not different branches /tags in his repository). Is he using any undocumented packager behavior ? Or i have been overlooked some important info ?
The URLs have changed, you need to update them. Also the packager currently bugs out with SVN External and it's old/bad practice to use them anyway, so might wanna stop doing it.
We're sorry, but this module is currently disabled. Please contact a site admin if this has been done in error. Site admins can enable modules under Site Configuration - General Settings in the Control Panel
Also I have no idea how I can actually navigate to my public profile without typing the URL in manually? Can you just add a "My Projects" link in teh user dropdown? Would be the best solution for me. Also a "View my public profile" link on https://www.wowace.com/account/profile?
I like the tags at the bottom. Its typical for me to also change the tags when I comment on an issue, so having them on the top would require quite a bit of scrolling - especially when there is a lot of comments already.
In fact, the majority of the time I would end up reading at the bottom of a ticket, so having controls there as well is better then at the top.
One idea for that: the header of the issue could just not scroll with the rest of the page, so you can always see what the title of the issue is, it's current tags and the controls on the right.
I agree that having a sidebar was better in the old design, for the new one, I think there is not that many options available per issue to justify the space it would take up.
Instead I would like to see the "Assignee" and "Tags" boxes moved next to the Edit etc buttons. Having them always at the top is more handy, as you don't have to scroll all the way down on longer issue threads.
The close checkbox feels super weird, and I think the GitHub approach to this is better, a "Close and Comment" button next to the "Update Issue" button which should then be changed to just "Comment" since you are not really updating anything, just adding your comment. I am not sure how it works currently, but I expect adding/removing changes to not cause a page reload and being done via JS, so the "Update Issue" text makes even less sense.
In addition to that, being able to assign colors to tags, like GitHub labels, would be a very welcome change.
0
Discord: https://discord.gg/sVQCHr5
0
travis is a cloud CI, so the package gets created on their server automatically every commit and then uploaded as a zip to wowace. wowace only allows zip uploads via their API, which we use.
0
Hey there, we are using the BigWigs packager, not the Wowace one, it's way better https://github.com/BigWigsMods/packager
and see our travis file on how we use it https://github.com/WeakAuras/WeakAuras2/blob/master/.travis.yml
0
Any news here? Been a few months and 0 changes..
0
Okay Torhal just told me that clicking your own avatar is the way to go to your profile.
0
Nevermind, I guess. It shows everything as updated as today, just one year ago.
0
So my packager run failed because of https://www.curseforge.com/forums/wow-sites/wow-sites-feedback/128694-pkgmeta-moving-a-subfolder-with-the-same-name-as?comment=4 yet the client shows the project as updated just now:
0
So my setup is
root/
AddonFolder
.pkgmeta
README.md
Example:
And I used to move AddonFolder into root with pkgmeta. Will that be possible (again) in the future or do I have to change my repo?
0
The URLs have changed, you need to update them. Also the packager currently bugs out with SVN External and it's old/bad practice to use them anyway, so might wanna stop doing it.
0
When I click "My threads" on the user dropdown, I get directed to https://www.wowace.com/new-content?filter-date-range-type=4&filter-association-type=3 which says
Also I have no idea how I can actually navigate to my public profile without typing the URL in manually? Can you just add a "My Projects" link in teh user dropdown? Would be the best solution for me. Also a "View my public profile" link on https://www.wowace.com/account/profile?
0
Dupe of https://www.curseforge.com/forums/wow-sites/wow-sites-feedback/127754-stop-changing-our-code
0
0
Mockup:
0
I agree that having a sidebar was better in the old design, for the new one, I think there is not that many options available per issue to justify the space it would take up.
Instead I would like to see the "Assignee" and "Tags" boxes moved next to the Edit etc buttons. Having them always at the top is more handy, as you don't have to scroll all the way down on longer issue threads.
The close checkbox feels super weird, and I think the GitHub approach to this is better, a "Close and Comment" button next to the "Update Issue" button which should then be changed to just "Comment" since you are not really updating anything, just adding your comment. I am not sure how it works currently, but I expect adding/removing changes to not cause a page reload and being done via JS, so the "Update Issue" text makes even less sense.
In addition to that, being able to assign colors to tags, like GitHub labels, would be a very welcome change.
0