-
It's 'normal' behavior of the site going into maintenance mode after an update. It saves the site from crashing after you did a site update and before you updated related version modules. You need to unlock your site by removing the auto-generated maintenance file in your web root folder, by using WebFTP or FTP. On a local installation just delete the file.
-
Hi Leonid.. unfortunately when I try to perform the upgrade via the update button, the first update to v13 produces the error:
bx_import fatal error: class (BxTemplEditorQuill) wasn't found in utils.inc.php on line 778
and does not proceed any further.
This is why I asked if I could perform manually or via patch files or similar?
-
Hi Leonid.. just wondering if I can proceed with another method to upgrade since the "bx_import fatal error" stops me from performing the upgrade in the normal way.
I'm accustomed to Linux CLI so if you know of a cli way to manually perform the upgrade, via the patch files or similar, please advise.
I'd imagine the process via the GUI just kicks off scripts on the back end to perform the upgrades from the Git.. so I should be able to do that manually or change my setup to avoid the "bx_import fatal error" prior to upgrade attempts?
-
Sorry, missed your reply here. So here you may find the solution to fix this step https://unacms.com/cmts-view/sthdkt?sys=bx_forum&cmt_id=45083
Comment to 'V12.1.0 installed, want to go to v13.1.0 only'