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

Possible Problem with Backup and Migrate Restore DB #64

Closed
stpaultim opened this issue May 19, 2021 · 6 comments
Closed

Possible Problem with Backup and Migrate Restore DB #64

stpaultim opened this issue May 19, 2021 · 6 comments
Assignees

Comments

@stpaultim
Copy link
Member

Just creating this ticket based upon this issue reported in the forum. I assume that this user also updated core to 1.19.0.

I updated the backup_migrate module and it was able to successfully create a backup. However when I try to restore the backup. I get the following error:

Call to unidentified method DatabaseConnection_mysql::prepare()

I am testing on some local development sites. The backup seems correct when I manually restore the database.

https://forum.backdropcms.org/comment/2867#comment-2867

I have not recreated or confirmed this issue. Has anyone else had this problem?

@quackers8me
Copy link
Collaborator

I can confirm the issue and found that it's due to removing the 'exends PDO' from the DatabaseConnection class to accommodate PHP8. I am looking for a solution and have reached out to the Drupal module maintainer.

@quackers8me quackers8me self-assigned this May 19, 2021
@stpaultim
Copy link
Member Author

@quackers8me - Thanks for the follow-up.

The user who reported this problem added the following information to the forum discussion.

I was using a fresh install of backdrop 1.19.0. No other modules; just backup_migrate.

@quackers8me
Copy link
Collaborator

In discussion with the D7 maintainer, the fix may require a change to backdrop core.

@quicksketch
Copy link
Member

The core issue for tracking this is backdrop/backdrop-issues#5094. Though we don't have any suggestion yet as to what the right fix would be on the core side either.

@quackers8me
Copy link
Collaborator

@quicksketch I wasn't sure if it should go there so I created a new one. I will update that issue instead.

@stpaultim
Copy link
Member Author

I experienced this problem on one of my own sites yesterday.

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

3 participants