WordPress.org

Forums

Types - Custom Fields and Custom Post Types Management
Errors after adding custom post type (6 posts)

  1. jsharkey90
    Member
    Posted 1 year ago #

    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/

  2. Ovidiu Nicolae
    Member
    Posted 1 year ago #

    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.

  3. jsharkey90
    Member
    Posted 1 year ago #

    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.

  4. Ovidiu Nicolae
    Member
    Posted 1 year ago #

    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

    Hope this helps.

  5. jsharkey90
    Member
    Posted 1 year ago #

    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"??

  6. Ovidiu Nicolae
    Member
    Posted 1 year ago #

    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.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.