How could I install sylius components in Symfony 3 ?
I'm trying to install SyliusOrderBundle in symfony 3 with composer but always return an error. is there any way to install this component in symfony 3?
Probably because you are getting version constraint ^0.18 installed, which is released halfway 2016 and therefore rather old. It's not compatible with the latest Symfony version.
To get the latest version from the master branch (warning: this might be unstable): composer require sylius/order:dev-master. Normally I wouldn't advice this, but tomorrow version 1.0 of Sylius will be released, so this should be fairly safe today if you upgrade tomorrow to version 1.0.
If you want the lastest beta version that is released: composer require sylius/order:^1.0.0#dev. This results in version of some weeks ago, which should be ok to get your project starting with I think.
Related
I've been to the Releases site for mod_auth_openidc and brought down the rpm. And attempting to install requires cjose but attempting to find and install that poses a problem as it seems to incorrectly test the version of jansson (e.g., 2.10 is though to be less than 2.3). Most of the documentation I find is years old. Trying to use yum brings in a very outdated version of the mod_auth_openidc (1.8.8) that fails to allow apache httpd to load if you have an OIDCDirectURL coded.
I'm trying to configure Apache HTTPD to call out to an OAUTH2 Server I've created but I can't get the old mod to work and I'd love to know where I can get the piece parts to allow the latest version to install. There are some old downloads on the Releases site if you page back to 2.0 but the libcjose0 is not an rpm.
Do I need to retrieve the dependencies from their github and build them? If someone has done this already and posted the assets I'm happy to retrieve them. I'm surprised RHEL 7 repos don't have the latest (or newer) versions of the mod_auth_openidc.
The version issue reported when trying to install cjose is a red herring. Based on this site I found I needed to install jansson-devel to get past the errant warning about versions.
Going here allowed me to retrieve a fairly recent version of cjose-0.5.1-1.el7.centos.x86_64.rpm which installed without complaints once jansson-devel was installed.
I was then able to install mod_auth_openidc-2.4.9-1.el7.x86_64.rpm from the github repo releases
I am now able to start apache httpd with the OIDCRedirectURI entry in httpd.conf
I am trying to upgrade from Typo3 6.2 to a later version (to be determined). When I run the Core Update in the install tool the 'Fetched list of released versions' works, however, it is then followed by a 'General error'. In the log, this is the error:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1380898792: No version matrix found in registry, call updateVersionMatrix() first. | TYPO3\CMS\Install\Service\Exception\CoreVersionServiceException thrown in file /home/usr/public_html/typo3/sysext/install/Classes/Service/CoreVersionService.php in line 271. Requested URL: https://domain.dev/typo3/sysext/install/Start/Install.php?install[action]=importantActions&install[context]=backend&install[controller]=tool&install%5Bcontroller%5D=ajax&install%5Baction%5D=coreUpdateIsUpdateAvailable&_=1608549770287
I have looked around for ages and can't find a fix that works. I will be very grateful for any help, please.
I don't think that you can update such an old Version by the install-tool update mechanism any more. since that version a lot has changed.
newer versions of 6.2 are only available as paid service (ELTS) from the TYPO3 GmbH.
And I think the server structure also changed meanwhile so that old ULRs might fail.
your way of update should be a manual update to (any outdated version of) 7 LTS, then the same for 8 LTS until you come to 9 LTS and 10 LTS
on each version do the upgrade wizards and fresh up the extensions if possible (including the upgrade wizards of the extensions).
individual extensions need their own updates.
use the deprecation log on each version to identify possible failures for the next TYPO3 version.
somewhere between you might change the installation to composer installation, which will result in a cleaner update way (if you are familiar with composer). for the future it will be very helpful to understand composer.
I upgraded the mettermost version from 4.4.1 to 4.5.
However, I got the error...
So, I tried to downgrade the version to 4.4.1, but the mattermost said "The database schema of the older version isn't supported".
Does anyone know how we should modify the database schema.
※browser: FireFox ESR 52
Unfortunately you can't downgrade a Mattermost install to a previous version through any officially supported path. You will need to revert to the database backup from before the upgrade in order to go back to version 4.4.
However, for the specific versions in question (reverting from 4.5 to 4.4) it is possible to do a downgrade as there are no database schema changes between these two versions. You will need to run the following SQL command in your Mattermost database:
UPDATE Systems SET Value='4.4.0' WHERE Name='Version';
You should then be able to run Mattermost 4.4.1 successfully on that database.
appixia's cartAPI is best solution I have found on web for webservice.
Git Source
I am Using same API's for Prestashop from last 1 year for 1.5 version.
Now I have upgraded my prestahop version from 1.5 to 1.6 with latest one. After upgrade I have installed same cartAPI module from Git source but it's not working as they mentioned in it's supported version document,
Prestashop 1.5.x - Tested on 1.5.0.17 through 1.5.3.1
Can anybody help me why this is not working?
Is there anyone who can upgrade this API to work with 1.6 version?
Requested to GIT
Now if I have to try for upgrade what type of changes have to make, please
give suggestions.
Since MT 4 version still has some bugs for WCF services, I would downgrade it to 3.2.6.
I've recovered this old version but now it doesn't work because I have a more recent mono-framework version. What steps do I have to follow for disinstalling mono-framework 2.10.1_3 and recovering the old one?
Thank you. Regards.
Update: For those interested in, rembember to uninstall previous mono version. See this link: Uninstall Mono
Old mono-framework will recognize, that you are installing an older version over an newer one and prompt you to continue