Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to apply data patch when running setup:upgrade #46

Open
bulldogm11 opened this issue Nov 28, 2023 · 5 comments
Open

Unable to apply data patch when running setup:upgrade #46

bulldogm11 opened this issue Nov 28, 2023 · 5 comments

Comments

@bulldogm11
Copy link

Preconditions (*)

  1. Magento 2.4.6-p3
  2. Meta Business 1.2.3

Steps to reproduce (*)

  1. Installed Meta Business extension via composer
  2. Ran setup:upgrade command

Actual result (*)

Received error:

Unable to apply data patch Meta\BusinessExtension\Setup\Patch\Data\DeleteLegacyData for module Meta_BusinessExtension. Original exception message: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'titanfuel0727_mg1.eav_attribute' doesn't exist, query was: DELETE FROM eav_attribute WHERE (attribute_code = 'facebook_age_group')

@ghost
Copy link

ghost commented Nov 29, 2023

@bulldogm11 I got the same error with magento 2.4.6-p3 and the reason was that my magento setup with prefix for tables in database. You can temporarily create a patch for this. There's even more scenario we can get this error. E.g: Table 'facebook_catalog_update' doesn't exist when trying to place order

@likearocket
Copy link

@bulldogm11 I got the same error with magento 2.4.6-p3 and the reason was that my magento setup with prefix for tables in database. You can temporarily create a patch for this. There's even more scenario we can get this error. E.g: Table 'facebook_catalog_update' doesn't exist when trying to place order

Are you able to provide a copy of the patch please? As we're also having this issue as per my thread https://github.com/magento/meta-for-magento2/issues/13

@kestraly
Copy link

kestraly commented Feb 7, 2024

Still problems with this and database prefixes

@angelo983
Copy link
Member

Duplicate of #13

@likearocket
Copy link

This should be fixed in v1.3.1 - I've closed my issues as the latest version resolves issues with my tables having prefixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants