I am new to TYPO3 and tried to install the official introduction package.
I found the package in the extension manager and clicked install but got the following message:
Could not install distribution 'bootstrap_package'
Your TYPO3 version is lower than this extension requires. It requires TYPO3 versions 6.2.14 - 7.99.99
I am using TYPO3 version 6.2.11.
I installed the system via docker TYPO3-docker-boilerplate.
I think this tool uses composer to get the TYPO3 base distribution.
I tried the upgrade wizard but there was no option to choose a specific version to upgrade to. So how can I upgrade TYPO3 to version 6.2.14?
I need to use version 6.2.
Unfortunately, the cms-base-distribution Composer package hasn't been updated since March. So you have to set the typo3/cms package in the composer.json file to the version you need (latest stable version of 6.2 is 6.2.15). The file is located in the code directory.
Then run composer update in the same directory.
This should update one dependency and the cms package itself:
- Removing helhum/class-alias-loader (1.0.99)
- Installing helhum/class-alias-loader (1.1.5)
Downloading: 100%
- Removing typo3/cms (6.2.11)
- Installing typo3/cms (6.2.15)
Downloading: 100%
Related
I have ClamAV server version 0.103.5 installed on a RHEL 8.5.
When I run freshclam it says:
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.103.5 Recommended version: 0.103.6
However, when I go to the ClamAV downloads page (https://www.clamav.net/downloads), I see that the latest RPM version is clamav-0.105.0.linux.x86_64.rpm.
My assumption is the the freshclam commands only refers to the same major version.
But if I follow the link from ClamAV page to the prebuilt packages for RHEL/Fedore (https://src.fedoraproject.org/rpms/clamav), it lists 0.103.6 as the latest available version.
So, can I install version 0.105.0 from ClamAV or must I use only official Fedora/RHEL packages?
I am installing Auctane-ShipStation module for Magento 2.3.4 by referring the following site https://help.shipstation.com/hc/en-us/articles/360025855652-Magento#connect-a-magento-store-to-shipstation-0-1.
There is no option to directly download the shipstation module. They are asking to install it via composer. I am using " composer require auctane/api:2.2.9 " command to install it but it is giving error " [InvalidArgumentException] Could not find a matching version of package auctane/api. Check the package spelling, your version constraint and the package is available in a stability which matches your minimum-stability( stable). "
Open your composer.json if that package has no stable version then you have to change your minimum-stability to dev.
https://getcomposer.org/doc/04-schema.md#minimum-stability
After cloning & while doing composer update I am getting the error :
Installation request for zofe/rapyd dev-master
Conclusion: don't install intervention/image 2.4.2
.......
......
......
I am using xampp 7.2.8 , composer 1.7.1, Windows 10 in Virtualbox.
I have cloned the created database, but unable to run the composer update or php artisan migrate as mentioned in https://github.com/raylight75/cms#official-documentation .
Could someone help me ?
I have posted the same issue in https://github.com/raylight75/cms/issues/8
From the composer log you've posted, it looks like the package you are trying to install zofe/rapyd#dev-master is not compatible with the version of Laravel you're using.
The log you've posted also differs to the error you've posted in your question. There is no mention of intervention/image in the logs. Instead, the log is showing an issue with laravelcollective/html and nesbot/carbon.
Try installing the latest stable version by updating the composer.json file and changing the version from dev-master to ~2.2. The latest stable version is v2.2.7, while version 2.6.3 is pre-release, but supports Laravel 5.6.
The issue may also be fixed by updating your version of Laravel to v5.6. However, this is likely to be more work than just using a lower version of zofe/rapyd.
I am trying to install Zend Framework 3 in Windows 7. I downloded the Skeleton from Git and run composer install. But getting the error
[UnexpectedValueException] Invalid version string "^1.1.0".
Details:
PHP Version 5.6.3,
XAMPP Version 5.6.3
I'm not sure what command you ran and why you downloaded the skeleton. The preferred way to install the skeleton is with composer:
composer create-project zendframework/skeleton-application path/to/install
More info can be found on https://framework.zend.com/downloads/skeleton-app
RavenDb latest version is installed as a nuget package. It references Newtonsoft.Json 4.0.2.
I'm trying to install TweetSharp. I get this log:
M> Install-Package TweetSharp
Attempting to resolve dependency 'Hammock (≥ 1.2.3)'.
Attempting to resolve dependency 'Newtonsoft.Json (≥ 4.0.1)'.
Successfully installed 'Hammock 1.2.6'.
Successfully installed 'Newtonsoft.Json 4.0.3'.
Successfully installed 'TweetSharp 2.0.8'.
Install failed. Rolling back...
Install-Package : Updating 'Newtonsoft.Json 4.0.2' to 'Newtonsoft.Json 4.0.3'
failed. Unable to find a version of 'RavenDB-Embedded' that is compatible with
'Newtonsoft.Json 4.0.3'.
As you can see, even if TweetSharp just needs 'Newtonsoft.Json (≥ 4.0.1)', nuget wants to install version 4.0.3 which can not work with RavenDb.
I tried to install previous versions of TweetSharp but it does not change anything.
Any way to circumvent this?
Sounds like a possible bug in NuGet. Please log an issue in the NuGet bug tracker: http://nuget.codeplex.com/workitem/list/basic
If TweetSharp is fine with NewtonSoft.Json 4.0.2, then the install should not have failed. In your bug, can you post the exact versions that caused this problem. For example:
List of installed packages with exact version installed.
List of dependencies for each package and the specific version range they specify.
And the exact version of TweetSharp you're trying to install. That'll help us look at the issue more quickly. Thanks!
My guess is we have some default logic that tries to upgrade packages to the latest bug fix release. In this case, we tried that, but it causes another dependency to fail. In that case, we should have known that and not tried to upgrade.
This is down to the semantic versioning that NuGet has had since (I think) 1.6. It's explained in more detail here but the basic idea is that if your dependency hasn't updated either the major or the minor revision number then they'll assume that it's a bugfix and not a breaking change.
So in this case the decision to install 4.0.3 instead of 4.0.1 was made.
You can run install-package with -ignoredependencies I would have thought that if you'd had 4.0.2 installed it wouldn't try to update you (because 4.0.2 satisfies the dependency).