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

SQL Error on config page right after installation #1865

Closed
OvalMedia opened this issue Feb 1, 2024 · 0 comments · Fixed by #1875
Closed

SQL Error on config page right after installation #1865

OvalMedia opened this issue Feb 1, 2024 · 0 comments · Fixed by #1875

Comments

@OvalMedia
Copy link

OvalMedia commented Feb 1, 2024

Preconditions

  1. Magento 2.4.4
  2. MariaDB 10.6.15
  3. database name is 'www.my-shop.com'
  4. Mailchimp module v103.4.57
  5. Shop is a copy of a live system in a local environment
  6. Shop is in developer mode

Steps to reproduce

  1. install module via composer: require mailchimp/mc-magento2
  2. enable module: bin/magento module:enable Ebizmarts_MailChimp
  3. run setup: bin/magento setup:upgrade
  4. compile: bin/magento setup:di:compile
  5. in backend go to mailchimp settings page

Expected result

no errors

Actual result

Page opens with an error message on top: "A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later."

In the system.log I find this message:

main.ERROR: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'www.my-shop' doesn't exist, query was: SELECT `main_table`.`mailchimp_store_id` FROM `mailchimp_sync_ecommerce` AS `main_table`
 LEFT JOIN `www`.`my-shop` AS `core_config` ON value = mailchimp_store_id WHERE (value is null) GROUP BY `mailchimp_store_id` [] []

Apart from this the configuration seems to work fine.

Additional information

My suspicion is that the system chokes on the database name, as it contains dots ("www.my-shop.com").

Edit

I just mirrored the same system onto a staging server where the database name differs (no dots). It confirms my suspicion, no sql error occured.

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

Successfully merging a pull request may close this issue.

2 participants