Hi,
my Una is running for years, version is 12.1.0.
In panel it shows "UNA 13.1.0 is available" but no update button.
When I switch in Developer to beta channel it shows 14.A2 and a upgrade button, but I like to stay with the version 13. But how do I achieve it then?
PS: yes my cronjobs running every minute
Comments
T
Can I update it by simply uploading the single files via FTP? How do I run the database upgrade then?
Hello @trunky !
No, this is a bad way to upgrade UNA in other ways except via Studio. This is a correct case that you see info about 14.0.0-A2 version now because the beta channel shows all available beta versions for there. As the jump to 13.0 had many intermediate steps (and for every module), the cumulative upgrade between 12.1 to 13.0 isn't available. So you need to backup your UNA files and Database and upgrade all available stages like 12.1 - 13.0.0.A1 - 13.0.0.A2-13.0.0.A3-13.0.0.B1 (and upgrade all modules in every stages too - just follow the appearing instructions).
T
Ok I tried and have to say it's pretty weird behaviour.
I've enable beta channel in developers module, it stated it will update to 14.0.A1. Ok, clicked on update and then it update to all the version mentioned. So why not doing this when displaying the stable?
I planned to stop on 13.1.0 then but at 13-RC3 I get a "Site is temporarily unavailable due to scheduled maintenance, please try again in a minute." message now, so I got stalled. Nothing in the logs, neither server side nor from Una. Only one warning from AqbBannersModule, that's it.
Update: I am on 13.1.0 now, had to remove the _bx_maintenance file and all went well from there on.
It seems for some reason your hosting rules didn't allow to rename/delete the file in the UNA's root. As you did it manually and didn't forget to update all installed modules then the upgrade can be considered as completed.
If I read this right, all A and B upgrades need to be made to get to the stable version? Therefore I might as well just stay with Beta channel in developer module and ride the problems as they occur. Very two steps forward and three steps back.
So all serious users become 'bug testers'. Awesome.
📷 Michel - 🌎 Meta-Travel 🌴 Community Hub
T
One doesn't have to actually "use" the A, B and RC version, just need to go through all them during the update process.
T
and as update, the Studio works fine, the frontend seems to work only the main categories (listing profiles, groups etc) but for all "deeper" links I get a spinning cursor and after some timeout a blank page or 503 :(
Logs only show warnings
AH01071: Got error 'PHP message: PHP Warning: Undefined array key 0 in /var/www/vhosts/xyz.com/httpdocs/cache/bx_templ_de_artificer_919122ca265e8463e5ce6c4be2905c89.php on line 2; PHP message: PHP Warning: Trying to access array offset on null in /var/www/vhosts/xyz.com/httpdocs/cache/bx_templ_de_artificer_919122ca265e8463e5ce6c4be2905c89.php on line 2; PHP message: PHP Warning: Undefined array key 0 in /var/www/vhosts/xyz.com/httpdocs/cache/bx_templ_de_artificer_919122ca265e8463e5ce6c4be2905c89.php on line 3; PHP message: PHP Warning: Trying to access array offset on null in /var/www/vhosts/xyz.com/httpdocs/cache/bx_templ_de_artificer_919122ca265e8463e5ce6c4be2905c89.php on line 3; PHP message: PHP Warning: Undefined array key 0 in /var/www/vhosts/xyz.com/httpdocs/cache/bx_templ_de_artificer_919122ca265e8463e5ce6c4be2905c89.php on line 5; PHP message: PHP Warning: Trying to access array offset on null in /var/www/vhosts/xyz.com/httpdocs/cache/bx_templ_de_artificer_919122ca265e8463e5ce6c4be2905c89.php on line 5'
EDIT: here is a real error:
AH01071: Got error 'PHP message: PHP Fatal error: Uncaught Error: Call to a member function addMarkers() on false in /var/www/vhosts/xyz.com/httpdocs/modules/base/general/classes/BxBaseModGeneralMenuViewActions.php:65\nStack trace:\n#0 /var/www/vhosts/xyz.com/httpdocs/inc/classes/BxDolMenu.php(123): BxBaseModGeneralMenuViewActions->addMarkers()\n#1 /var/www/vhosts/xyz.com/httpdocs/template/scripts/BxBaseMenu.php(25): BxDolMenu->__construct()\n#2 /var/www/vhosts/xyz.com/httpdocs/modules/boonex/artificer/data/template/system/scripts/BxTemplMenu.php(17): BxBaseMenu->__construct()\n#3 /var/www/vhosts/xyz.com/httpdocs/template/scripts/BxBaseMenuMoreAuto.php(33): BxTemplMenu->__construct()\n#4 /var/www/vhosts/xyz.com/httpdocs/template/scripts_templ/BxTemplMenuMoreAuto.php(17): BxBaseMenuMoreAuto->__construct()\n#5 /var/www/vhosts/xyz.com/httpdocs/template/scripts/BxBaseMenuCustom.php(18): BxTemplMenuMoreAuto->__construct()\n#6 /var/www/vhost...'
Yes, you're right. The upgrade from 12.1 to 13.0 will drive via the beta channel only. With the disabled auto-upgrade you may leave it in the settings.
T
Have my community offline for awhile cause there is still that error
AH01071: Got error 'PHP message: PHP Fatal error: Uncaught Error: Call to a member function addMarkers() on false in /var/www/vhosts/xyz.com/httpdocs/modules/base/general/classes/BxBaseModGeneralMenuViewActions.php:65\nStack trace:\n#0 /var/www/vhosts/xyz.com/httpdocs/inc/classes/BxDolMenu.php(123): BxBaseModGeneralMenuViewActions->addMarkers()\n#1 /var/www/vhosts/xyz.com/httpdocs/template/scripts/BxBaseMenu.php(25): BxDolMenu->__construct()\n#2 /var/www/vhosts/xyz.com/httpdocs/modules/boonex/artificer/data/template/system/scripts/BxTemplMenu.php(17): BxBaseMenu->__construct()\n#3 /var/www/vhosts/xyz.com/httpdocs/template/scripts/BxBaseMenuMoreAuto.php(33): BxTemplMenu->__construct()\n#4 /var/www/vhosts/xyz.com/httpdocs/template/scripts_templ/BxTemplMenuMoreAuto.php(17): BxBaseMenuMoreAuto->__construct()\n#5 /var/www/vhosts/xyz.com/httpdocs/template/scripts/BxBaseMenuCustom.php(18): BxTemplMenuMoreAuto->__construct()\n#6 /var/www/vhost...'
Profiles and Discussion post display are not working, giving a blank page with that error.
One other result here in search was from 2019 someone who had problems with the timeline, but didn't see any change with Timeline removed or reinstalled.
@trunky could you please specify your UNA version and version of your Artificer app? Also is any circumstance which cased this error ?
UPDATE: the reason was in that fixed for 14.0 bug https://github.com/unacms/una/issues/4586