nopCommerce 3.40 roadmap and estimated release date. Let's discuss.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
9 Jahre weitere
XtremeCommerce wrote:
Have you thought about converting it to a Bootstrap Design?

Still under discussion
9 Jahre weitere
J.Ding wrote:
So the whole mobile version is not available anymore?
We have a pretty big desktop version which is not suitable for responsive design, what should i do with the mobile devices?


Yes it was sorry !!!
9 Jahre weitere
XtremeCommerce wrote:
So the whole mobile version is not available anymore?
We have a pretty big desktop version which is not suitable for responsive design, what should i do with the mobile devices?

Yes it was sorry !!!


Well I do not have much time for that, we want to go online next month.
So i think i will just stay with 3.30 for the moment.
9 Jahre weitere
Hi Andrei,

good job and keep it.

There is an update of the SQL file from 3.30 to 3.40?
Where is this update file?


Frank
9 Jahre weitere
fbfrank wrote:
Hi Andrei,

good job and keep it.

There is an update of the SQL file from 3.30 to 3.40?
Where is this update file?


Frank

Hi Frank,

Thanks. Please find it here
9 Jahre weitere
I have downloaded NopCommerce 3.4.On minimizing browser, page is not scrolling as was happening in 3.1.Align is different.It this intentional.
9 Jahre weitere
a.m. wrote:
Hi Andrei,

I have hosted my website in the United States. But live in Germany.
All times in nopCommerce are now United States time.

Now must I always expect webserver (US time) + 6 hours = Germany time

I hope that you understand.


Frank
please see https://nopcommerce.codeplex.com/workitem/10427




Hi Andrei,

This is a solution in 3.40? How and where was this solved in 3.50?


Frank
9 Jahre weitere
fbfrank wrote:
Hi Andrei,

This is a solution in 3.40? How and where was this solved in 3.50?


Frank

Hi Frank,

The only solution is to use "string" instead of "DateTime" type. It's not fixed yet because this solution is quite "ugly"
9 Jahre weitere
a.m. wrote:
Hi Andrei,

This is a solution in 3.40? How and where was this solved in 3.50?


Frank
Hi Frank,

The only solution is to use "string" instead of "DateTime" type. It's not fixed yet because this solution is quite "ugly"



Hi Andrei,

OK.
where is the change?


Frank
9 Jahre weitere
There are a lot of changes. You have to modify all models where DateTime is used and returned to the client using AJAX (string should be returned). Find more info at work item description (it also has several links to forums and other resources)
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.