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.
Related
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.
when installing Zabbix v3.4 I get the following error message: http://imgur.com/a/xo3tg
Looks like an error in the yum repository. Do you have any suggestions for solutions or something similar?
Best regards
As you can see, there is just 2.2 version of Zabbix (agent, server, proxy, etc.) in that repository.
It seems Zabbix 2.2 (LTS) is the latest version supported by OpenSUSE using its repositories.
By the way, you can install older versions of Zabbix-agent (like 2.2) sending data correctly to newer server/proxy versions (like 3.0 or even 3.2).
I think the major item you will miss with using zabbix-agent older than 3.X is encryption. Other major features work very good.
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.
I'm trying to install Eclipse Kepler (4.3) IDE with Bazaar version control system integration on a CentOS 6.5 machine. Everything seems perfect, until I restart the IDE and want to use bazaar. It asks for xmloutput >= 0.9.2 but according to this page the latest version available is xmloutput 0.8.8
I have tried to install bzr-eclipse 1.3 or 1.2 but all the links in Eclipse are just for the latest version.
Does anybody know how to install a previous version of bzr-eclipse or how to use a correct version of xmloutput?
This problem seems to be very close to this question (resolved by upgrading to a newer version of Bazaar).
Is it correct that the DB-scripts in $WSO2_AM_HOME/dbscripts, only contains migration scripts until version 1.5?
Can we assume that WSO2-AM 1.6 db-repository is the same as version 1.5?
You need to upgrade the databases when migrating from APIM 1.5 ->1.6. You can find the migration scripts and the readme file from [1].
Seems,the relevant scripts has not been included to APIM 1.6.0 packs and created [2] to track this.
[1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.6.0/modules/distribution/resources/migration-1.5.0_to_1.6.0/
[2] https://wso2.org/jira/browse/APIMANAGER-1969
Thanks;
/Lalaji