Opened 13 years ago
Closed 13 years ago
#20310 closed feature request (invalid)
Add "flush rewrite rules" as note to "save permalinks"-button
Reported by: | F J Kaiser | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | UI | Keywords: | close |
Focuses: | Cc: |
Description
As it seems to be completely unknown, that you can flush your rewrite rules with saving the permalink structure, I suggest to add a note directly below the button on the "Settings" » "Permalinks" screen in the admin UI.
Change History (7)
#3
in reply to:
↑ 1
@
13 years ago
Replying to helenyhou:
Just visiting the Permalinks screen calls
flush_rewrite_rules()
, so not only would the text not be particularly helpful for most users (especially since it's already happened), but it wouldn't be accurate re: saving.
Just found that out after showing this ticket to someone. Still the "problem" remains: People don't know how to flush the rules.
#4
@
13 years ago
Still the "problem" remains: People don't know how to flush the rules.
Regular users should never have to "Flush their rewrite rules", it's not an action that a user needs to perform, as such, adding documentation in the admin on how to do it is useless to anyone other than a new plugin developer, and they should instead be shown the proper way to add rewrite rules and/or how to register post types and taxonomies in such a way that it all just works.
What is the problem that actually needs solving here?
#5
@
13 years ago
Agreed - if a user knows what "flushing rewrite rules" means, they can probably find out (and I've added a note to the Settings Permalinks Screen Codex page). If they don't, then text about it, even in a contextual help tab instead, is likely to be more confusing or possibly alarming than helpful, especially to a non-technical type.
#6
@
13 years ago
Replying to dd32:
Regular users should never have to "Flush their rewrite rules",
The problem started with the famous »Even a caveman can do it«. WordPress has a big community of people who don't know how to code. But since this sentence nothing holds them back. (Ok, it wasn't only that sentence.)
and they should instead be shown the proper way to add rewrite rules and/or how to register post types and taxonomies in such a way that it all just works.
That's a problem of documentation. I added a lot to Codex, but sometimes I think, that basic things could be noted directly in the UI - visible for admins only - as well and would make things much easier. At least this is just a thought.
What is the problem that actually needs solving here?
Well, it's not really a problem. I wrote »problem« (with quotes) for a reason. And I didn't reopen the ticket. There're just a lot of questions out there that end with "Ah! I didn't know where I could flush the rules" and "Ah! Ok, if I shouldn't flush the rules programmatically on every page load, how should I do it then?".
#7
@
13 years ago
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
- Version 3.3.1 deleted
Neither of those can be solved by directing people to load the permalinks page, so text there is useless, so I'll close this ticket then.
The Codex is the correct place to document how to flush rewrite rules and/or register post types, If the examples there are not correct, feel free to update them, or let me know and I'll look at it if I've got some time.
Just visiting the Permalinks screen calls
flush_rewrite_rules()
, so not only would the text not be particularly helpful for most users (especially since it's already happened), but it wouldn't be accurate re: saving.