nopCommerce 4.30 BETA released. Please share your impressions

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
4 years ago
[email protected] wrote:
Not exactly a demo, more a work in progress but this site is 4.3
http://wchd.brianwatson.eu
A fair bit of work remains before we will be going live but it should offer some insight as to how the public facing side of the site works.


That site is looking very good, nice job.  And if that's an indication on performance on 4.3 it does appear to be improved quite a bit.  Thanks for sharing.
4 years ago
Great to see this new version. I'll plan the migration of our Mollie plugin for may 2020. I'm excited to see what kind of data access is now in place..
4 years ago
@775tech  - Nice work. your 4.3beta site seems impressively fast. Is that a mySQL db? MSSQL? or SQL Express?  Can i be nosy are ask what hardware or cloud spec is backing that? using redis cache? etc.

thanks
Jon
4 years ago
a.m. wrote:
When is 4.30 planned to be officially released?
It will depend on how many bugs we find. But most probably in about a couple of weeks


We just upgraded from 3.8 to 4.2 for our website, but it's not yet launched. If we upgrade again to 4.3, will it be too hard or pretty easy?
4 years ago
[email protected] wrote:
Hi,

can somebody share a 4.3 nopcommerce site link?
I'm not a programmeer but I would still like to check the new features.

Thanks

Matteo

I will add in couple of days.
my website:https://hoodarcheryshop.com
But its nopcommerce 4.20+ some developer source.
ı wil upgrade to 4.30 beta+latest developer source from github.(need wait for some plug-ins upgrade)
4 years ago
Continue report error in log:
Unexpected end of Stream, the content may have already been read by another component.
ubuntu 18.04 ssl with cloudflare
nopcommerce in develop branch.

it is said can resolve by add DisableFormValueModelBindingAttribute , the   link at here.

error logs:

Unexpected end of Stream, the content may have already been read by another component.
Full message  
System.IO.IOException: Unexpected end of Stream, the content may have already been read by another component.
   at Microsoft.AspNetCore.WebUtilities.MultipartReaderStream.ReadAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.WebUtilities.StreamHelperExtensions.DrainAsync(Stream stream, ArrayPool`1 bytePool, Nullable`1 limit, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.WebUtilities.MultipartReader.ReadNextSectionAsync(CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Http.Features.FormFeature.InnerReadFormAsync(CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Mvc.ModelBinding.FormValueProviderFactory.AddValueProviderAsync(ValueProviderFactoryContext context)
   at Microsoft.AspNetCore.Mvc.ModelBinding.CompositeValueProvider.CreateAsync(ActionContext actionContext, IList`1 factories)
   at Microsoft.AspNetCore.Mvc.ModelBinding.CompositeValueProvider.TryCreateAsync(ActionContext actionContext, IList`1 factories)
   at Microsoft.AspNetCore.Mvc.Controllers.ControllerBinderDelegateProvider.<>c__DisplayClass0_0.<<CreateBinderDelegate>g__Bind|0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at WebMarkupMin.AspNetCore3.WebMarkupMinMiddleware.ProcessAsync(HttpContext context, Boolean useMinification, Boolean useCompression)
   at WebMarkupMin.AspNetCore3.WebMarkupMinMiddleware.ProcessAsync(HttpContext context, Boolean useMinification, Boolean useCompression)
   at WebMarkupMin.AspNetCore3.WebMarkupMinMiddlewareBase.Invoke(HttpContext context)
   at StackExchange.Profiling.MiniProfilerMiddleware.Invoke(HttpContext context) in C:\projects\dotnet\src\MiniProfiler.AspNetCore\MiniProfilerMiddleware.cs:line 125
   at Nop.Services.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) in /home/maple/nopCommerce430/src/Libraries/Nop.Services/Authentication/AuthenticationMiddleware.cs:line 79
   at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
   at Nop.Services.Installation.InstallUrlMiddleware.Invoke(HttpContext context, IWebHelper webHelper) in /home/maple/nopCommerce430/src/Libraries/Nop.Services/Installation/InstallUrlMiddleware.cs:line 53
   at Nop.Services.Common.KeepAliveMiddleware.Invoke(HttpContext context, IWebHelper webHelper) in /home/maple/nopCommerce430/src/Libraries/Nop.Services/Common/KeepAliveMiddleware.cs:line 51
   at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)
4 years ago
bradcwalker wrote:
We just upgraded from 3.8 to 4.2 for our website, but it's not yet launched. If we upgrade again to 4.3, will it be too hard or pretty easy?


If there is no customization in your source code then it pretty easy.
If there is customization in source code then it will hard be based on customization.
4 years ago
Hi,

any update on when 4.3 stable will be finally realesed?

Thanks
4 years ago
[email protected] wrote:
any update on when 4.3 stable will be finally realesed?

We plan to introduce one more version for testing - "4.30 release candidate" on April 30th. And release the final version around May 11-12
4 years ago
a.m. wrote:
any update on when 4.3 stable will be finally realesed?
We plan to introduce one more version for testing - "4.30 release candidate" on April 30th. And release the final version around May 11-12


Awesome.

Eagerly awaiting for this update.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.