magento2

alling Magento on a new server, Magento installer says installation is successful and all requirements are met, then it proudly redirects you to your broken home page.

rails eco-system built by Spree and Solidus community. Its very easy to build a highly customized and resilient system using cloud offering combined with these open source systems. So I do not see why a mid-size business will choose shopify or bigcommerce. They are good for mom-pop shops and simple commerce, but for unique shopping experience they fall short and better to build customized one with complete control. [1] https://github.com/magento/magento2 [2] https://github.com/mirumee/saleor [3] https://github.com/Sylius/Sylius [4] https://github.com/shuup/shuup [5] https://github.com/solidusio/solidus [6] https://github.com/spree/spree [7] https://github.com/vuestorefront/vue-storefront [8] https://github.com/Divanteltd/storefront-ui [9] https://github.com/4seer/openflutterecommerceapp

b6209a4e62ede9... EDIT: I say all this in a generic "use of debugger" sense, not a Go-specific debugger usage.

as 3 month old bugs that I can't provide an update on, or even an ETA for resolution. I look forward to Magento hopefully fixing the major issues with M2 in the near future. P.S. I realised that I didn't actually post the URL to the bug I mentioned in my previous post. It's https://github.com/magento/magento2/issues/6683 ("Products updated_at field is not updating on save") which seems related to a couple of other bugs pertaining to "updated_at" fields not being modified.

.php: chmod($this->_localConfigFile, 0777); ./app/code/core/Mage/Catalog/Model/Product/Attribute/Backend/Media.php: $ioAdapter->chmod($this->_getConfig()->getTmpMediaPath($fileName), 0777); ./app/Mage.php: chmod($logDir, 0777); ./app/Mage.php: chmod($logFile, 0777); ./lib/Zend/Service/WindowsAzure/CommandLine/PackageScaffolder/PackageScaffolderAbstract.php: @chmod($path, '0777'); ./lib/Zend/Service/WindowsAzure/CommandLine/PackageScaffolder/PackageScaffolderAbstract.php: @chmod($path, 0777); ./lib/Zend/Service/WindowsAzure/CommandLine/PackageScaffolder/PackageScaffolderAbstract.php: @chmod($path, 0777); ./lib/Zend/Cloud/StorageService/Adapter/FileSystem.php: chmod($path, 0777); ./lib/Varien/Autoload.php: @chmod($this->_collectPath, 0777); ./lib/Varien/File/Uploader.php: chmod($destinationFile, 0777); ./lib/Mage/Backup/Filesystem.php: chmod($backupsDir, 0777); ./errors/processor.php: @chmod($this->_reportFile, 0777); 2. The company thinks there's nothing wrong with storing money as floats: https://github.com/magento/magento2/issues/555 The way we eventually dealt with hosting Magento (which we had strongly advised against) was a concrete sarcophagus and a thirty-kilometre exclusion zone: * a cron line specifically to remove o-w permissions from all files in the webroot every minute (which is very inelegant, but the alternative is maintaining our own patches to core). * Files not owned www-data, except where Magento must be able to write to them. * deploy all webroot files as a user the webserver can't write. * cron.sh (Magento's internal cron) runs as root out of the box. We ran it as www-data. * AppArmor to keep Magento from ever, ever being able to pull shit. This caught Magento's more antisocial tendencies on more than one occasion. * Admin login: use a path other than "/admin" to foil quite a lot of attack bots at the very simplest level. We have outsourced our remaining Magento, thankfully, and I don't personally have to maintain the above any more. (You know you've been administering Magento a bit long when you can hum along to bits of "Metal Machine Music" accurately.) The use case for Magento is (apparently deliberately) confused. It's an unholy melange of a CMS and a shopping basket. There is no good out-of-the-box experience; in practice it's a job creation scheme for consultants. Even crap-tier "well technically I can tell my boss's boss we have paid support" support, with a four-day response time for them to ask you a simple question you already put the answer to in the original ticket, is swingeingly expensive. I can't say what we're paying for this standard of quality, but I can say that it's public knowledge that Magento is at least $13k/yr: http://web.archive.org/web/20120215011525/http://www.magento... The problem Magento seems to solve is when the business wants a quick site without developer involvement. After a few other abortive platforms (Plone, Drupal - which are both fine for what they are, in ways Magento just isn't, but didn't end up matching our needs), our eventual solution to this was Wordpress, which we have outsourced so I don't have to think about that either. Outsourced Wordpress with securing it being the host's problem is totally the right answer. I don't have a good answer on the shopping basket, but Magento was bad enough at that too that we went back to our in-house homerolled system. I understand some work has gone into Magento 2.0 to make it less mind-bogglingly horrible.

ingle ticket can do. In general, it's unfortunate that Magento 1.x development and bug tracking are so... internal. In contrast to the visibility and interaction present at https://github.com/magento/magento2/issues it's clear that everyone is better off. Of course, we have to consider how to have the same kind of open dialogue for Enterprise Edition, and we're working out how to do that. Would you care to participate in a private GitHub repo, or can you suggest some other medium? Really, neither you nor I should have to spend time writing about the 777 issue - an open dialogue would likely have led this to be fixed years ago, so we could spend time bemoaning & fixing other issues!

re solving this for Magento 2 by having tech writers on staff and by soliciting community help (docs are also on GitHub, PRs accepted): https://github.com/magento/devdocs > search was pretty much broken and it was slow Search and newsletters are insufficient for anything but the most basic needs. That's why there are so many SaaS search vendors filling this space quite well via free extensions. > on a shared host, performance must be terrible Shared hosts are never appropriate for commerce sites due to security reasons. There are a number of specialized small business hosts which run < $50 / month. For shops lacking that budget, well, there will be challenges in general.