UNA 15.0.0-A1 is now available. Anyone tried it yet ?

So finally its available on Github ..

github dot com/unacms/una/releases/

Anyone tried it yet ? I will try on a test setup later..

It includes SpaceNook too and a long list of changes.

  • Up vote
    5
    Down vote
  • View
    317
  • More
Replies (29)

    • Wau..good job @unateam 👍

      • If your site is live and you rely on search traffic, it’s better not to install it yet — otherwise you’ll end up with a large number of pages having identical descriptions. UNA CMS already has many duplicate pages even without this.

        • P

          On my „normal“ Una website the update is available, on my Spacenook instance not, why that?

          • Even if you launch a new site on UNA 15, you won’t be able to change the descriptions on some pages just like that — for example, category pages. On UNA, all category pages have the same description, and user pages often use the same identical descriptions as the category pages. 🙂

            • Just to clarify:

              This isn’t a Spacenook release it’s only UNA 15.0.0-A1, which is an early alpha (A1) build, not the final stable version.

              Spacenook is a customized UNA stable release that includes specific preset configurations and adjustments.

              Such customized Spacenook builds are created only for stable UNA releases, not for alpha or beta versions.

              For reference:

              • A1 / Alpha 1 → first internal test build (unstable, for developers)
              • B1 / Beta 1 → public test version (more stable, but still in testing)
              • RC (Release Candidate) → nearly final, used for validation
              • Release (Stable) → official, production-ready version

              • I think this can be customized.

                • H

                  Have you checked github ? Check the link - github dot com /unacms/UNA/releases/tag/15.0.0-A1 (I cant pastte link, so change dot to .). under the assets .

                  github dot com/unacms/UNA/releases/download/15.0.0-A1/UNA-Spacenook-v dot 15 dot 0 dot 0-A1 dot zip

                  ooff... I cant even paste a zip file name here.. It doesnt allow it ..

                  So there is a spacenook release for this alpha release... whatever that means.

                  image_transcoder.php?o=sys_images_editor&h=2863&dpx=2&t=1760122561

                  • H

                    image_transcoder.php?o=sys_images_editor&h=2864&dpx=2&t=1760122581

                    • you're right, that's strange, that means you can update to the beta channel. first time I see Spacenook on a beta version

                      • If you want to enable beta updates, go to the Developer module:

                        studio/module.php?name=bx_developer

                        Look for the Update Channel option and set it to Beta.

                        Then open studio/dashboard.php and click Update to check for the latest beta build.

                        Also, in studio/settings.php, there’s an option called Automatic System Updates → “Try to update core system and modules automatically.”

                        These options will automatically update any modules that are available on the UNA Market.

                        I’m not sure why all the update-related settings are so scattered across different places, but that’s how it is for now.

                        Make sure to create a full backup first, so you can roll back if you’re not satisfied with the result.

                        It’s also a good idea to test the update on a clome test site before applying it to your live installation.

                        • @Ivan Mishchenko do you mean pages like this one - https://unacms.com/searchKeyword.php?cat=bx_posts_cats&keyword=2&section[]=bx_posts ?

                          • Ohh really! @Ivan Mishchenko, I thought that those identical page descriptions, duplicate pages, canonical issues etc were fixed in UNA 15A1.

                            • All pages that didn’t have a description have the same description: “Community powered by UNA Platform.” Even my page has that description. It would be better to change this, otherwise UNACMS could be downgraded in search results — tens of thousands of pages have the same description.

                              • It's specifically the description of each page on the site. All pages of any site updated to version 15 have identical descriptions. For example, on the UNACMS site tens of thousands of pages share the same description — even this comment's page has the description: "Community powered by UNA Platform."

                                • H

                                  And got a strange situation here.. When going to studio/store.php?page=downloaded, I can see the module "Developer" is installed. But in studio/launcher.php, the "Developer" module is not visible..

                                  I am on UNA 14.0.

                                  Maybe due to this, I only see the following Options related to "Update" when visiting the studio/module.php?name=bx_developer

                                  1. Automatic System Updates - Try to update core system and modules automatically.
                                  2. Force Automatic Updates - Update core system and modules even if modified files are detected.

                                  There is no way for me to select the beta channel.

                                  • Yeah, that definitely needs to be addressed by the UNA Team.

                                    • Sorry, I just noticed that you're a standard member. UNA is free to test, but if you want to update, you need to have a license. Updates will not be possible without a valid license not for the installed modules, nor for UNA Core. Only users with a paid license can perform updates. Any premium module can only be updated with a valid license.

                                      • H

                                        I have paid licenses..

                                        • Regarding the Developer module, it's clear that the installation was not completed correctly. I suspect there may be an issue with folder and file permissions. You will likely need to fix the permissions and then uninstall and reinstall the module manually via SSH or PHPMyAdmin, directly through the database.

                                          • f you need to set the correct permissions for UNA CMS, run this command:

                                            Save as a file if you need further help to restore UNA permissions set_permissions.sh

                                            #!/bin/bash
# Filename: set_permissions.sh

# Move into the 'una' directory
cd una || { echo "Directory 'una' not found!"; exit 1; }

# Change the owner of all files and folders to 'www-data'
sudo chown -R www-data:www-data .

# Set permissions for all directories to 755:
# 7 = read (4) + write (2) + execute (1) for the owner
# 5 = read (4) + execute (1) for the group
# 5 = read (4) + execute (1) for others
sudo find ./ -type d -exec chmod 755 {} \;

