View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000699 | XMB1 | Bugs | public | 2024-04-08 19:44 | 2024-04-15 04:35 |
| Reporter | flushedpancake | Assigned To | miqrogroove | ||
| Priority | low | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | suspended | ||
| Product Version | 1.9.8 SP2 | ||||
| Summary | 0000699: 'Custom status' is only enterable from the admins' 'edit another user's profile', rather than from memcp even if user has perms | ||||
| Description | No idea if this is intentional or not, but it's likely a very old bug. e.g. editprofile.php?user=flushedpancake lets me edit my custom title, but even though I'm a super admin, I can't do this in memcp.php?action=profile. | ||||
| Tags | No tags attached. | ||||
| MySQL Version | |||||
| PHP Version | |||||
| Web Server | |||||
| Browser | |||||
| Flags | |||||
| Original Reporter | |||||
| SVN Revision | |||||
| Git Commit | |||||
|
|
The permissions described by this issue don't exist. The only privilege allowed by memcp is for admins to bypass quarantine, bypass the avatar size limit, and see invisible buddies. Anything else would be a feature request of some sort. |
|
|
Could this be adapted into a feature request? I'd rather not have to open up another issue about this, so. |
|
|
What's the feature exactly? Just make `memcp` more like `editprofile`? Or unify them? Or create a better permissions system? |
|
|
I'm assuming it's not possible to do something like "if user's rank is below moderator, (template which would be used in memcp to display the field for a custom status) return an empty string" type of thing with the current system in an efficient manner due to limitations? That said, now that I actually bothered to look at it, it'd bring about an inconsistency with the rest of the memcp_profile template, since there, all the input fields are just part of the template, and embedding a template with input stuff in it just feels "off", if that makes sense. For consistency's sake, hacking in a rank dependent field seems rightly out of scope and it's probably best to consider this a non-issue with the current system, and factoring in the amount of time and effort it would take to templatise every single input field it's not worth the effort for a small project like this. Apologies if that sounded incredibly awkwardly worded. |
|
|
For a feature request, don't worry about the details. Just describe the outcome. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-04-08 19:44 | flushedpancake | New Issue | |
| 2024-04-09 15:17 | miqrogroove | Assigned To | => miqrogroove |
| 2024-04-09 15:17 | miqrogroove | Status | new => resolved |
| 2024-04-09 15:17 | miqrogroove | Resolution | open => suspended |
| 2024-04-09 15:17 | miqrogroove | Note Added: 0000463 | |
| 2024-04-09 21:25 | flushedpancake | Status | resolved => feedback |
| 2024-04-09 21:25 | flushedpancake | Resolution | suspended => reopened |
| 2024-04-09 21:25 | flushedpancake | Note Added: 0000471 | |
| 2024-04-10 04:27 | miqrogroove | Note Added: 0000472 | |
| 2024-04-10 10:38 | flushedpancake | Note Added: 0000477 | |
| 2024-04-10 10:38 | flushedpancake | Status | feedback => assigned |
| 2024-04-10 11:56 | miqrogroove | Status | assigned => resolved |
| 2024-04-10 11:56 | miqrogroove | Resolution | reopened => suspended |
| 2024-04-10 11:56 | miqrogroove | Note Added: 0000480 | |
| 2024-04-15 04:35 | miqrogroove | Status | resolved => closed |
