Well, I searched for a few words to pay tribute to the work of UNA Team with this new version of UNA. while remembering these first stammerings. What fantastic progress! I am dazzled...
Here are those few words.
It took a long time but they got there
They count what they left there
Much more than feathers, whole pieces
And some even say a little identity
Yet she is in them this motionless force
Who pushes them forward, prevents them from sleeping
Always towards effort alongside pleasures
Until obsessing them with this unique mobile
To be the first, to be the first
To get up there, at the very end of the ladder
Like those black eagles that dominate the sky
To be the first, to be the first...
You are the best ! Many thanks to the whole team !
It has been several times that I have lost a member because they have no control over who can comment on their personal photos, nor can they delete a comment they dislike.
Correct me if I'm wrong, but currently the only way for a member to delete a comment is to use the admin. When I explain this, the answer is often: "Well that's a shame, so I'm leaving the site". What I can understand ...
If there is a way to fix it, I haven't found it ...
Personal (portrait) photos are special objects, I think it was a mistake to treat them like everyone else, because you will find stupid comments at best, derogatory comments at worst.
A solution for this?
I have seen that a lot of questions are asked about this. Trying to post a #video, and it doesn't work?First check 3 things. Go to Studio => Host Tools => Files and folders permission.You should have something like this:
Check that Cron is working, you should have "Last run" <1 minutes:
----------------------------------------------------
On the server side (php.ini) side, these 3 values are important and ideally like this:max_execution_time = 360max_input_time = 360memory_limit = 512M (minimum)Important: The "upload_max_filesize" and "post_max_size" values of your server (php.ini) will always take precedence over the UNA settings.----------------------------------------------------If this works for small videos and not for bigger ones, you may need to increase the "Default cURL timeout" setting.You can find this setting at the bottom of the Studio => Developer page
It currently defaults to 10. It appears to depend on server bandwidth. Test 120 In my case I had to increase it to 300 for a 2 GB video.-------------------------------------------------------Also, it can be useful to check if FFMPEG is not consuming too many resources, you can see this with the "htop" or"top" command. In my case, "Load average" went up to 8, although that didn't seem to be a problem, I preferred to limit.This is possible with a utility such as "cpulimite".Order example:"cpulimit -e /your_path/plugins/ffmpeg/ffmpeg.exe -l 80"-l 80 limit to 80% by adding the -v option, you can see it working and testing to find the right limit.
You can then create a.sh script and run it on startup via a cron job with something like:
@reboot /root/scripts/limitesCPU/limitesFFMPEG.sh
