"New Custom Post Type" Error

This topic contains 5 replies, has 3 voices, and was last updated by  Kiran 6 years, 9 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • August 10, 2017 at 2:27 pm #390535

    geokreuz
    Buyer
    Post count: 21

    I just created a fifth custom post type for my site but it does not work properly.

    I am getting this error when I try to create a New Sample Post.

    Warning: end() expects parameter 1 to be array, boolean given in /”website name”/wp-content/plugins/geodirectory/geodirectory-functions/taxonomy_functions.php on line 1635.

    Also,
    this post type does not give me the option to create a “Category Top Description”, a map Icon, a Default image and does not let me choose a Schema Type.

    Other Customer post types I created a month ago work just fine.

    August 10, 2017 at 2:34 pm #390539

    geokreuz
    Buyer
    Post count: 21
    This reply has been marked as private.
    August 10, 2017 at 6:36 pm #390584

    Paolo
    Site Admin
    Post count: 31206

    Hi,

    this is weird and I suspect it is caused by a conflict with another plugin. Did you try to disable all non gd plugin for a second to see if the problem persists?

    Let us know,

    Thanks

    August 10, 2017 at 9:23 pm #390611

    geokreuz
    Buyer
    Post count: 21

    Okay thanks

    I’ll try that in a few hours.

    I’ll keep you updated.

    August 11, 2017 at 3:19 am #390643

    geokreuz
    Buyer
    Post count: 21

    I got it working but due to another reason.

    I don’t think the Custom Post Type liked my name (slug & taxonomy) and it must have created a conflict somewhere.

    My Custom Post Slug was supposed to be “tag_sale” or “tagsale” and the taxonomies was supposed to be “tag-sales” or “tagsales”. The only thing I can think of is that it does not like the use of the word TAG.

    When I changed the SLUG & Taxonomies to “garagesales” and “garage_sale” it works fine, like the others.

    …anyway, all better now.

    Thanks!

    August 11, 2017 at 6:46 am #390658

    Kiran
    Moderator
    Post count: 7069

    Hi There,

    Thanks for letting us know.

    BTW we have fixed this problem. Use of tag string in post type name conflicting with the tag taxonomy (gd_xxxx_tags). But now we have fixed it and it will be reflected in next release.

    Kiran

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket