nopCommerce 4.10 BETA released. Please share your impressions
- 10
- 70
- 9/18/2017
- Denmark
nopAdvance wrote:
Thank you :)
I remember to have read somewhere in the posts that when EF Core supports lazy load, and so it does in 2.1 it will be implemented in nopCommerce.
I would have thought that this time was now?
Can someone elaborate a bit on that? :)
Hello
Can someone confirm that MS SQL can be interchanged with another DB-engine in this .NET Core release?
Cheers
Janus
Hi,
No this is not possible in this release.
Thank you,
Atul
Can someone confirm that MS SQL can be interchanged with another DB-engine in this .NET Core release?
Cheers
Janus
Hi,
No this is not possible in this release.
Thank you,
Atul
Thank you :)
I remember to have read somewhere in the posts that when EF Core supports lazy load, and so it does in 2.1 it will be implemented in nopCommerce.
I would have thought that this time was now?
Can someone elaborate a bit on that? :)
- 9
- 55
- 5/24/2013
- United States
FYI if you are getting "HTTP Error 502.5 - Process Failure" after deploying your code to a Windows 2016 Server on Azure:
https://github.com/nopSolutions/nopCommerce/issues/3166
https://github.com/nopSolutions/nopCommerce/issues/3166
- 174
- 1361
- 4/14/2011
- Ukraine
Thank you, that's helpful. Here are some more general ASP.NET Core startup troubleshooting / debugging tips
https://odetocode.com/blogs/scott/archive/2018/07/16/7-tips-for-troubleshooting-asp-net-core-startup-errors.aspx
https://odetocode.com/blogs/scott/archive/2018/07/16/7-tips-for-troubleshooting-asp-net-core-startup-errors.aspx
- 3
- 25
- 7/13/2018
- United States
I love nopCommerce! However, 4.1 breaks almost every single plugin I have. All the ones I bought that I do not have source code for are causing major issues specifically since they reference the BaseNopModel.cs. Most plugins I am finding that rely on this must be updated. My own custom plugins I was able to update, however the ones I have purchased do not work in this upgrade.
This commit caused the problem: https://github.com/nopSolutions/nopCommerce/commit/00ce73a42a83ce101c24aad5a87ea86f1b5bfbb2
This commit caused the problem: https://github.com/nopSolutions/nopCommerce/commit/00ce73a42a83ce101c24aad5a87ea86f1b5bfbb2
Silver Solution Partner
Certified Developer
- 332
- 2270
- 3/2/2018
- Norway
breaker05 wrote:
They will break unless they are upgraded to 4.1. If you purshased the plugins you will have to wait for a 4.1 version.
I love nopCommerce! However, 4.1 breaks almost every single plugin I have. All the ones I bought that I do not have source code for are causing major issues specifically since they reference the BaseNopModel.cs. Most plugins I am finding that rely on this must be updated. My own custom plugins I was able to update, however the ones I have purchased do not work in this upgrade.
This commit caused the problem: https://github.com/nopSolutions/nopCommerce/commit/00ce73a42a83ce101c24aad5a87ea86f1b5bfbb2
This commit caused the problem: https://github.com/nopSolutions/nopCommerce/commit/00ce73a42a83ce101c24aad5a87ea86f1b5bfbb2
They will break unless they are upgraded to 4.1. If you purshased the plugins you will have to wait for a 4.1 version.
- 3
- 25
- 7/13/2018
- United States
hkreklame wrote:
That's exactly what I said above. The ones I have bought break because they do not support the new code changes and is an issue for most people who have purchased plugins. I was reporting this for others on how to fix if they have the source code themselves.
I love nopCommerce! However, 4.1 breaks almost every single plugin I have. All the ones I bought that I do not have source code for are causing major issues specifically since they reference the BaseNopModel.cs. Most plugins I am finding that rely on this must be updated. My own custom plugins I was able to update, however the ones I have purchased do not work in this upgrade.
This commit caused the problem: https://github.com/nopSolutions/nopCommerce/commit/00ce73a42a83ce101c24aad5a87ea86f1b5bfbb2
They will break unless they are upgraded to 4.1. If you purshased the plugins you will have to wait for a 4.1 version.
This commit caused the problem: https://github.com/nopSolutions/nopCommerce/commit/00ce73a42a83ce101c24aad5a87ea86f1b5bfbb2
They will break unless they are upgraded to 4.1. If you purshased the plugins you will have to wait for a 4.1 version.
That's exactly what I said above. The ones I have bought break because they do not support the new code changes and is an issue for most people who have purchased plugins. I was reporting this for others on how to fix if they have the source code themselves.
- 10
- 70
- 9/18/2017
- Denmark
breaker05 wrote:
Can you mention a few of the plugins, before I upgrade :)
I love nopCommerce! However, 4.1 breaks almost every single plugin I have. All the ones I bought that I do not have source code for are causing major issues specifically since they reference the BaseNopModel.cs. Most plugins I am finding that rely on this must be updated. My own custom plugins I was able to update, however the ones I have purchased do not work in this upgrade.
This commit caused the problem: https://github.com/nopSolutions/nopCommerce/commit/00ce73a42a83ce101c24aad5a87ea86f1b5bfbb2
This commit caused the problem: https://github.com/nopSolutions/nopCommerce/commit/00ce73a42a83ce101c24aad5a87ea86f1b5bfbb2
Can you mention a few of the plugins, before I upgrade :)
