When I upgraded UNA to 14.0.0-RC2, my iFrames started being blocked from showing on the Timeline. I'm looking through the code to try to figure out how to change this. I am downloading the last version to compare certain files. Does anyone know how to fix this?
Jitsi has been discussed here for about 5 years. Most questions on the subject were answered but many were not. Yes, we know that Jitsi has changed their terms.
Needless to say, today's social site users expect easy to navigate, seamless video of all kinds. If they don't find it, they will keep moving on to sites which do.
Users, however, have no idea how complicated coding is for internet video, audio and streaming... For example, the video engine here on UNA is based on FFmpeg - which has dozens of pages of just settings. The documentation would fill a large book.
Anyway, it appears that UNA did the heavy lifting and integrated Jitsi into their Messenger app. At present, it connects for video calls which are subject to a five minute limit. A link is provided to "Jitsi As a Service" or JAAS and there is an offer for a free "starter package". The free service is limited to a small group of users, of course. Which is much, much better than nothing.
So for self-hosters, the question is: How do the Jitsi required settings correspond or interface with those in the Messenger settings? I cannot get them to work. Jitsi states that: "All you need to do is to copy the integration code snippet and paste it into your app or website."
I realize that for the full video services a dedicated server with ample resources is needed. So, I guess the free service is the iFrame variety. But how? And why does it seem so complicated?
Hi Una SEO Expert,
I am exploring the website for professional networking and so far everything looks good and I am learning a lot. When it comes to SEO, I have seen how we can optimize SEO for certain static pages, but when it comes to dynamic pages like User Profiles, I do not see any option to do SEO. Below is a quick comparison of user profiles on LinkedIn and my website user profile in Google search . Could you please suggest how I can achieve similar SEO meta tags description for profile pages? (my website profile page have fields like Location, Profile Title, Summary Description ). Any support and guidance will be much appreciated.
Thanks,
I was using the video button in the Quill editor to post videos to the timeline. I just upgraded to the latest UNA and the new HTMLpurifier rewrite is hiding all videos. This happens on regular and admin accounts. Is there a way to bypass this?
Hi @AQB Soft , love the mod Greeting. Does the job. A tiny enhancement could make the 'Greeting' more personal; "Just some chars" added to the greeting, may be up to 60 (?), or a custom number of chars set in studio/greeting/chars_by_greeting (exp.), would make it perfect for a first step of *communication" with users . The use of the default editor (small version) would be the perfect Greeting ;)
I try to get this infos (gender,birthday,location ) , but without success
$oProfile = BxDolProfile::getInstance($iProfileId);
$aProfileInfo = $oProfile->getInfo();
$aProfileGender = $aProfileInfo['gender'];
How can i do?
When I start a comment and select the emoji button in the Quill editor, I am getting a flickering problem with the popup emoji window (#emoji-palette). There is some kind of window/div/frame issue where I have trouble clicking on the categories or selecting an emoji. The emoji window is clipping when it runs into the following post on the timeline. On mobile, it goes underneath that next post at its start. I tried changing the width of the window in custom styles. But that didn't solve the issue. I notice it doesn't happen on this site. I'm not sure if this was something that was fixed post-UNA 13? I attached a screenshot. But the Windows screenshot tool doesn't capture the flickering.
We have been “quiet” for a few months, piecing together the new NEO universal app, core UNA CMS update and a handful of new modules. All these updates are a bit different from the regular new modules and bug fixes. So different, in fact that we had to re-think how to package, ship, and support UNA.
I’ll share the observations first, then takeaways, then the news...
Observations
- Native Apps give a huge advantage. While UNA is responsive and can be shipped as a PWA, native apps from App Stores with interactive, platform-specific UI consistently attract more engagement. For social platforms, 8 out of 10 returning users typically prefer native apps.
- React Web App has greater potential. While the UNA classic UI holds its ground, the Next.js web app exported from the NEO universal app repo represents a significant upgrade. Features like data-prefetching, WebSocket updates, aggressive caching, and virtualized lists enable high-performance modern web apps. UNA CMS is a fantastic API server and admin interface, but for user-facing applications, server-rendered SPAs are the superior choice.
- AI is powerful, promising, yet temperamental. The AI Agents module is theoretically capable of creating automations and tools to compensate for missing modules or integrated services. Its potential is immense, but it requires further research and tooling to unlock fully. However, AI often behaves unpredictably, being overly confident when it shouldn’t be, and needs careful supervision.
- Docs are hard, for two reasons. First, while writing docs isn’t such a big deal, keeping them up to date is hard. We make hundreds of commits for each update and many affect logic to the point that docs require updates. the second reason is justtaposed to the first one - people just don’t read docs. The amount of times we have to explain the same things that are already covered in docs over and over and staggering.
- 99% of the issues are “Day 1 stumbles”. Nearly every problem UNA operators report stems from initial setup, hosting environment, or basic configuration challenges.
Takeaways
We need to make it easier to deploy react apps.
At the moment we only build apps under custom professional support agreements. It’s a very nuanced and tailored approach, taking us a number of weeks to prepare backend and the apps for production deployment. We need to make it more accessible for UNA CMS users to launch the apps.
Pre-configured opinionated kits work best.
The way to make deployment easier is to provide an initial configuration that serves an actual use-case. UNA CMS is powerful, but the “anything is possible” can also mean that its not suitable for anyuthing in particular out of the box. So, we need to focus more on the starter kits, tied with matching pre-preconfigured API and React apps.
AI should interpret docs and knowledge.
If we maintain and update knowdlege base continuously, we can train AI to interpret it and help UNA users understand the system.
Steps
UNA 14 Release
The upcoming release of UNA 14 is heavily focused on API, compatibility with NEO apps and the Agents module for AI-automations. We’re likely to have one more RC shortly followed by final release.
Spacenook + NEO Bundle Starter Kit
Spacenook starter kit is getting an update to UNA 14, some configuration changes and most importantly settings pre-set to work with NEO. It will also include a pre-configured NEO apps package.
AI assistant in UNA Studio and UNA CMS
Still quite experimental at this stage, but we should soon be able to provide a built-in AI-powered assistant chat within Studio helping with configuration, as well as a documentation assistant here at UNA CMS.
Share more about ongoing dev
We’ve been to quiet recently, even though in recent months we made more really exciting changes than ever. We should tell more now and show what’s happening. I’ll keep you posted!
I am trying to set up a test album using one of my testing accounts. Anything related to processing album requests freezes my site. I end up having to reset NGINX and PHP-FPM 8.1. When I check my front-end error log, I get the following (edited):
*1251 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 0000:0000:0000::103, server: EXAMPLE.COM, request: "GET /wordpress/wp-admin/setup-config.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/EXAMPLE.COM.sock:", host: "EXAMPLE.COM"
*1257 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 0000:0000:0000::103, server: EXAMPLE.COM, request: "GET /wp-admin/setup-config.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/EXAMPLE.COM.sock:", host: "EXAMPLE.COM"
*1310 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 0000:0000:0000::103, server: EXAMPLE.COM, request: "GET /wordpress/wp-admin/setup-config.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/EXAMPLE.COM.sock:", host: "EXAMPLE.COM"
*1345 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 0000:0000:0000::103, server: EXAMPLE.COM, request: "GET /wp-admin/setup-config.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/EXAMPLE.COM.sock:", host: "EXAMPLE.COM"
*6 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 000.00.000.00, server: EXAMPLE.COM, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/EXAMPLE.COM.sock:", host: "EXAMPLE.COM", referrer: "h-t-t-p-s://EXAMPLE.-COM-/create-album"
I think I have some kind of conf file problem. I'm not sure. Also, I'm not using WordPress, but I had originally installed it to test the server before installing UNA.