Is there a chart/statistic which versions of Shopware 6 are used by online shops actually.
Background: developing custom plugins, it's hard to cover all versions from 6.1 - current (6.4)
I would suggest supporting the releases since the latest major release 6.4, which has first been released 1 1/2 years ago. That's ample time for users to have updated to one of the minor releases since then. When you offer plugins in the community store you'll get an overview which Shopware versions your plugin is used with. Looking at the data of my plugins I can tell you that the vast majority is now at 6.4. Without breaking changes it should not be a problem supporting all 6.4 releases and with the 6.5 major release coming next year you should be able to cover a significant userbase by supporting both the upcoming and the current major release.
Related
We are still running Magento community version 2.3.4x.
We are upgrading since 4 months to current version, there were many plug-ins not compatible and so on.
Now we are about 2-3 weeks before we can fully switch.
On 11. of Oct. Adobe released:
Security update available for Adobe Commerce | APSB22-48
https://helpx.adobe.com/security/products/magento/apsb22-48.html
But our version of out of service since one month.
So we can not switch now, and there is also no patch.
Adobe Commerce 2.4.5 and earlier versions
What can we do until then?
I know this is not an adequate question here, but since It will probably affect 60% of all Shop worldwide, it's necessary to ask this here.
Maybe try this: https://github.com/EmicoEcommerce/Magento-APSB22-48-Security-Patches
This repository contains Magento 2 Patch Files for the recently found security issues on 12-10-2022. The patch files aim to fix the CVE-2022-35698 and CVE-2022-35689 vulnerabilities.
I have included the PHP Stripe lib version 4.4.0 into my Slim Framework setup version 2.4.2. PHP version 5.4.16.
I autoload in the library using require ("../vendor/autoload.php");
However when I call:
\Stripe::setApiKey($this->stripeKey);
$customer = \Stripe\Customer::create(array(
'email' => $email,
'card' => $token
));
I get the error "Class 'Stripe' not found" I think its to do with the Slim Framework not integrating with Stripe.
I have downloaded https://github.com/collegeman/slim-common which is a Slim project that has Stripe integrated and that works ok, but I am looking to update the Stripe library to 4.4.0 (its latest version)
Update
When I remove "namespace Stripe;" from the stripe/stripe-php/lib/Stripe.php it proceeds to say "Class 'Stripe\Stripe' not found in /vendor/stripe/stripe-php/lib/ApiResource.php on line 16"
Looking at the documentation usage looks like the following:
\Stripe\Stripe::setApiKey($this->stripeKey);
I think this is a PHP version issue.
The recent versions of Stripe require PHP >= 5.6.0, see the documentation here on GitHub.
A few months ago, I attempted to install a slightly earlier version of Stripe (whatever was newest then) with PHP 5.4.16 and it generated the same exact error message.
I think you may need to upgrade PHP. Alternatively, you could try using an older version of Stripe that supports PHP 5.4. However this would not be a good solution; PHP 5.4 has reached end-of-life as of September 2015, a long time ago, and as a result may have a long list of concerns associated with it. Back when I was running PHP 5.4, over the past few years, I have run into a long list of problems with it, including it not working with newer software packages, and not supporting modern best-practices with respect to cryptography and other security measures. Even if you manage to get Stripe working here, you may run into other problems down the line, perhaps with Stripe, or perhaps with other software packages, security, etc.
At a bare minimum I recommend upgrading to 5.6, but as that version has already reached end-of-life too (December 2018) an actively-supported version such as 7.3 or greater would be better. I upgraded to 7.4 which is supported through November 2022 and will likely be supported for Stripe much longer than that, and it fixed the problem here, as well as a variety of other unrelated problems I had been having, although I did need to rewrite quite a lot of code in order to do the migration.
We have SAP Hybris Commerce version 5.1.1 with custom extensions installed. Now we need to upgrade it to newest version 6.2.
My question is: Can we upgrade it to 6.2 and skip all versions between 5.1 and 6.2? Or must it be done by upgrading to 5.2, then to 5.3 and so on?
Yep - 5.1.1 to 6.2 ought to work (I've been working on a project that's done exactly this).
You will probably have to make some changes - watch out for any customisations you've made - it might be worth reading through the release docs to have an idea of what's changed - off the top of my head the structure of add ons is one area that's a bit different between 5.1 and 6.2, but otherwise things should work OK in theory.
Yes you can directly update to 6.2.
It's important to regulary update your hybris version. You should not have so much gap with current version. Indeed it become tougher to migrate your custom code.
Upgrading each minor version in a row is totally useless most of the time. Only do this if you have issues you can't solve while migrating to the target version.
You should take a look at this migration documentation and this guide (it can be used even if it doesn't match your version).
Note that some stuff like promotion are totally different in hybris 6 so you can expect some trouble to migrate everything. Take care of your extensions generated with old template also.
5.5.1 introduces JDK8 and Spring 4, I would not underestimate this change! Depending on the size of your project I would first go for 5.5.1. Also notice the MySQL change for 6.2 (5.6). Don't forget to declare deployment tables in your items.xml. Search for "third-party compatibility" and "release notes" on the wiki. Also try shifting to the backoffice since the hMC is marked as deprecated.
Yes you can migrate directly 6.2.
The time and difficulty depends on your custom code (and how much it respects good practices : naming conventions, usage of service, architecture respect...etc)
You might also consider that HMC is deprecated in 6.2
I would like to ask a question about wether or not I should do the migration to Liferay 6.2.
Me and my team are working since 4 month on a portal quite big developed with Liferay 6.1 (CE edition) and now, since the project publication date is still 4-5 month ahead (so I do have time), I was wondering if doing the migration to 6.2 now is a good choice.
I already tried the new version and I must say I am impressed about the new features and since now I haven't find any bugs.
Anyone had any experience on developing portlet/themes on Liferay 6.2? Is is worth it to do the migration now or shall I wait for the next ga2 release?
Any suggestion is very welcome.
Thanks
Depends mostly on the kind of work you've done on that portal. Even slight upgrades in Liferay, can have major differences in the source code. If this affects the work you've done, it will affect the upgrade too. For example, things will get difficult to update if :
You have developed custom portlets, as they will need recompilation for the new runtime
Developed Portlets that use ServiceBuilder might need more work than just a recompilation
Using Hooks (even simple jsp hooks) might need re-writing. ext hooks will almost certainly need to, and it can become a major pain
On, the other hand, if most of your work had to do with light theming and content management, it could become an relatively easy and painless upgrade.
In any case, make sure to keep a backup of your Liferay Database, because once you upgrade, there is no way to downgrade back to the initial version.
As you're using CE, my recommendation is to upgrade as soon as possible. Reason is that there are no more updates for 6.1, now that 6.2 is out. If you're going live in 5 months, you'd be on a version that's unsupported for half a year at the date of publication.
The alternative is to go to EE, which is supported for ~5 years from release, e.g. you'll have several years of support in front of you. However, as Liferay is paying my salary, note that I might be biased...
Of course, being unsupported "by Liferay" does not mean that you won't be able to fix any bugs or issues, but you'll have to do this on your own, and sooner or later you should upgrade anyway... If you're not yet live, I'm recommending to do it sooner.
Liferay 6.2 does not (yet) support as many marketplace apps as Liferay 6.1. Also Liferay 6.2 CE has bugs, and patches are available only to EE subscribers; this forced us to use Liferay 6.1 CE instead of 6.2 CE.
You will have issues if you are using the Vaadin framework under Liferay.
Liferay 6.2 CE does not support Vaadin out of the box ... it is delivered with Vaadin 6.8, but it is broken - your portlet code will break.
You would have to consider moving to Vaadin 7.1 at best ... and that is a non-trivial code migration as many items have been deprecated between 6.8 and 7.
I went that route and the learning curve was unexpectedly steep.
I have a project built around Subsonic 3.0.0.3 and have run into the dreaded medium trust issue, can anyone tell me is there a way I can mod the code myself to get this working or what the expected timescale for 3.1 version is? Its looking increasingly like I will have to ditch subsonic to get my system running
Regards
Mike
No timeframe for SubSonic 3.1 (or 3.0.0.4), but here are the current plans: http://groups.google.com/group/subsonicproject/browse_thread/thread/caae09418ce4d975/
The SubSonic Google discussion group is the best place to find out about the current development happenings for SubSonic.
Short answer, as soon as possible.
Long answer, there's a number of things planned for 3.1 these include (but are not necessarily limited to):
Oracle support
MediumTrust support
Automatic mapping of collections in SimpleRepository
These are all in development right now but before they become the main focus we need to get version 3.0.0.4 out the door with fixes for a lot of the outstanding issues listed on github. There's also a lot of more boring work going on behind the scenes which should make regular and stable releases easier.
The current release schedule is:
Version 3.0.0.4 - 22nd March 2010
Version 3.1 - 22nd May 2010