Bumping because this is still a bug in 0.1.12c and @zep is working on 0.1.12d
Apparently this can be circumvented through code trickery so this may be intentional
@dw817 just fixed it ^-^ didnt reload the page before posting the comment before this
1
Awww man (cracking knuckles) code trickery is what I do best.
Glad you got it solved though.
[Please log in to post a comment]