ETA for 4.20 is the middle of April
UPDATE:
ETA for BETA 4.20 is the end of April
ETA for 4.20 is the middle of May
UPDATE:
ETA for BETA 4.20 is the end of April
ETA for 4.20 is the middle of May
Great news!! Thanks.
Nopcommerce 4.20
Certified Developer
- 189
- 2395
- 2/9/2013
- United States
ChuckR wrote:
Hi Andrei,
I just noticed that the MySQL workitem was just dropped from 4.2 just as your about to release - and now it has a 4.3 tag. Is this accurate? Are you cancelling MySQL support for 4.2?
ETA for 4.20 is the middle of April
UPDATE:
ETA for BETA 4.20 is the end of April
ETA for 4.20 is the middle of May
Thanks Andrei,
That's good news! Were really looking forward to being able to cut SQL Azure Data Services cost and begin leveraging MYSQL over MSSQL for some clients. nopCommerce has typically needed a min S2 or S3 package (100 DTU) for some of our sites - which runs the price to $150 / database/ month. I noticed MYSQL is still a pending item on 4.2 so was hoping it wouldn't get dropped to hit the original date release. Were planning some costs cutting around that feature alone.
So far, 4.2 looks very good!
UPDATE:
ETA for BETA 4.20 is the end of April
ETA for 4.20 is the middle of May
Thanks Andrei,
That's good news! Were really looking forward to being able to cut SQL Azure Data Services cost and begin leveraging MYSQL over MSSQL for some clients. nopCommerce has typically needed a min S2 or S3 package (100 DTU) for some of our sites - which runs the price to $150 / database/ month. I noticed MYSQL is still a pending item on 4.2 so was hoping it wouldn't get dropped to hit the original date release. Were planning some costs cutting around that feature alone.
So far, 4.2 looks very good!
Hi Andrei,
I just noticed that the MySQL workitem was just dropped from 4.2 just as your about to release - and now it has a 4.3 tag. Is this accurate? Are you cancelling MySQL support for 4.2?
Team Member
- 16611
- 155790
- 10/22/2008
- Armenia
ChuckR wrote:
Hi Chuck,
Unfortunately, that's right. We've started working on this task and it was finished for PostgreSQL (MySQL could be implement almost the same way). Here is the branch. But we don't like source code quality. That's why we've decided to postpone and refactor it first. Maybe, we'll implement it a new branch for 4.20 later so our community can use it
I just noticed that the MySQL workitem was just dropped from 4.2 just as your about to release - and now it has a 4.3 tag. Is this accurate? Are you cancelling MySQL support for 4.2?
Hi Chuck,
Unfortunately, that's right. We've started working on this task and it was finished for PostgreSQL (MySQL could be implement almost the same way). Here is the branch. But we don't like source code quality. That's why we've decided to postpone and refactor it first. Maybe, we'll implement it a new branch for 4.20 later so our community can use it
- 68
- 386
- 3/7/2019
- India
Hello all,
Though I am software developer I am completely new to nopCommerce.
I want to use nopCommerce for my ecommerce website.
So, should I use 4.20 which is under development, or stick with 4.10?
What’s new in 4.20?
Or should I start using 4.20 and update it as get updates from development version from GitHub?
Which way to proceed please reply.
Though I am software developer I am completely new to nopCommerce.
I want to use nopCommerce for my ecommerce website.
So, should I use 4.20 which is under development, or stick with 4.10?
What’s new in 4.20?
Or should I start using 4.20 and update it as get updates from development version from GitHub?
Which way to proceed please reply.
Certified Developer
- 189
- 2395
- 2/9/2013
- United States
a.m. wrote:
Thanks Andrei,
A separate branch would be great or having it as one of the very first changesets in 4.3 Dev branch so it can be easily back-ported to 4.2 without breaking 4.2 plugins would be a huge win.
As always, we appreciate your hard work, and looking forward to 4.2 release.
thx
I just noticed that the MySQL workitem was just dropped from 4.2 just as your about to release - and now it has a 4.3 tag. Is this accurate? Are you cancelling MySQL support for 4.2?
Hi Chuck,
Unfortunately, that's right. We've started working on this task and it was finished for PostgreSQL (MySQL could be implement almost the same way). Here is the branch. But we don't like source code quality. That's why we've decided to postpone and refactor it first. Maybe, we'll implement it a new branch for 4.20 later so our community can use it
Hi Chuck,
Unfortunately, that's right. We've started working on this task and it was finished for PostgreSQL (MySQL could be implement almost the same way). Here is the branch. But we don't like source code quality. That's why we've decided to postpone and refactor it first. Maybe, we'll implement it a new branch for 4.20 later so our community can use it
Thanks Andrei,
A separate branch would be great or having it as one of the very first changesets in 4.3 Dev branch so it can be easily back-ported to 4.2 without breaking 4.2 plugins would be a huge win.
As always, we appreciate your hard work, and looking forward to 4.2 release.
thx
- 50
- 298
- 8/2/2017
- United States
a.m. wrote:
So would PostgreSQL be a viable option to use with version 4.2?
I just noticed that the MySQL workitem was just dropped from 4.2 just as your about to release - and now it has a 4.3 tag. Is this accurate? Are you cancelling MySQL support for 4.2?
Hi Chuck,
Unfortunately, that's right. We've started working on this task and it was finished for PostgreSQL (MySQL could be implement almost the same way). Here is the branch. But we don't like source code quality. That's why we've decided to postpone and refactor it first. Maybe, we'll implement it a new branch for 4.20 later so our community can use it
Hi Chuck,
Unfortunately, that's right. We've started working on this task and it was finished for PostgreSQL (MySQL could be implement almost the same way). Here is the branch. But we don't like source code quality. That's why we've decided to postpone and refactor it first. Maybe, we'll implement it a new branch for 4.20 later so our community can use it
So would PostgreSQL be a viable option to use with version 4.2?