Timeline for get_posts() not working when accessing with a custom user role
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2020 at 6:15 | answer | added | Mort 1305 | timeline score: 1 | |
| Nov 21, 2018 at 22:15 | comment | added | Tom J Nowell♦ | You don't have to put everything in taxonomies, storing the status by assigning terms doesn't stop you using post meta for other fields | |
| Nov 21, 2018 at 20:48 | history | edited | Tony Djukic | CC BY-SA 4.0 |
added 636 characters in body
|
| Nov 21, 2018 at 18:37 | answer | added | socki03 | timeline score: 0 | |
| Nov 21, 2018 at 18:08 | comment | added | Tony Djukic | I hear you @tomjnowell, that was my original plan but there's a lot more data in the sessions than just the status and it wouldn't have worked as a taxonomy. For this purpose however I only need to check the status. At any given time there shouldn't be more than 4 or 5 sessions in the system, and usually no more than 2 active. So it's a really quick query. | |
| Nov 21, 2018 at 18:02 | comment | added | Tom J Nowell♦ |
A sidenote but your querying for mwss_session_status is super expensive/slow, mwss_session_status should really have been a taxonomy with 2 terms, 'true` and false, it could be 100x faster to query
|
|
| Nov 21, 2018 at 17:55 | review | First posts | |||
| Nov 22, 2018 at 3:33 | |||||
| Nov 21, 2018 at 17:55 | history | asked | Tony Djukic | CC BY-SA 4.0 |