I would suggest releasing fixes to bugs in B4 and leave mod enhancements for a later date. B3 just created more bugs hence B4 and B4 might create more bugs and so forth... Releasing the fixs for bugs right now would help. Mod enhancements are seperate from a stable release and can always be done on a later date.
Comments
I do agree!
Makes a perfect sense!
To me this is kind of getting out of hand. I actually thought B3 was going to be the stable version and we're into B4 now...
The Streaming option for UNA Cloud members still isn't available to us either. I'm at a crossroads wether to just fold and not look back... Spent too much money on a product that simply doesn't work. Been with UNA working on this site since 2019 and still don't have a stable version.
I don't think it makes sense to add a bunch of enhancements with the bugs making it take longer to release the fixs that already have been fixed.
K
We’re almost there. Hang tight. They said RC will follow the B4. It’s been a roller coaster ride for sure, but I really do like all the enhancements- made it a lot better.
I wish it really was that easy but even after B4 I have to wait for the other mod developers to update their mods... Then I have to wait for UNA to do something for UNA Cloud members so we can use the Streaming App. My custom template has been broken again after B3 so there's that also.
When it comes to first digit(s) in beta like 11, 12, 13, 14. There is no way to break down. Developers/Hackers Feedback begins.
12.0.0-B1, 12.0.0-B2, 12.0.0-B3, 12.0.0-B4
13.0.0-B1, 13.0.0-B2, 13.0.0-B3, 13.0.0-B4
When it comes to release candidate. Public and Feedback begins.
12.0.0
13.0.0
When it comes to before first point, we can break down.
12.0.1
13.0.1
When it comes to next digit(s) in betas. Previous stable version usually halt, then we can update if needed before upgrading.
That's just the way things works in development. One time, I alerted Alex T a serious bug which led to immediate update and pushed other tickets to next number.
Been working on Artificer's vanilla custom style, and will not share until final release. Why? CSS, Database, HTML, JS, PHP and who knows what else could have been added/changed/removed between betas and before RC.
Some developers are brave enough to develop during betas and be prepared to release shortly after RC. Most don't, because they don't want to deal with buggy betas. Hence longer waiting period.
UNA Development First. Others Module Development Second.
Updating/Changing Open Source Software and Third-party Plugins. Therefore, UNA's betas are being develop as is. They did great job. If you're not a developer or not familiar with css, html, js, php coding. Then why did you get involved with beta on your live-production site? If you're so curious, please create a beta folder or subdomain like beta.yoursite.com. This way, you can decide whether your site's ready to upgrade or not.
Hope this clears up.
This was the same situation in Dolphin. Issues with script were always evident and not addressed, and new features were always priority, which did nothing for the script issues....
"Why did you get involved with beta on your live production site?"
Good question. My site was never "Live". I had a couple people join to test it out and give feedback. Even with UNA 12 it still had way too many bugs to go live with. So I continued with upgrading the betas with the hope that those bugs would be fixed. It wasn't just bugs that kept getting created, it was the entire custom template that got deformed because the implementation of Tailwind changed it. I contacted the original developer of my template and they do not do any custom work. So basically I bought a custom theme that does not work. I made plenty of suggestions like an open sandbox for developers of mods to be able to see how their mod changes with UNA 13 beta releases so they can update their mods over time. No sandbox was created. Many developers are waiting for UNA 13 to even attempt to fix their mods. Even if I had kept my site on UNA 12; I could not release it as it was still unstable. At least with allowing my site to go to beta I can try and make changes that I can. UNA 12 isn't stable; UNA betas aren't stable... So like you said unless I can do the work myself then why go through the betas?
1.) Fixed my template issue
2.) Give numerous feedback to the community about what fixes they will need once UNA 13 is released. Many people don't realize how much their site is going to change and may not be prepared or able to make the changes.
3.) If I just wanted the basic out of the box look for my site with the same colors, fonts, etc... Well yea I could have just stayed on UNA 12 bugs and all; went live and watched everyone leave....
4.) For many of us on UNA Cloud we do not have access to the servers. We cannot make any changes that involve us gaining access to the servers. The best we can do is work with RAW blocks and CSS scripts.
5.) We do not have access to the Streaming App. At all. I paid $150 for it just to find out UNA Cloud members do not get to stream UNTIL AFTER a stable version of UNA 13 is released (via UNA Team) so yes would love to expedite UNA 13
Some users with really good sites with heavy custom work on UNA 12 shouldn't have to wait over a year to get bugs fixed... And that my friend is what it boils down to. UNA 13 should have been a separate possible project with Tailwind; but hot fixes to UNA 12 should have been kept going on a monthly basis. Those much needed hot fixs are rolled into beta 13 unfortunately over a year later so many people gambled on going into beta to at least attempt to get their bugs fixed instead of waiting over a year
I run three UNA sites (six UNA licenses) and have over twenty domains. Been using custom Decorous and custom Protean for long time. Am already moving on to custom Artificer.
In a standard business production environment, a sandbox might be misunderstood or considered a needless expense. But sandboxes are critical for several scenarios in development, cybersecurity and research. Making sure the sandbox is truly isolated and secure is more important in cybersecurity research than in software development because malware actively and aggressively scans the network for exploitable vulnerabilities.
To do any security research or dive into malware analysis, a sandbox is a must. It will ensure that all resources are unavailable to the virtual machine, including network storage. With a sandbox, you can analyze code without the risk of destroying a production environment.
Even though a sandbox should be a safe space, attackers always try to break sandbox security.
If you need a sandbox to test code or potential malware, you can create your own sandbox by installing a virtual machine. VirtualBox is often used to host the virtual environment, also called a virtual machine. Then you just need an installation file to run the operating system within the virtual machine.
1) What was your custom template based on? If Decorous, Lucid, Ocean, Protean... these will come to Tailwind CSS revision in UNA 14.
2) Again, beta is not for community unless you created beta.yoursite.tld, those who wants to participate should storm-in with reports.
3) Leave default plain template as-is! That looks perfect. *humour intended*
4) If you need full access to server, go with VPS or Dedicated Server.
5) Free via manual which require access to VPS or Dedicated Server.
Pro Cloud (UNA)
2 CPU
4GB RAM
80GB SSD
$199/month
UNA responsible to maintain hardware and software*.
* Additional cost may imply
VPS (Not UNA)
4 Cores
8GB RAM
160GB SSD NVMe
$19.55/month
You could create a virtual machine with quarter or half resources.
You responsible to maintain hardware and software, UNA can help only within UNA software* and related.
* Additional cost may imply
Dedicated Server (Not UNA)
8 Cores / 16 Threads
64GB RAM
2x 960 SSD NVMe + 2x 6TB HDD
$127.85/month
You could create two virtual machines or more.
You responsible to maintain hardware and software, UNA can help only within UNA software* and related.
* Additional cost may imply