Title: Errors after adding custom post type Last modified: August 21, 2016 --- # Errors after adding custom post type * [jsharkey90](https://wordpress.org/support/users/jsharkey90/) * (@jsharkey90) * [12 years, 11 months ago](https://wordpress.org/support/topic/errors-after-adding-custom-post-type/) * below are the error messages that display after I click the button to save the new post type… please let me know if this is a stupid mistake and can easily be fixed… I’ve reinstalled the plugin multiple times but that did not seem to help. * Warning: array_combine() [function.array-combine]: Both parameters should have at least 1 element in /home/content/68/11389868/html/jacksharkey/wp-content/plugins/ types/wpcf.php on line 170 * Warning: array_merge() [function.array-merge]: Argument #1 is not an array in/ home/content/68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php on line 170 * Warning: array_merge() [function.array-merge]: Argument #2 is not an array in/ home/content/68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php on line 177 * Warning: array_merge() [function.array-merge]: Argument #2 is not an array in/ home/content/68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php on line 177 * Warning: in_array() expects parameter 2 to be array, null given in /home/content/ 68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php on line 179 * Warning: array_combine() [function.array-combine]: Both parameters should have at least 1 element in /home/content/68/11389868/html/jacksharkey/wp-content/plugins/ types/wpcf.php on line 170 * Warning: array_merge() [function.array-merge]: Argument #1 is not an array in/ home/content/68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php on line 170 * Warning: array_merge() [function.array-merge]: Argument #2 is not an array in/ home/content/68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php on line 177 * Warning: array_merge() [function.array-merge]: Argument #2 is not an array in/ home/content/68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php on line 177 * Warning: in_array() expects parameter 2 to be array, null given in /home/content/ 68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php on line 179 * Warning: Cannot modify header information – headers already sent by (output started at /home/content/68/11389868/html/jacksharkey/wp-content/plugins/types/wpcf.php: 170) in /home/content/68/11389868/html/jacksharkey/wp-includes/pluggable.php on line 876 * [http://wordpress.org/extend/plugins/types/](http://wordpress.org/extend/plugins/types/) Viewing 5 replies - 1 through 5 (of 5 total) * [Ovidiu Nicolae](https://wordpress.org/support/users/ovinic/) * (@ovinic) * [12 years, 11 months ago](https://wordpress.org/support/topic/errors-after-adding-custom-post-type/#post-3917504) * It is a known bug of the current 1.3.1 version and it is already fixed in the next release. However I do not know when it will be updated, probably very soon; maybe someone from support can tell us. * Thread Starter [jsharkey90](https://wordpress.org/support/users/jsharkey90/) * (@jsharkey90) * [12 years, 11 months ago](https://wordpress.org/support/topic/errors-after-adding-custom-post-type/#post-3917509) * ah, well that clears that up then – thanks!… I already went through uninstalling wordpress and setting everything back up again and it still occurred (at which point I almost put a hole through my screen) so thank you for letting me know. I will be eagerly anticipating in the meantime. * [Ovidiu Nicolae](https://wordpress.org/support/users/ovinic/) * (@ovinic) * [12 years, 11 months ago](https://wordpress.org/support/topic/errors-after-adding-custom-post-type/#post-3917510) * No problem. If you can’t wait until the fix is submitted to the repository you can enable debug mode and debug log. The errors will be logged into a file. After you are done creating your custom post types and taxonomies you can just disable debug mode and you’re all set. The errors only occur when saving or editing. * More details here: [http://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_debugging](http://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_debugging) * Hope this helps. * Thread Starter [jsharkey90](https://wordpress.org/support/users/jsharkey90/) * (@jsharkey90) * [12 years, 11 months ago](https://wordpress.org/support/topic/errors-after-adding-custom-post-type/#post-3917512) * Sweet, definitely does help (got sick of seeing the errors appear). Thanks!!…. * Also, just out of curiosity – the errors that occur aren’t actually anything that will need to be fixed on my end later/actually something bad right? i.e. nothing is actually going wrong, but certain functions are receiving arguments they consider “invalid”?? * [Ovidiu Nicolae](https://wordpress.org/support/users/ovinic/) * (@ovinic) * [12 years, 11 months ago](https://wordpress.org/support/topic/errors-after-adding-custom-post-type/#post-3917513) * Nope, you won’t have to fix anything at your end. The plugin actually works, but it keeps throwing those warnings when saving a custom post type (which is actually being saved, despite the errors). Hopefully it will be updated soon. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Errors after adding custom post type’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/types_ced1d3.svg) * [Toolset Types - Custom Post Types, Custom Fields and Taxonomies](https://wordpress.org/plugins/types/) * [Frequently Asked Questions](https://wordpress.org/plugins/types/#faq) * [Support Threads](https://wordpress.org/support/plugin/types/) * [Active Topics](https://wordpress.org/support/plugin/types/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/types/unresolved/) * [Reviews](https://wordpress.org/support/plugin/types/reviews/) * 5 replies * 2 participants * Last reply from: [Ovidiu Nicolae](https://wordpress.org/support/users/ovinic/) * Last activity: [12 years, 11 months ago](https://wordpress.org/support/topic/errors-after-adding-custom-post-type/#post-3917513) * Status: not resolved