I found my problem, i used argument item <item name="template" xsi:type="string">templates/form/collapsible</item> it is used to display for collapsible structure.
After remove this line of code is working fine. i think this error is occurred because we can not use tab structure and collapsible structure in single UI component form.
We user varnish and redis cache on our server and had this same error. This is the procedure we followed for a successful upgrade.
composer require magento/product-community-edition 2.2.6 --no-update
rm -rf var/di/* var/generation/* var/cache/* var/log/* var/page_cache/*
curl -X 'PURGE' -H'X-Magento-Tags-Pattern: .*' ...
I ran into this problem as well. Possibly due to a module we installed, the attribute was created and deleted. What ended up working to run the upgrade, was to create the attribute in the database. With the following queries.
INSERT INTO `eav_attribute` (`attribute_id`, `entity_type_id`, `attribute_code`, `attribute_model`, `backend_model`, `backend_type`, ...
I found a solution in the app/etc/di.xml file I have changed the following
<virtualType name="developerMaterialization" type="Magento\Framework\App\View\Asset\MaterializationStrategy\Factory">
<argument name="strategiesList" xsi:type="array">
<item name="view_preprocessed" xsi:type="object">Magento\...
I checked this issue again, seems like I was not the only one facing this.
Problem seems to be fixed with this commit:
Some code has to be changed:
$dirFiles = array_diff($dirFiles, ['..', '.']);
/* remove './'*/
This could be down to the image being in the CMYK colour space, Imagick can have issues when working with these images as it is unable to convert to RGB properly.
You can either upload a preconverted image, or trying patching in a way for Magento to deal with this issue with the use of setImageColourSpace and a nice little if around $image->...
Found solution here : https://github.com/magento/magento2/issues/7624
Copy final_price.phtml from
change (around line 22)
<?php if (!$block->isProductList() &&...
I also came accross this error today, for me i discovered it was the Ebizmarts_MailChimp module that was causing the issue, you can disable the module entirely which corrected the issue or what i chose to do instead was
rename the file
It's ok to delete these so long as you have other means to update the products not yet processed i.e. assuming you're going to manually ('update on save') or programmatically update these.
If you are deleting ID's lower than the version in the view_state table then you're basically removing the entries from being processed next time the cron ...
Having the exact same issue on 2.1.5 and 2.1.17. Our last UPS order came through April 15th at 9pm. With no configuration change, it stopped working on April 16th.
You can possibly fix it by changing the gateway url to https rather than http So change
You can try adding like 'MAGE_INDEXER_THREADS_COUNT'=>3 then the env.php will look something like following
'backend' => [
'frontName' => 'magento226administrator'
'crypt' => [
'key' => '45625508600206a4c2d2f2bf406b23fb'
'db' => [
'table_prefix' => '',
'connection' => ...
You need to follow the below steps:
Create default_head_blocks.xml like below:
Andd create local.css like below
Add the below code to default_head_blocks.xml
You have to add it in your current theme like this:
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../../../vendor/magento/framework/Module/etc/module.xsd">
<css src="css/local.css" />
I was trying to do the exactly same thing but I did it with another approach with Plugin.
as you can see prepareAndRender method is public and it's calling the private method preparePageMetadata
There is no need to override the private method while we can create an after plugin for prepareAndRender and just modify the $resultPage config assets.
In your ...
You can create a '_module.less' file and then call your less files in it.
Add your 'slick.less' and 'slick-theme.less' file under the following directory
Now create '_module.less' file as given below
I just got a solution from this link
So I am describing what I supposed to be followed
1) First I followed @Rohan Hapani's solution like hiding below method
* Removes 'Web Setup Wizard' from the menu if doc root is pub and no setup url variable is specified.
* @param Builder $subject
* @param Menu $menu
* @return Menu
You can do in your custom theme or in the custom module.
Following code is from my custom module.
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
There is an issue in Magento v2.2.6 and v2.2.7
It has been fixed in the 2.2-develop branch, but hasn't been released yet.
Here is the commit which fixes this issue.
It is already fixed in the 2.3 version, and will be released for the v2.2.8.
To change the label for First Name to Volunteer First Name , Last Name and Street Address.
Copy locale's csv file from /vendor/magento/module-checkout/i18n folder to app/code/Magento/module-checkout/i18n directory.
"First Name","Volunteer First Name"
"Last Name","Volunteer Last Name"
"Street Address","Volunteer Street Address"
After saving ...
The problem was that the attribute was not added to a attribute group.
The following code solved the problem:
$attributeSet = $eavSetup->getDefaultAttributeSetId(Category::ENTITY);
$attributeGroup = $eavSetup->getDefaultAttributeGroupId(Category::ENTITY);
Yes, there is an event(checkout_cart_product_add_before) before adding the product into the cart but from the Magento 2.3.X please check this link for Magento 2.3.x
But you are using Magento 2.2.6 version and in this version, this event does not exist so I would suggest you use a plugin feature of Magento.
So in your case, you want to restrict adding the ...
We posted the same question on github for Magento 2. https://github.com/magento/magento2/issues/18134
I downgraded to 2.2.5 again using composer, used the database from the backup I created before, or just revert to the backup. Create the manufacturer attribute using the specs according to a original/clean 2.2.5 installation for that attribute. Again ...