#StackBounty: #magento2 #magento-2.1 #module Create Dirty Playground In Magento 2.1.6

Bounty: 50

The method outlined here to create a dirty playground doesn’t work in magento 2.1.6: https://magento.stackexchange.com/a/40848/55108

It generates the error:

Uncaught TypeError: Argument 2 passed to MagentoFrameworkAppHttp::__construct() must be an instance of MagentoFrameworkEventManager, none given

The TestApp class in the example extends MagentoFrameworkAppHttp. This is the Http classes constructor:

public function __construct(
    MagentoFrameworkObjectManagerInterface $objectManager,
    EventManager $eventManager,
    AreaList $areaList,
    RequestHttp $request,
    ResponseHttp $response,
    ConfigLoaderInterface $configLoader,
    State $state,
    Filesystem $filesystem,
    MagentoFrameworkRegistry $registry
) {
    $this->_objectManager = $objectManager;
    $this->_eventManager = $eventManager;
    $this->_areaList = $areaList;
    $this->_request = $request;
    $this->_response = $response;
    $this->_configLoader = $configLoader;
    $this->_state = $state;
    $this->_filesystem = $filesystem;
    $this->registry = $registry;
}

So I guess it is failing because $eventManager doesn’t exist within the playgrounds context?

How does the code need to be updated to work with 2.1.6?


Get this bounty!!!

#StackBounty: #magento2 #product #custom-options Magento2 Catalog Product Options

Bounty: 50

We found this issue when working in a default Magento2.1.

While creating custom options for a product, if I select the drop-down field a second time, the spinner never stop loading.

Please find the below screen-shot:
enter image description here

I think this is a Magento2 core bug, can anyone confirm and suggest how to fix it?

Thanks


Get this bounty!!!

#StackBounty: #magento2 #custom-options Magento2 Catalog Product Options

Bounty: 50

We Found the issue in default magento2.1, while creating the custom options, when i am selected the drop-down field for second time its loading continuously.
Please find the below screen-shot:
enter image description here

I thought its Magento2 issue
Can anyone give us the clarification on this.

Thanks


Get this bounty!!!

#StackBounty: #magento2 #magento-2.1 #git #deployment #gitignore Magento2 – local / staging / production deployment & gitignore

Bounty: 100

This could be one kind of discussion more than a question.

I’d like to know which deployment policy you follow with Magento2 & local > staging > production environments

After some tries we’ve decided the best (or at least, the most solid) approach would be this gitignore file including vendor folder in git.

