WordPress / WordPress/sqlite-database-integration
Warning: Constant SQLITE_DRIVER_VERSION already defined
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 363
- Forks
- 67
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 7
Description
From https://wordpress.org/support/topic/warning-constant-sqlite_driver_version-already-defined/:
I’m using LocalWP. The issue occurs if the site is cloned from a blueprint that already has the plugin activated.
After disabling the plugin and reactivating it, the warning is gone.
This seems to be an edge case, but let's investigate how something gets imported twice here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the LocalWP blueprint-cloning scenario described in the issue, including disabling and reactivating the plugin. Trace where SQLITE_DRIVER_VERSION is defined and how the plugin is imported or initialized twice; done means the warning no longer appears in that scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100