I've noticed that if I set limits on how many actions can be performed after a given set of time has passed, for example, posting 5 feed items every 1 hour, the message prompted to users is displayed as a ISO 8601 value rather than something that's understandable by humans that are not fluent in these things.
An example, when the user has reached their limit of actions, instead of it displaying in a standard time, it prints off as 2024-07-06T21:40:00+0000 that they will be able to once again perform actions.
I'm unsure if this is just a configuration mishap on my part or it's something that the UNA core is doing.
It was recently reported to me from a Premium user that they were getting the file size limit I have set for the "Standard" user role.
I had Standard user member set to only allow up to 6MB in file size while Premium users were using the server-limit I set of 18MB, however the Premium member was only able to upload up to 6MB file sizes, anything higher would result in a broken file/image.
This doesn't make sense to me how these settings are bleeding in to one another when we're given the option to set the file size limit for uploading per user role.
Edit:
I'm running version: 14.0.0-B1
From what I can tell, after a poll has ran its course, there is no way to close the poll to prevent future voting. The only way that I can tell to cease voting is by deleting the poll entirely or having it set to where only I can view it.
This prevents us from having historical data to show community votes, can we get a feature added to the Poll application to allow for owners of a Poll to manually close it out to prevent future votes when their deadline hits for the poll?
Ever since the fix came out to enable the friend request button for profiles that are private, people are unable to undo their pending request to a user who has a private profile both from the profile and profile cards under sent requests within connections. The button is hidden for private profiles but still there for public profiles.
While most of my reported issues have appeared to be resolved, there's still multiple instances where it's still not respected.
Before I go into detail, let me provide links for context:
https://unacms.com/d/album-photos-are-not-respecting-content
https://github.com/unacms/una/issues/4630
Within the albums app, it's still not respected when a user navigates to the Popular Images and Top Images tabs within the Albums app. They are both shown regardless of the signed in users Content Filter settings.
For the Timeline app, if a user sets the content filter rating on it, a user can get around these settings by having a direct link to the timeline feed item (usually obtained by clicking on the time link on the feed item to be brought to the dedicated feed item display) and I also tested this for a signed out member, they have full access to this, despite my settings being set as the following:
With this setting in mind, this should not happen, but it does, I'm unsure how this impacts other Apps that make use of the content filter rating system, I have tested the Photos app and it works as intended from my brief testing.
When I switched to stable, the script detects the stable release of 13.1.0 but it does not offer a way to do the update.
However if I switch it back to beta, I can see and click to update to the latest beta release of 14.
Now I don't mind updating directly to the latest beta from my current versioning, but would that produce errors if I totally skip 13.1.0 stable?
I am looking for which part of the UNA code is force setting content filter boxes to be checked after it checks the profiles date of birth field.
I am seeking to modify this so that the boxes are not by default checked, but instead are offered to the user to be checked if the requirements are met for the rating to be offered to the user.
As it stands right now, if someone that is age 21 or over, the following is displayed.
✅G
✅PG
✅PG-13
✅R
✅X
What I desire, by default, when someone who creates a profile that is 21 or over, have the following by default.
✅G
🔲PG
🔲PG-13
🔲R
🔲X
Reason: Not everyone wishes to see such content above their comfort zone right out of the gate, and with age verification laws going into effect, we must start disabling and hiding R and X until a user has paid to have these unlocked, such as purchasing Premium so that a transactional history data is logged to verify age to meet law requirements.
I've already discovered how to hide the options R and X for users, but this doesn't stop the UNA script from automatically checking the boxes upon profile creation....
I created a new role that's suppose to supersede the default "Mod" role, I noticed when I navigate to any modules "Manage" page, the toggle to switch between your own context items versus all context items is gone.
I tried looking high and low for this item in studio and I'm drawing blanks here, just where in Studio is this located?
I recently noticed that if photos within an album get any kind of interactions that would normally send the context owner a notification, it doesn't.
When someone comments on a photo within the album, no notification.
If someone leaves a like on the photo within the album, no notification.
The only time when someone gets a notification about the album (not its contents) is when someone comments or likes the overall album itself.
Is this a bug or intended?