Jump to content

1 Screenshot

  • 1.7m
  • 63.8k
  • 73.53 kB

Recommended Comments



This plugin is not picking up all permissions after the August game update. Someone was saying that there was a change to oxide permissions case sensitivity and that this might be the cause. I'm not going to pretend to know the details, but just wanted to give the heads ups in case there is anything that needs updated with this plugin. 

Link to comment
Share on other sites
  • Administrator

Hi,
I'm not sure the ins and outs but I know there were some unintended case-sensitivity changes in oxide which, I believe, have since been reverted or fixed.

As far as I know all's good right now - I had a check through on my server and everything seems to be working OK again.

 

  • Like 1
Link to comment
Share on other sites

I've been using the plugin for over a year now, thanks for that 🙂

At the moment I have the problem that about 40 plugins are not displayed for example BotReSpawn 😉
I have a Linux server running under Pterodactyl and all the latest updates are installed.

  • Like 1
Link to comment
Share on other sites

I peeked around at the CS files for plugins that have permission not showing up in Permissions Manager. They all seem to have one thing in common and that is they are set to register their plugin with mixed cases, ie BotReSpawn.  For comparison I have the plugin "XLevels" which is registering it's permissions as "xlevels" (not XLevels) and that plugin is showing up in Permissions Manager.  Hopefully this helps. 

  • Like 1
Link to comment
Share on other sites
6 hours ago, Steenamaroo said:

Hi,
I'm not sure the ins and outs but I know there were some unintended case-sensitivity changes in oxide which, I believe, have since been reverted or fixed.

As far as I know all's good right now - I had a check through on my server and everything seems to be working OK again.

 

There were 5 updates in a 24 hour span, we're running the most recent version with no issues as well. Bout 140ish plugins all running swell. 
image.png.c89e894b98c3ad166742d8393b7f6768.png

I'm pretty sure the first note on the last update was to correct the problem some people are seeing. I'd suggest running a steam and oxide update on any servers not working correctly just to be safe. Hope this helps!

  • Like 1
Link to comment
Share on other sites
5 hours ago, Neighigh said:

There were 5 updates in a 24 hour span, we're running the most recent version with no issues as well. Bout 140ish plugins all running swell. 
image.png.c89e894b98c3ad166742d8393b7f6768.png

I'm pretty sure the first note on the last update was to correct the problem some people are seeing. I'd suggest running a steam and oxide update on any servers not working correctly just to be safe. Hope this helps!

Unfortunately it did not solve it for me. I was sure i was up to date on Oxide releases but decided to run a server/oxide update just now during our nightly restart just in case and I'm still missing quite a few plugins from the permission manager list.  

  • Sad 1
Link to comment
Share on other sites

im also having this problem . i have the latest version of oxide installed . but to be fair if i try grant the permissions the manual way it says the permissions doesn't exsit

Link to comment
Share on other sites
  • Administrator

I'm seeing the same issue here.
Looks like oxide isn't handling mixed-case Permissions.

Based on their update notes, I think oxide should handled mixed case permissions just fine, as it always did, so I'd suggest reporting this to them - It's possible they aren't aware yet.

Link to comment
Share on other sites
  • Administrator

There was another update since the one in your screen shot.
2.0.5626 - Fixed NullReferenceException when loading permissions on fresh server installs.
Perhaps that one reintroduced issues?

Edited by Steenamaroo
Link to comment
Share on other sites
  • Moderator

Case sensitivity is the devil, permissions should be case agnostic, change my mind. 😉

  • Haha 1
Link to comment
Share on other sites
4 hours ago, Steenamaroo said:

There was another update since the one in your screen shot.
2.0.5626 - Fixed NullReferenceException when loading permissions on fresh server installs.
Perhaps that one reintroduced issues?

I'm confused hearing that lol I really thought I was up to date! Is Umod not displaying their updates correctly? Or maybe they rolled back 626 for these issues? This is what I'm seeing from there:image.png.86c192833ed2c9ed6f24707331b60e0e.png

Link to comment
Share on other sites
  • Administrator

Sorry, that was a typo - I meant 2.0.5625
Still, you said "I'm pretty sure the first note on the last update..." with reference to what is the penultimate update.

Maybe I misunderstood. If you're on 5625, please ignore.

Edited by Steenamaroo
Link to comment
Share on other sites
1 hour ago, Steenamaroo said:

Sorry, that was a typo - I meant 2.0.5625
Still, you said "I'm pretty sure the first note on the last update..." with reference to what is the penultimate update.

Maybe I misunderstood. If you're on 5625, please ignore.

No worries! We're on Linux so I assumed 5623 on our end. Fingers crossed for everyone having troubles!!

Link to comment
Share on other sites
  • Administrator

What build are you on?
2.0.5625 is current, whether linux or windows.

Link to comment
Share on other sites

We're on 2.0.5625, just ran oxide.version to check. Our provider makes it easy for us to update so I assumed(luckily this time) that we were on latest. I seem to have no issues with permissions, not sure why that is, hope they get around to resolving whatever the difference is there.

Link to comment
Share on other sites
  • Administrator

Gotcha. Thanks for clarifying.
That's interesting. Maybe you just don't have any plugins with mixed-case permissions?

Try this. If you don't see 'TestPerm' in PermissionsManager UI, then you've just been lucky.

 

TestPerm.cs

Link to comment
Share on other sites
19 minutes ago, Steenamaroo said:

Gotcha. Thanks for clarifying.
That's interesting. Maybe you just don't have any plugins with mixed-case permissions?

Try this. If you don't see 'TestPerm' in PermissionsManager UI, then you've just been lucky.

 

TestPerm.cs 282 B · 1 download

Yessir, no sign of TestPerm. Counting our lucky stars! Soooo many plugins XD

Link to comment
Share on other sites
On 8/8/2022 at 6:02 AM, Steenamaroo said:

I'm seeing the same issue here.
Looks like oxide isn't handling mixed-case Permissions.

Based on their update notes, I think oxide should handled mixed case permissions just fine, as it always did, so I'd suggest reporting this to them - It's possible they aren't aware yet.

Just noticed that I have at least one permission that I went to check on one of my servers, that isn't showing up. So this must still be somewhat of a thing. I was thinking it was already sorted since they are all working. But I have at least one that I know of that isn't showing up for me inside permission manager. I can manually add or remove the permission. Typing it all in lower case worked fine as well as typing it with mixed case.

Just feedback not a major issue but happened to notice it today.

  • Like 2
Link to comment
Share on other sites
  • Moderator
2 hours ago, Jarrod Everhart said:

i also have had a ton of perms disappear this month that was normally there before

Quote the Raven/Oxide nevermore... Case sensitivity is the devil, adding it to permissions was not an improvement to the Oxide platform. 😞

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Like 23
  • Love 11

User Feedback

1.2m

Downloads

Total number of downloads.

5.9k

Customers

Total customers served.

86.9k

Files Sold

Total number of files sold.

1.7m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.