NopCommerce 4.30 Roadmap Offer

There is no straight cut solution for this. DateTime is used many different ways for many different reasons in nopCommerce.

Usually DateTime input field takes value fom a user in local time. Then system converts it to UTC time and saves to database. Again when it’s time to show it to the user, system converts that UTC time to local time. These things are managed by DateTimeHelper class.

In your case, you can take input value in persian local time, then convert it to Gregorian local time and finally Gregorian local time to UTC time. You can add methods for these to DateTimeHelper class to make it easier.

We have a NopCommerce shop running for about three years now and are huge fans! We've been waiting for a couple of features, so if we can vote then our top three would be:
(top priority) #279 Quote (proposal) feature
#1 Ability to assign catalog price per currency
#5 Multiple invoices per order

When do you intend to release 4.30?

MaxM wrote:
We plan to release the beta version in about one week. Then we'll release the RTM version 4.30 in about two more weeks

Great news 👍

a.m. wrote:
Great !! Waiting for beta version !!

a.m. wrote:


Sounds Good.

Eagerly waiting for new version

Great news!!!!!  Congratulations Team for successfully using Linq2DB instead EF.









//Sohel

Waiting...

a.m. wrote:

Nice on this corona quarantine time we can test it. Current code has many issue hope it will fix before beta.

Thanks,
Jatin

rajupaladiya wrote:

Agreed with Mr.Raju
I also face this critical issue while working with Rewards point, and this issue need to be fix by Nopcommerce. Hope they have fixed in this new 4.30 release.