Can't get my scrolling menu's to scroll or execute.
I'm using CB 1.1-R3, ScrollingMenuSign v1.1.1, Essentials Core, ChopTree, Lift-7, NoLagg, and SignThatChest-1.8. I have the RedPower, Buildcraft, ModLoader MP, and Minecraft Forge Bukkit ported mods.
Both my girlfriend and are OP's but neither one of us can make the signs do anything beyond being setup. I'm not using a permission plugin and would like to avoid that fiasco for as long as possible.
I used this plugin a while back and loved how easy and powerful it was, I greatly appreciate any help.
Not able to reproduce the problem at this point.
I'm having the same problem. Using GroupManager for perms, but won't work for Ops, even when adding the nodes. I tried "/sms debug" and it's telling me allowed=false for scrolling and executing. I've tried adding scrollingmenusign.* and scrollingmenusign.admin. I even set scrollingmenusign.execute and still says allowed=false.
::UPDATE:: I updated to the latest GroupManager build, and everything works now! :)
I'll download 1.1.1 again. Something that might be of note that I didn't realize before, we are directly under the spawn point, within the same chunk, and I haven't tried to set up a scrolling sign outside of it yet. I'm gonna test it right now.
Edit: Would it be better for me to get 1.1.1 or 1.1.3?
Edit2: Just tried with 1.1.3, moved away from the spawn point by quite a bit. Unable to scroll or execute.
Get 1.1.3 - although I don't think it will affect your particular problem, it does contain various other bugfixes which are worth having.
I haven't done any GroupManager testing, but I will do so when I get a chance.
I setup GroupManager and it's working now, if you can think of anything else I can do to test this with just OP's I'll be glad to pull GM to do so. On that note, it doesn't seem to matter where the sign is, works fine in the spawn chunk.
If you can't recreate the issue then it's fine, I am using a lot of non-standard crap right now lol. Thanks for the help and the great plugin!
Yeah, PEX seems to like doing things its own way. Unfortunately far too many people use it, but I'm still very tempted to just say "PEX is not supported" :) Bukkit itself needs to take part of the blame too, for a way-too-vague specification of how superperms parent-child node relationships work.
Seriously though, I am considering a complete permissions rewrite for the next major SMS release - it would be less flexible, but hopefully a lot more reliable.
I am experiencing this phenomenon, too. Signs are becoming unresponsive. I used the "/sms list" command, and it's saying there are 0 views. The text on the sign remains, but it would seem SMS no longer remembers them.
That sounds like a completely unrelated problem, to do with saved view data not reloading properly. Please open a new ticket, and attach a zipped up copy of your plugins/ScrollingMenuSign folder (and let me know which menu(s) aren't working any more). Also check for any errors in the server startup log related to ScrollingMenuSign.
Is it still an issue using SMS with Pex?
I tried SMS today and get the same problem. using CB 1.3.1-R1.0, Pex 1.19.3 and SMS 1.5.0.
Curious to know if this is the problem before I spend hours converting to GroupManager.
Yes, it is still an issue is the answer after a couple of testruns with GM. Time to learn how GM works...
Switching away from PermissionsEx is probably the right choice :) But if you do have trouble with scrolling/executing etc., the best course action is to enable some debugging, and post the results. Do /sms set log_level fine, and /pex debug, then try to scroll and/or execute something. You can do /sms set log_level info afterwards to disable debugging.
/sms set log_level fine
/sms set log_level info
To post a comment, please
or register a new account.