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.
The disabled brokers bug was fixed some times ago, but the fix seems to be lost. It'll work in the next alpha version, that will be released as soon as the repository works again.
The new alpha version should have the fix. It worked the last time I tested this...
This isn't fixed in 1.11-beta1-4-gfda0724, the version where this started happening is 1.1-5-gebba849, with 1.1-1-g6909d6c being the working version. That being the problem with disabling a broker and not being able to re-enable it because the settings tab is disabled. Hope that helps and makes sense.
This isn't fixed in 1.11-beta1-4-gfda0724, the version where this started happening is 1.1-5-gebba849, with 1.1-1-g6909d6c being the working version. That being the problem with disabling a broker and not being able to re-enable it because the settings tab is disabled. Hope that helps and makes sense.
Hm you're right... I was sure I uploaded a fix for this :( I'll do this as soon as possible.
Why am I getting a massive "The data object X has no type attribute set." on login all of the sudden D:?
Theese messages were only ment to be printed in alpha versions... It seems that I have forgot to upload my latest changes before going on holiday. 1.11-beta3 should be less verbose.
Good Morning! First of all, thanks alot for this great addon, I do appreciate it. I've just downloaded latest Fortress verion (1.11.2) with the new Icon and Text alignment feature and I notice a undesired (well, in my opinion of course) behaviour: if I hide the block icon on a per-block basis, the "space" used by the icon itself is still being counted and I have a lot of blank space in between the text. Any chance to fix this? Thanks! And :)
-
View User Profile
-
View Posts
-
Send Message
Project AuthorIf you're using TipTac, fiddle with the mouseover/anchoring settings. That's a known issue.
Any chance on getting the fix up?
This isn't fixed in 1.11-beta1-4-gfda0724, the version where this started happening is 1.1-5-gebba849, with 1.1-1-g6909d6c being the working version. That being the problem with disabling a broker and not being able to re-enable it because the settings tab is disabled. Hope that helps and makes sense.
Hm you're right... I was sure I uploaded a fix for this :( I'll do this as soon as possible.
Edit: The new beta version (1.11-beta2) should fix this bug: http://www.wowace.com/projects/fortress/files/152-1-11-beta2/
Theese messages were only ment to be printed in alpha versions... It seems that I have forgot to upload my latest changes before going on holiday. 1.11-beta3 should be less verbose.
Fixed! :) Thanks
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator