Skip to content

Use the WordPress install's database prefix with the capabilities field. Thanks to WordPress user @dhartendorp for the report.#501

Merged
jonathanstegall merged 1 commit intomasterfrom
500-prefix-capabilities
Oct 5, 2022
Merged

Use the WordPress install's database prefix with the capabilities field. Thanks to WordPress user @dhartendorp for the report.#501
jonathanstegall merged 1 commit intomasterfrom
500-prefix-capabilities

Conversation

@jonathanstegall
Copy link
Copy Markdown
Member

What does this Pull Request do?

This fixes #500 by using $this->wpdb->prefix . 'capabilities' instead of wp_capabilities.

How do I test this Pull Request?

  • Map a capabilities field with a custom prefix
  • Map a capabilities field without a custom prefix

@jonathanstegall jonathanstegall self-assigned this Sep 30, 2022
@jonathanstegall jonathanstegall added this to the v2.2.5 milestone Sep 30, 2022
@jonathanstegall jonathanstegall added bug fix Pull request that fixes a bug patch pull request that requires a patch release, ex v2.1.2. This is the default for new releases. labels Sep 30, 2022
@jonathanstegall jonathanstegall changed the title Use the WordPress install's database prefix with the capabilities field Use the WordPress install's database prefix with the capabilities field. Thanks to WordPress user @dhartendorp for the report. Oct 5, 2022
@jonathanstegall jonathanstegall merged commit b7e5ca0 into master Oct 5, 2022
@jonathanstegall jonathanstegall deleted the 500-prefix-capabilities branch October 5, 2022 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug fix Pull request that fixes a bug patch pull request that requires a patch release, ex v2.1.2. This is the default for new releases.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

In WordPress Core, the wp_capabilities field uses the wpdb prefix, but we do not

1 participant