Opened 10 years ago
Last modified 16 months ago
#36428 new defect (bug)
Weird default value of option 'default_link_category'
| Reported by: | JanVoracek | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Upgrade/Install | Version: | 3.5 |
| Severity: | normal | Keywords: | needs-unit-tests has-patch |
| Cc: | Focuses: |
Description
The option default_link_category has value 2 after installing WordPress. It makes no sense since 3.5.
Generally, it's not a big problem, but we check referential integrity in our plugin and this fails because there's no term_taxonomy with ID 2.
Change History (4)
This ticket was mentioned in Slack in #core by peterwilsoncc. View the logs.
6 years ago
This ticket was mentioned in PR #8811 on WordPress/wordpress-develop by @vishalkakadiya.
16 months ago
#3
- Keywords has-patch added; needs-patch removed
Changes:
- Update the default link category to be populated as 0, not as 2, as when WordPress is installed, there will not be any default link categories added, unlike the Category taxonomy.
- The above change makes sense to me, as the link feature is not widely used in many WordPress sites and is not default-enabled.
#4
@
16 months ago
I have raised the PR for this ticket - https://github.com/WordPress/wordpress-develop/pull/8811
Changes in PR:
- Update the default link category to be populated as 0, not as 2, as when WordPress is installed, there will not be any default link categories added, unlike the Category taxonomy.
- The above change makes sense to me, as the link feature is not widely used in many WordPress sites and is not default-enabled.
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I've moved this over to the upgrade/install component and added a couple of key words. As mentioned above, it's of fairly low priority.