remove strpos warning when prefix is empty
#43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OllieJones
approved these changes
Jul 24, 2022
OllieJones
added a commit
that referenced
this pull request
Jul 24, 2022
… into main @carlalexander's change from #43
|
For what it's worth, WordPress's 6.0.1 installer refuses to build a site with an empty table-name prefix. |
|
Well, the thing was that I didn't do this on a new site. I ran this on a 14yo WordPress site. So they probably allowed it back then 🤣 |
|
Yeah, I figured. WordPress from antiquity. We did fix the bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a warning if you try to run the plugin with a WordPress installation without a prefix