magento / magento/magento-cloud-docker

Call to undefined method Magento\Eav\Api\Data\AttributeExtension::setIsPagebuilderEnabled while deploying Magento 2.4.5

Open
#359 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Progress: ready for grooming
Dominant language
PHP
Stars
277
Forks
187
PR merge metrics
No merged PRs in 30d

Description

Failing to deploy Adobe Commerce in the Docker container.
It's the step 6 in this [documentation](https://developer.adobe.com/commerce/cloud-tools/docker/deploy/developer-mode/).
The fix is already available [here](https://github.com/magento/magento2-page-builder/issues/730#issuecomment-1302736299)

### Preconditions

1. using Windows 10 with WSL2 updated

### Steps to reproduce

From WSL
1. git clone https://github.com/magento/magento-cloud.git
2. curl -sL https://github.com/magento/magento-cloud-docker/releases/download/1.3.4/init-docker.sh | bash -s -- --php 8.1 --image 1.3.5 --host magento2.docker
3. ./vendor/bin/ece-docker build:compose --mode="developer" --sync-engine="manual-native" --port=9080
4. docker compose up -d
5. ./bin/magento-docker copy-to --all
8. docker compose run --rm deploy cloud-deploy

### Expected result

1. Adobe Commerce is correctly deployed on Docker container

### Actual result

This error occur
`Call to undefined method Magento\Eav\Api\Data\AttributeExtension::setIsPagebuilderEnabled()0 /app/vendor/magento/framework/Interception/Interceptor.php(146): Magento\PageBuilder\Plugin\Catalog\Model\Product\Attribute\RepositoryPlug
in->afterGet(Object(Magento\Catalog\Model\Product\Attribute\Repository\Interceptor), Object(Magento\Catalog\Model\ResourceModel\Eav\Attribute\Interceptor), 'sku')
1 /app/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Catalog\Model\Product\Attribute\Repository\Interceptor->Magento\Framework\Interception\{closure}('sku')
2 /app/generated/code/Magento/Catalog/Model/Product/Attribute/Repository/Interceptor.php(23): Magento\Catalog\Model\Product\Attribute\Repository\Interceptor->___callPlugins('get', Array, Array)
3 /app/vendor/magento/module-catalog-search/Setup/Patch/Data/SetInitialSearchWeightForAttributes.php(103): Magento\Catalog\Model\Product\Attribute\Repository\Interceptor->get('sku')
4 /app/vendor/magento/module-catalog-search/Setup/Patch/Data/SetInitialSearchWeightForAttributes.php(56): Magento\CatalogSearch\Setup\Patch\Data\SetInitialSearchWeightForAttributes->setWeight('sku', 6)
5 /app/vendor/magento/framework/Setup/Patch/PatchApplier.php(162): Magento\CatalogSearch\Setup\Patch\Data\SetInitialSearchWeightForAttributes->apply()
6 /app/setup/src/Magento/Setup/Model/Installer.php(1095): Magento\Framework\Setup\Patch\PatchApplier->applyDataPatch('Magento_Catalog...')
7 /app/setup/src/Magento/Setup/Model/Installer.php(961): Magento\Setup\Model\Installer->handleDBSchemaData(Object(Magento\Setup\Module\DataSetup), 'data', Array)
8 [internal function]: Magento\Setup\Model\Installer->installDataFixtures(Array)
9 /app/setup/src/Magento/Setup/Model/Installer.php(386): call_user_func_array(Array, Array)
10 /app/setup/src/Magento/Setup/Console/Command/InstallCommand.php(238): Magento\Setup\Model\Installer->install(Array)
11 /app/vendor/symfony/console/Command/Command.php(255): Magento\Setup\Console\Command\InstallCommand->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
12 /app/vendor/symfony/console/Application.php(1021): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
13 /app/vendor/symfony/console/Application.php(275): Symfony\Component\Console\Application->doRunCommand(Object(Magento\Setup\Console\Command\InstallCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Compon
ent\Console\Output\ConsoleOutput))
14 /app/vendor/magento/framework/Console/Cli.php(116): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
15 /app/vendor/symfony/console/Application.php(149): Magento\Framework\Console\Cli->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
16 /app/bin/magento(23): Symfony\Component\Console\Application->run()
17 {main}

Fatal error: Uncaught Exception: User Error: Some transactions have not been committed or rolled back in /app/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php on line 4067 in /app/vendor/magento/framework/App/ErrorHandler.php:62
Stack trace:
0 [internal function]: Magento\Framework\App\ErrorHandler->handler(256, 'Some transactio...', '/app/vendor/mag...', 4067)
1 /app/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php(4067): trigger_error('Some transactio...', 256)
2 [internal function]: Magento\Framework\DB\Adapter\Pdo\Mysql->__destruct()
3 {main}
thrown in /app/vendor/magento/framework/App/ErrorHandler.php on line 62`

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with step 6 of the linked developer-mode deployment documentation and the Magento_PageBuilder plugin shown in the stack trace. Review the referenced Magento 2 Page Builder issue for the reported fix, then verify whether the documented Docker deployment completes without the undefined-method error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, php
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.