Timeline for Creating a Custom Post Type as a Plugin? Why?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:37 | history | edited | CommunityBot |
replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/
|
|
| Sep 24, 2013 at 21:03 | history | edited | fuxia♦ | CC BY-SA 3.0 |
added 467 characters in body
|
| Sep 18, 2013 at 16:53 | history | edited | fuxia♦ | CC BY-SA 3.0 |
added 4 characters in body
|
| May 11, 2013 at 22:12 | comment | added | fuxia♦ | The simple answer is: Custom post types work better in plugins. | |
| May 11, 2013 at 22:11 | comment | added | sleeper | Ok, so no "simple" answer to this question, eh? The link seems to provide the best info on how to "decide" where to put the CPT (based on several variables). | |
| May 11, 2013 at 22:04 | comment | added | sleeper | "Where to put my code: plugin or functions.php?" - Excellent discussion. Seems I've stumbled into a Hornet's Nest. | |
| May 11, 2013 at 22:00 | history | edited | fuxia♦ | CC BY-SA 3.0 |
added 109 characters in body
|
| May 11, 2013 at 21:59 | comment | added | sleeper | "The theme isn’t loaded when the constant SHORTINIT is set to TRUE (custom AJAX handlers, importers or APIs), no posts can be added to such a custom post type or taxonomy." ??? I have no idea what that means (yet). I'm just getting into CPT's. Please explain. | |
| May 11, 2013 at 21:54 | history | answered | fuxia♦ | CC BY-SA 3.0 |