Suggestions about magento2

[mzeis]

I'm also not totally sure if this is the correct place for general suggestions but I can comment on a few things from my POV (please note I'm not with Magento):

• It's better to split different concerns up into distinct issues
• Ad 1.) The use of jQuery has already been announced and started.
• Ad 3.) Better performance is one of the planned improvements to Magento 2. See https://wiki.magento.com/display/MAGE2PROJECT/Goals#Goals-3.ImprovedProductPerformanceandScalability.
• Ad 5.) You can already define that the store code is used in the URL for every store-view but I agree that this isn't optimal as it's not possible to omit the store code for the defaulte store view as you would like to do.
• Ad 6.) (= 1. Market Ready Germany): have a look at https://github.com/firegento/firegento-germansetup. Besides that: official support for different countries would be nice.

[alexander-sibert]

Yeah, i am fine with you.

Ad 1.) is cool
Ad 3.) I saw 2 Extensions in github for MongoDB support, have you tested it?
Ad 5.) I know that with Store Codes but Magento can improve it. If you show the settings with i18n in Drupal 7 for Multilanguage that is a dream.
Ad 6.) Market Ready Germany is bullshit :D, Firegento German Setup is good. Official support will be better. PrestaShop made it, too.

[lukebranch]

In regards to suggestions there are a few things I would love to see integrated into the Magento 2.0 core:

1. Integration with a variety of CDN's out of the box such as Cloudflare, Cloudfront, Nexcess, MaxCDN, Google Page Speed or any number of others. A simple API integration would be great and would allow for substantial gains in performance for the majority of Magento-based websites doing business internationally. Most CDN's require some time-consuming setup to allow Magento to function properly, something that works out of the box would be ideal.
2. The Paypal Website Payments Standard & Express payment option has a bug that does not transfer line cart items properly and leaves the quantity of any particular product as 1 on the paypal invoice.
3. Allow for editing of PDF packing slips in a similar method to the GUI Editor that has been laid out on the Magento 2 wiki for editing templates or perhaps through a method like the transactional emails are being customized at this point in time.
4. Easy addition of extra custom checkout fields and steps.
5. Tier pricing over a group of different products that would allow for more flexible promotions. It would be ideal if this could be implemented in the same manner as the grouped or bundled products that would allow an instant change in price on the product page.
6. Allow the triggering of newsletters based on specific promotional rules (eg. allow triggering of a birthday newsletter for customers who have provided a birth date).
7. A basic customer support ticket system, order ticket system and knowledgebase/FAQ that keeps everything connected to a customer's account. Something that would allow for admin to respond directly from the backoffice and would be notified whenever there was a ticket opened or overdue. This or integration with something like OTRS or osTicket/osFAQ would be great.
8. Allow control of robots.txt directly from the backoffice individually for multi-website, multi-store setups.
9. Allow for creation and editing of custom XML feeds for use with a variety of (CSE) Comparison Shopping Engines like Google Shopping/Base, Yahoo Shopping, Bizrate and any number of domestic CSE's.
10. A responsive template for inclusion in the core.
11. Plugin for Akismet included by default to curb review spam.
12. Rollback/Backup feature that allows for backup to a cloud service such as Amazon buckets or dropbox.
13. Cronjob schedule and history integrated into the backoffice.
14. Canonical tags to remove the duplicate content issue faced by many Magento multi-store, multi-device websites (eg. mobile optimised by means of user agent redirection).
15. A security check module that checks the vulnerability of your Magento site based on many different things such as .htaccess file, chmod file permissions, apache/litespeed server config, php config, etc. And suggest changes that you can make or allows for changes to be applied from the backoffice (eg. similar to Better WP Security for Wordpress).
16. SEO analysis module in much the same manner as the WordPress SEO plugin for Wordpress to give you suggestions and methods for improving your page rank.
17. Easily customizable contact page to allow for addition of extra fields.
18. Manual approval of customer accounts able to be applied on a multi-website, multi-store level to allow for better support for those operating retail and wholesale orders from the same dashboard. Easily customizable customer signup forms to allow for custom fields as well would be a definite plus.
19. Allow for a Google Analytics dashboard in the backoffice.
20. Easy addition of extra tabs at the product page level to allow for custom content and custom tabs for each product.
21. Integration of social sharing buttons such as facebook (like and share), twitter, pinterest, google plus, etc.

If any of these have already been covered in the wiki or in another forum my apologies. These features are a wishlist for the 2.0 release and I hope that a few of them will be considered.

[alexander-sibert]

A good list: Drupal has already such robots.txt administration/creation module for Multisites. Also i find the Multilanguage and Backend Translation functions of Drupal more than cool.

You can see it here: http://www.neofelis.de/robots.txt (I can control this over Backend with Multisite function.)

Magento should have interest, to hold his position in the ecommerce shop systems market. The big reasons to decide not for Magento are:

1. Performance is very slow
2. Not very good Multi-Language Support

[piotrekkaminski]

Thank you for the valuable suggestion. Let me try to answer some of those.
First of all, if you submit any of those with code and tests, there is much higher chance it will make its way into the core :)

I see comments regarding multi-language support - can you please elaborate what is the main issue? We might be not aware of that.

@alexander-sibert :
We are in the process of moving to jQuery. Layered navigation improvements are in the backlog but i would not expect a quick fix. We are addressing performance issues and we take this very seriously. There are improvements to customers import already available. Product import should follow. I would not expect changes in translation functionality or german-market specific functionality.

@lukebranch;

1. There is an extension for that.
2. It is filed as a bug.
3. Would love to have it - unfortunately probably not possible.
4. Not on the roadmap, can be done with custom code
5. Not on the roadmap
6. Great idea - not on the roadmap unfortunately
7. There are many extensions for that.
8. Already done
9. There are many extensions for that.
10. Working on it
11. I expect an extension to cover that. not a core functionality.
12. I expect an extension to cover that. not a core functionality.
13. Good feedback - will add to backlog.
14. We do have canonical tags - what do you think is missing?
15. There are so many different environments that i don't see this to work reliably.
16. I expect an extension to cover that
17. added to backlog
18. Partially available in the Enterprise Edition
19. Not a core functionality
20. Can you provide more details - do you mean admin or frontend?
21. Lots of extensions cover that.

This answer is not intended to be an exhaustive list of all the
planned updates and enhancements. Although this roadmap provides our best view of
the product direction, priorities can change and features may be adjusted. As a result,
we do not recommend making firm business decisions solely based on this information.

[therouv]

There is already an extension for 13): https://github.com/fbrnc/Aoe_Scheduler Only the cron history is missing afaik.

[alexander-sibert]

@piotrekkaminski In Drupal we have for Security for cron.php access following during the Installation generated ID: http://neofelis.de/cron.php?cron_key=jTsdfsdfHDmzb_9c_0Csdfdfs-nV1sfdfsdfOgVg-ccsdfsdfsf0

May be it is possible for Magento

I changed a bit the code in the cron key ;)

[alexander-sibert]

On Drupal i can receive for definied E-Mail address a update notification about modules assigned with cron. If updates are available (checked every day or week) i receive a E-Mail about this. I think that will be a great support to have all modules in current version. Drupal have here one more function. The Drupal Community can decide between normal update or a security update. Drupal shows me in the modules list all security updates with red background.

Then: That is right, that we have for some things a lot of extensions in the Community but think, not all extensions are developed fine. Only a small part of the Magento Connect Extensions are developed fine.

[piotrekkaminski]

Thanks for all the suggestion. We are using some of them already. I'm closing this issue. Feel free to provide new suggestions as new issues.