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

Scotter wrote:
This question is not related to this topic. It is better that you open a new topic for your question.

We have some inside sales staff who use the site to complete orders for customers.
To support this we need:
  Separate prices for different customers. I was thinking based on Roles. We currently have up to 5 price tiers.
  Note field for additional instructions on the Cart page
  Option to Register at the end of the Checkout. If their email is unique, they should only be asked for a password.
  
I have implemented many customizations which I am happy to contribute, if there is interest. None of these were done as plugins.
  Bulk edit of Products. Given a list of Skus, returns current nop field values in a spreadsheet which can be edited and reimported.
  Copy Address fields so Guests are searchable.
  Transfer the contents of My cart to another customer and impersonate that customer. Used by our inside sales team.
  Home Page and ContactUs have the proper Title and Meta tag values based on their respective Topic values.
  Canonical URLs are retrieved from a table.
  When an item (A) has a related item (B) that is Required, B cannot be removed from the cart. Removing A, removes A and B.
  Quick Order to quickly build a cart. see: http://www.dieselpartsdirect.com/quickorder
  Conditional messaging on search results. Too many hits, no hits, Goldilocks.

Matchison wrote:
Hi,

Sure. Any contribution is more than welcome! Even if some of contributed functionality is not used in the official package, it could be helpful for other developers. It would be great if you could share your customized solution by creating a new fork on codeplex as described here

Dear Nopcommerce admins
i would like to say how great of a job you guys have done so far,
i like to ask if in the upcoming patch we will have the conditional attributes ?
work item http://nopcommerce.codeplex.com/workitem/11008
many thanks

Gerard

a.m. wrote:

Andrei -
I'll create a fork as you suggested for the items that I have already implemented.
Could the above 3 features be considered for inclusion with 3.70? (I have not worked on these yet).

Matchison wrote:
Thanks. I've just created a work item for this task

Matchison wrote:
But you already can use checkout attributes with "textbox" type in order to support such field

Matchison wrote:
This work item already exists. Please vote for it here

I recently checked the v3.60 and saw some good steps towards SEO in general and SEO related to images specifically.

However, the name of an image still changes to the product name and I do not see any option to disable it.

A product can have multiply images and not all of them have to show the exact product or product variation they took the name from.

For example, if I have the product "Awesome T-Shirt with custom logo" I will have an image showing it from the front, one from the back, another with a close-up of the logo, one red, one black, a couple of others with sample logos, etc.

Soon you end up with a dozen images all named "00000xx_awesome-t-shirt_with_custom_logo_550.jpeg" but in reality only one or two should have a name like that. The others should be named "00000xx_awesome-t-shirt_front", "00000xx_awesome-t-shirt_back", "00000xx_awesome-t-shirt_with_broken_heart", etc.

Since they always have the identifier in the name (which by the way is best to be at the end of the name) there will be no problem matching them to the correct product.

SEO of images is practically 4 things, file name, alt tags, title tags and the perfect combination of file size and image dimensions.

Right now only the first thing -file name- is missing from nopCommerce. Why not add it (as an option at least)?


PS: If anyone is interested in more image optimization tips you can ready this . It's not the best guide but it's pretty good and covers pretty much everything.

Hi,

I saw for 3.7 Remove render blocking  scripts is on the work item list. It is sure that this feature comes in 3.7. If not we have to looking for another solution for this problem. At the moment we lose visiblity against our competitors and one reason is this issue.

Regards,

Dominik

a.m. wrote:

- Better vendor support

How about this? Any details?

Can this work item make it into this release? Currently, we are just disabling the buy button, however it is cluttering the search results.

Mark product as discontinued