This works for TYPO3 9:
Composer:
./vendor/bin/typo3 upgrade:list -a
./vendor/bin/typo3 upgrade:run <wizardName>
without Composer:
Same as Composer, but use different path:
./typo3/sysext/core/bin/typo3 upgrade:list
./typo3/sysext/core/bin/typo3 upgrade:run <wizardName>
As documented in Installation & Upgrade Guide: Upgrade Wizard (see also Reference Index for both Composer and non-Composer)
In TYPO3 8, shows no commands "upgrade", e.g.
./vendor/bin/typo3
output:
...
referenceindex
referenceindex:update Update the reference index of TYPO3
syslog
syslog:list Show entries from the sys_log database table of the last 24 hours.
How can you run these commands from CLI in TYPO3 8?
You can try the binary typo3cms.
The typo3cms binary is NOT part of the core. Its provided by the composer package helhum/typo3-console and includes the basic binary featurees plus some extra.
Call it like the typo binary => ./vendor/bin/typo3cms
Then you will get the following output for the upgrade option:
upgrade
upgrade:all Execute all upgrade wizards that are scheduled for execution
upgrade:checkextensionconstraints Check TYPO3 version constraints of extensions
upgrade:list List upgrade wizards
upgrade:wizard Execute a single upgrade wizard
TYPO3 also includes the binaries fluid and doctrine-dbal in the vendor/binfolder
Related
I have applied a patch AC-3022.patch in magento 2.4.3-p1, but it gives error: Patch is deprecated
https://experienceleague.adobe.com/docs/commerce-operations/release/notes/security-patches/2-4-3-p1.html?lang=en
https://i.stack.imgur.com/ZjUtS.png)](https://i.stack.imgur.com/ZjUtS.png
https://i.stack.imgur.com/Pqrad.png)](https://i.stack.imgur.com/Pqrad.png
Why is the patch deprecated?
Applied patch using following commands in magento root directory -
step 1 - composer require magento/quality-patches
step 2 ./vendor/bin/magento-patches apply AC-3022
You need to check the compatibility of your store version with the patch requirements; please specify the following things:
What's your Magento version
PHP version
As of Magento 2.4.4, the system requirement has been changed from PHP7.4 to PHP8.1
So, carefully upgrade the PHP version and apply the patch again.
I am following this tutorial to create my own plugin to grafana 6.7.3.
However, at the beginning I can see:
IMPORTANT: This tutorial is currently in beta and requires Grafana
7.0, which is scheduled for release in May. Some of the features mentioned may not work for earlier versions.
So, when I go to Configuration -> Plugins -> my-plugin, I get the following errors:
Error Loading Plugin
And:
This template is a starting point for building Grafana Panel Plugins
in Grafana 7.0+
I think it is because #next param to create the plugin:
npx "#grafana/toolkit"#next plugin:create my-plugin
But, I have tried to use with no #next param and with #6.7.3 and nothing did work.
npx "#grafana/toolkit" plugin:create my-plugin
npx "#grafana/toolkit"#6.7.3 plugin:create my-plugin
Is there any way to create plugin to 6.7.3 version?
I have Symfony 5 project and just following the instructions to install the DoctrineMongoDBBundle package, and I'm receiving te following error,
Attempted to load interface "CommandSubscriber" from namespace "MongoDB\Driver\Monitoring".
Did you forget a "use" statement for another namespace?
/vendor/doctrine/mongodb-odm/lib/Doctrine/ODM/MongoDB/APM/CommandLoggerInterface.php (line 9)
I have the following versions of mongodb and doctrine running.
doctrine/mongodb-odm-bundle": 4.1
mongodb/mongodb": 1.6
Also the php driver installed through Pecl (Version 1.7.4)
Anyone got any ideas to what I'm missing?
If it helps anyone in the future, whilst the MongoDB Driver was installed, I needed to restart PHP FPM, that fixed it.
On https://cloud.google.com/appengine/docs/python/ the runtime for the flexible python environment is said to be 3.6. However on https://cloud.google.com/appengine/docs/flexible/python/runtime it is said to be 3.7.
My build is reported to fail as it depends on a package that requires 3.7 (using gcloud app deploy). So at least my build is using 3.6.
Is this an error in the doc or is also 3.7 available in the flex env?
Update 1
Although the feedback says the default python3 interpreter in the flex env is 3.7, I did have following error when trying to deploy my app when dependent on a module that requires 3.7:
Step #1: <my-dep-module> requires Python '>=3.7' but the running Python is 3.6.8
When I remove that dependency and I build I also see 3.6 mentioned in the build output:
Step #1: ---> f186f86e42ea Step #1: Step 2/9 : LABEL python_version=python3.6 Step #1: ---> Running in 7b76fdee165b
Step #1: Removing intermediate container 7b76fdee165b Step #1: ---> 482717f31b28
Step #1: Step 3/9 : RUN virtualenv --no-download /env -p python3.6 Step #1: ---> Running in b1d15ba3568d
Step #1: Running virtualenv with interpreter /opt/python3.6/bin/python3.6
Thus somehow gcloud app deploy is building using 3.6 nevertheless?
You can set the Python interpreter's version to the latest supported Python 3.x release, which is currently 3.7.2, in the app.yaml file by specifying the runtime_config element like so:
runtime: python
env: flex
runtime_config:
python_version: 3
You could set it to other versions by specifying 3.6 or 3.5 as documented here but 3 at this time refers to 3.7.2.
You can set for App Engine flex any version you want in the app.yaml as you can see here. If you just mention 3 at :
runtime_config:
python_version: <version number>
It will take by default the latest version possible ( now, 3.7.2 )
When i try install and i have this error:
# composer require backpack/base
Using version ^0.7.3 for backpack/base
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for backpack/base ^0.7.3 -> satisfiable by backpack/base[0.7.3].
- backpack/base 0.7.3 requires laravel/framework 5.3.* -> satisfiable by laravel/framework[5.3.x-dev, v5.3.0, v5.3.0-RC1, v5.3.1, v5.3.10, v5.3.11, v5.3.12, v5.3.13, v5.3.14, v5.3.15, v5.3.16, v5.3.17, v5.3.18, v5.3.19, v5.3.2, v5.3.3, v5.3.4, v5.3.5, v5.3.6, v5.3.7, v5.3.8, v5.3.9] but these conflict with your requirements or minimum-stability.
Installation failed, reverting ./composer.json to its original content.
How fix that?
You're probably running a Laravel 5.2 app. If so, you have two options:
1) Upgrade from Laravel 5.2 to Laravel 5.3, then try again, it will most definitely work. The Laravel upgrade takes about about 1 hour for a medium-sized project, but you'll have all the benefits of using the latest and greatest (both Laravel and Backpack).
2) Install Backpack for Laravel 5.2, but please be aware you're running an old Backpack version and you won't be receiving any updates or new features.
My recommendation, of course, is option #1. In the end, you'll still need to update Laravel, then update Backpack, so it's best to just do it now.