#2938 closed enhancement (fixed)
Don't have a category selected by default
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 2.1 | Priority: | low |
Severity: | minor | Version: | 2.0.4 |
Component: | Administration | Keywords: | bg|has-patch commit |
Focuses: | Cc: |
Description
It drives me nuts having to uncheck the box next to my default category when writing a new post if I don't want it in that category.
How about we just don't check any boxes off the bat and only then if the user doesn't pick any categories, we assign it to the default category?
I see no drawback to doing this. Does anyone else?
I'll have a patch shortly probably.
Attachments (2)
Change History (12)
#2
@
19 years ago
I found a trick to get TortoiseSVN to think the file has changed. Rename edit-form-advanced.php to something like edit-form-advanced1.php. Then run an update and tortoiseSVN will restore the file. Delete that file and rename edit-form-advanced1.php back to edit-form-advanced.php and it should show a red exclamation point. Then you can create the patch. That's what I do all the time.
#3
@
19 years ago
I've attached the JS I have used previously to do this.
I have conflicted opinions about what the core should do.
#4
@
19 years ago
If anyone's interested, here is my plugin that uses JavaScript to uncheck the default category, if someone checks another.
#5
@
18 years ago
- Keywords commit added
- Owner changed from anonymous to markjaquith
- Status changed from new to assigned
+1
Default category will be selected if the post is published with no category selected... no need to pre-select the default. I often forget to uncheck the default one so my posts go in "Foo and Uncategorized."
Well, I edited
/wp-admin/edit-form-advanced.php
, but TortoiseSVN is being retarded and not realizing that I made any changes which means I can't make a patch.So instead, here's the needed code change (on line 77):
to this:
I tested it and it seems to work fine. :)