# Set permissions for all files to 644:
# 6 = read (4) + write (2) for the owner
# 4 = read (4) for the group
# 4 = read (4) for others
sudo find ./ -type f -exec chmod 644 {} \;

# Give execute permission to ffmpeg.exe (since it's an executable)
sudo chmod +x ./plugins/ffmpeg/ffmpeg.exe

# Go back to the previous directory
cd ..

# Set this script's owner to 'root' and permissions to 755
# If you want, replace 'root' below with your SSH username
sudo chown root:root set_permissions.sh
sudo chmod +x set_permissions.sh

# Display confirmation message
echo "Permissions successfully set. Script permissions preserved."

                                            How to use:

                                            1. Create the file:
                                            vim set_permissions.sh
                                            1. Press i to enter Insert mode.
                                            2. Paste the code from above.
                                            3. Save and close:
                                            • Press ESC
                                            • Type :wq
                                            • Press Enter

                                            Final steps:

                                            • Make the script executable:
                                            sudo chmod +x set_permissions.sh
                                            • Run it anytime to restore your file and folder permissions:
                                            ./set_permissions.sh

                                            What this script does:

                                            • Sets the correct ownership (www-data:www-data) and permissions for your una/ project.
                                            • Makes sure ffmpeg.exe stays executable.
                                            • Preserves its own permissions as root:root with 755, so it’s always ready to use safely.

                                            Directory Structure

                                            your_project/
├── set_permissions.sh   ← This script is here
└── una/                 ← The UNA CMS directory

                                            Happy coding! 

                                            • H

                                              I am migrating another site (no content yet other than translations and some customizations on logo etc).. I managed to upgrade una to 15.0 and other modules except Channels.

                                              I re-did again from a backup and still the same result for Channels. It says there is an upgrade available. Clicking install does nothing.

                                              As per this page in unacms dot com wiki/Upgrade, I am supposed to see any errors in logs/upgrade_modules.log. But this file is not there.

                                              I only have upgrade.log inside logs folder and the contents are this.

                                              --------- 2025-10-12T06:21:49+00:00

14.0.0-15.0.0.A1 upgrade will be applied
Files permissions are ok and can be overwritten
Files copying successfully completed
Deprecated files were successfully deleted or there is no files to delete
System files hash was successfully updated
System SQL script was successfully executed
The following languages will be affected for system:
 - No languages will be affected

                                              • There is a new setting

                                                Studio > Settings > General > Community description

                                                You can set it to the empty string to have previous behaviour.

                                                • H

                                                  Just a heads up. You might have set "Automatic System Updates" in settings. But if your upgrade fails for any reason, this checkbox gets cleared (yes, its as per implementation).

                                                  My upgrade was failing due to this issue..

                                                  I had BX_DIRECTORY_PATH_ROOT configured inside inc/header.inc.php to the below value (note the private_html)

                                                  /home/username/domains/domain.tld/private_html/subfolder

                                                  But I was calling cron using the public_html path

                                                  /opt/alt/php83/usr/bin/php -q /home/username/domains/domain.tld/public_html/subfolder/periodic/cron.php

                                                  Though private_html is a soft link to public_html , and cron runs OK, but the upgrade results in error. "ERROR:Files copying failed"

                                                  So I printed the $sFilePathFrom, inside BxDolFile.php (the file is available inside temp folder during upgrade)

                                                  sFilePathFrom : /home/username/domains/domain.tld/private_html/subfolder//home/username/domains/domain.tld/public_html/subfolder/tmp/patch_14.0.0_15.0.0-A1/UNA-Patch-v.14.0.0-to-v.15.0.0.A1/files/14.0.0-15.0.0.A1/files/

                                                  This is an invalid directory (note the double // ). Somehow UNA is appending the paths in a strange way.

                                                  Changing my cron call solved it for me...

                                                  EDIT : Few additional details in the error logging would solve quiet a number of issues users are facing. Like invalid source directory xxxx given, permission denied for folder1 etc... The cryptic "ERROR:Files copying failed" was difficult to debug specially since this is printed by upgrade/classes/BxDolUpgradeUtil.php. That is magically appearing inside the temp folder only during upgrade :) Being inside temp folder did not help ;(

                                                  • H

                                                    Additional note - Increase your php max_execution_time to few minutes during the upgrade. I think (a wild guess) my earlier broken module upgrades (some modules remaining stuck) could be due to this.

                                                    • Hello @highlightings !

                                                      Did you have any limits to set the Cron Jobs the same as the main path with the private_html folder? Because commonly, both points should be equal.

                                                      • H

                                                        Maybe I understood your question wrong . But will make an attempt.

                                                        I have regular automated Cron that is using the base path. But for the upgrade, I was triggering it manually from terminal. So just ran the cron.php. Since it's a symlink, I assume it should not matter (?)..

                                                        But somehow una is appending the path as I have shown above.

                                                        • It seems yes, the symlink may distort the proper path of the script's run. So if you have the [somepath] in the BX_DIRECTORY_PATH_ROOT constant then it would be better to run Cron Jobs with this [somepath] too. But it is nice that you've detected it!

                                                          • Thanks! Yes, I found that item, but I don't understand what it's for — the description should be different on every page.

                                                            • @Ivan Mishchenko it was added by mistake, we're removing it now, thank you for noticing this.

                                                              Login or Join to comment.