News for hackers. Stuff that matters.
Re:Popular WordPress plugin comes with a backdoor, steals si... by jawngee on Saturday March 05, 2016 @09:33PM (#11232213)
Yes, you should because dealing with keeping that in sync between dev, staging, production is a major hassle.

If you are changing your theme and using custom post types, you still have to modify the theme to support the custom post types. So copy and paste, or isolate the custom post types to a separate file and include in your functions.php.

If you're doing it any other way, then you honestly don't really know what you are doing.

Re:Popular WordPress plugin comes with a backdoor, steals si... by CM30 on Sunday March 06, 2016 @06:58AM (#11233457)
Not really. If you're not running a test site, put the theme and custom plugins inside another folder and commit that to Git or SVN. If you are running a test site, oommit the wp-content folder, with the uploads directory and any third party code set as ignored.

And the way I suggest is also what a lot of WordPress experts suggest, as seen here:

http://justintadlock.com/archives/2013/09/14/why-custom-post...

http://www.wpbeginner.com/opinion/wordpress-custom-post-type...

https://www.smashingmagazine.com/2012/11/complete-guide-cust...

Re:Popular WordPress plugin comes with a backdoor, steals si... by joeguilmette on Sunday March 06, 2016 @03:19AM (#11232935)
There are pros and cons for both methods.

Personally, I much prefer to put functionality in a plugin and the theme limited to the frontend presentation. To suggest that I don't know what I'm doing is, well... Incorrect.

Syncing production, staging, and dev is an unrelated and solved problem.