Timeline for Where, When, & How to Properly Flush Rewrite Rules Within the Scope of a Plugin?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2014 at 19:34 | comment | added | Nicolai Grossherr | The difference is minor indeed, especially if the transients is permanent, non-expiring, but of course transients have other capabilities, benefits that are nice to have. @MatthewLee | |
| Feb 15, 2014 at 17:59 | comment | added | MatthewLee | This was very helpful. I had a similar situation to Michael. I ended up incorporating helga's suggestion on using a transient and I set it in the validation function for the settings. I ended up needing to set the transient to false after flushing or else it just kept flushing on every admin page load until the transient expired. So functionally using an option or a transient was the same. I guess transient might be nice just to keep the options table a little cleaner. But a minor point. | |
| Nov 27, 2013 at 22:11 | comment | added | Nicolai Grossherr |
You're of course right about transient, I guess I opted for *_option() because of settings page. @helgatheviking
|
|
| Nov 17, 2013 at 0:23 | comment | added | helgatheviking | Or you could use a transient maybe? But definitely +1 for not flushing the rules on every admin_init. | |
| Nov 15, 2013 at 19:02 | history | edited | Nicolai Grossherr | CC BY-SA 3.0 |
added 3 characters in body
|
| Nov 15, 2013 at 18:54 | history | edited | Nicolai Grossherr | CC BY-SA 3.0 |
deleted 36 characters in body
|
| Nov 15, 2013 at 18:47 | history | answered | Nicolai Grossherr | CC BY-SA 3.0 |