.DS_Store
/.buildpath
/.cache
/.metadata
/.project
/.settings
atlassian*
/nbproject
/sitemap
/sitemap.xml
/.idea
/.gitattributes
/app/config_sandbox
/app/etc/config.php
/app/etc/env.php
/app/code/Magento/TestModule*
/lib/internal/flex/uploader/.actionScriptProperties
/lib/internal/flex/uploader/.flexProperties
/lib/internal/flex/uploader/.project
/lib/internal/flex/uploader/.settings
/lib/internal/flex/varien/.actionScriptProperties
/lib/internal/flex/varien/.flexLibProperties
/lib/internal/flex/varien/.project
/lib/internal/flex/varien/.settings
/node_modules
/.grunt
/pestle.phar
/pub/media/*.*
!/pub/media/.htaccess
/pub/media/catalog/*
!/pub/media/catalog/.htaccess
/pub/media/customer/*
!/pub/media/customer/.htaccess
/pub/media/downloadable/*
!/pub/media/downloadable/.htaccess
/pub/media/import/*
!/pub/media/import/.htaccess
/pub/media/theme/*
/pub/media/theme_customization/*
!/pub/media/theme_customization/.htaccess
/pub/media/wysiwyg/*
!/pub/media/wysiwyg/.htaccess
/pub/media/tmp/*
!/pub/media/tmp/.htaccess
/pub/media/captcha/*
/pub/static/***
!/pub/static/.htaccess

/var/*
!/var/.htaccess

.unison*
/sync.sh

So we run composer only in local environment: As any new extension, or software upgrade is tested in local, then validated and committed. We’d probably then include app/etc/config.php file in git too but that file is rewriten when running setup:upgrade, right?

Including vendor means repository size will be bigger than (maybe) recommended but this way when deploying code, we just run the sequence:

bin/magento setup:upgrade
bin/magento setup:di:compile (optional)
bin/magento setup:static-content:deploy

Related info:
http://www.damianculotta.com.ar/magento/gitignore-y-la-estrategia-de-deploys-en-magento2

See why we choose compile command as optional Magento 2 – setup:di:compile ?

UPDATE

The truth is we are having some problems when deploying code changes in our published Magento 2 projects

Changes work in local & staging (checked in both modes: developer & production… although we conceptually configure that environments in developer mode), but some of them don’t work in production environment (in production mode), etc… so I am not sure we are following the right strategy. I’d like to see what’s the appropriated command sequence, and the relevance of the order in that commands

In fact, every day I am less convinced about the utility of Magento 2 production mode, unless you are not going to change anything in the project. Can you change my mind?


Get this bounty!!!

#StackBounty: #magento2 #product #configurable-product Can't disable configurable product variations in Magento 2

Bounty: 50

When I edit a configurable product in the Configuration section, it shows the list of all the configurations.

I want to disable one of the products listed there so when I choose Disable Product the status does change to “Disabled”.

But after saving the product, status changes back to Enabled.

I have the error logs enabled but no error message appears there even when I have cleared the cache and reindexed.

enter image description here


Get this bounty!!!

#StackBounty: #magento2 #product #configurable-product Can't disable configurable product variations in Magento 2

Bounty: 50

When I edit a configurable product in the Configuration section, it shows the list of all the configurations.

I want to disable one of the products listed there so when I choose Disable Product the status does change to “Disabled”.

But after saving the product, status changes back to Enabled.

I have the error logs enabled but no error message appears there even when I have cleared the cache and reindexed.

enter image description here


Get this bounty!!!

#StackBounty: #magento2 #product #configurable-product Can't disable configurable product variations in Magento 2

Bounty: 50

When I edit a configurable product in the Configuration section, it shows the list of all the configurations.

I want to disable one of the products listed there so when I choose Disable Product the status does change to “Disabled”.

But after saving the product, status changes back to Enabled.

I have the error logs enabled but no error message appears there even when I have cleared the cache and reindexed.

enter image description here


Get this bounty!!!

#StackBounty: #magento2 #product #configurable-product Can't disable configurable product variations in Magento 2

Bounty: 50

When I edit a configurable product in the Configuration section, it shows the list of all the configurations.

I want to disable one of the products listed there so when I choose Disable Product the status does change to “Disabled”.

But after saving the product, status changes back to Enabled.

I have the error logs enabled but no error message appears there even when I have cleared the cache and reindexed.

enter image description here


Get this bounty!!!

#StackBounty: #magento2 #product #configurable-product Can't disable configurable product variations in Magento 2

Bounty: 50

When I edit a configurable product in the Configuration section, it shows the list of all the configurations.

I want to disable one of the products listed there so when I choose Disable Product the status does change to “Disabled”.

But after saving the product, status changes back to Enabled.

I have the error logs enabled but no error message appears there even when I have cleared the cache and reindexed.

enter image description here


Get this bounty!!!

#StackBounty: #magento2 #product #configurable-product Can't disable configurable product variations in Magento 2

Bounty: 50

When I edit a configurable product in the Configuration section, it shows the list of all the configurations.

I want to disable one of the products listed there so when I choose Disable Product the status does change to “Disabled”.

But after saving the product, status changes back to Enabled.

I have the error logs enabled but no error message appears there even when I have cleared the cache and reindexed.

enter image description here


Get this bounty!!!