Bug #224: PKExcept in Newest Eoserv Binary (0.6.2)
| ID | #224 |
|---|---|
| Submitter | Hacker_Alex |
| Product | EOSERV |
| Severity | Normal |
| Status | CLOSED, INVALID |
| Submitted | 20th Mar 2013 |
| Updated | 22nd Mar 2013 |
11 years, 41 weeks ago
PKExcept Does not always turn off PK on all maps listed.
On maps that have the PK on value in their data, the PKExcept does not always guarantee that PK is disabled. This shows that there is something wrong in the communication between PKExcept and PK-enabled maps by map properties.
Situation: I set a map to PKExcept. Did a rehash, it worked, pk was disabled. After a restart, the PKExcept no longer worked. I wondered what gives and noticed that that map had the PK value set to on. No I did not edit that map between the server uptime and restart so nothing has changed in the map itself.
Was PKExcept ever meant to turn off PK even on maps that have them on by default?
Comments
11 years, 41 weeks ago
From the description of PKExcept itself: "Only disables PK on maps enabled by GlobalPK". The code explicitly only checks PKExcept as a disabler of GlobalPK's effect, and there is only code to enable PK on non-pk maps dynamically, not the other way around.
Updated Status to CLOSED, INVALID
Add Comment
Please don't post unless you have something relevant to the bug to say.
Do not comment to say "thanks" or "fix this please".
Please log in to add comments. EOSERV Bug Tracker > Bug #224: PKExcept in Newest Eoserv Binary (0.6.2)