Strange Bug

This topic contains 6 replies, has 2 voices, and was last updated by  Kai Liu 5 years, 3 months ago.

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

Open Support Ticket
  • Author
    Posts
  • #465382

    Kai Liu
    Expired Member
    Post count: 368

    Just freshly loaded a CPT data into GD V1.

    Listing appears in CPT categories, showing correct count. However, when going to ALL listing page, those new listings are not show default image, and every link is a dead link 404, cannot link to detail page of the listing at all.

    Please advise what would cause this? Any remedy or do i have to wipe out the whole CPT data and reload again?

    Thanks

    Sam

    #465383

    Kai Liu
    Expired Member
    Post count: 368
    This reply has been marked as private.
    #465394

    Guust
    Moderator
    Post count: 29970

    You do not have street addresses for the listings (add anything you like, but they cannot be blank).

    #465395

    Kai Liu
    Expired Member
    Post count: 368

    Oh, is that what causing this?

    That is easy fix. But need to wipe out and reload. Much quicker that way

    Thanks

    #465397

    Kai Liu
    Expired Member
    Post count: 368

    Hi Guust,

    Just checked csv fike, tgere is no blank address in any of the listing. Must be import error again

    #465398

    Kai Liu
    Expired Member
    Post count: 368

    Found issue. This is the second time I encounter this issue.

    I just checked database, in geodir_CPT_details, for this category, there is no address fields in db table at all. The second time.

    Last time I have to delete the CPT, recreate it again to get proper table created.

    #465401

    Kai Liu
    Expired Member
    Post count: 368

    Deleted the CPT, and all dependent listings, recreated it again. Now, checking in database, table fields are double of previously checked. Address fields are all there.

    Would it be some bugs in creating the table while creating CPT? Anyway, that is in V1, both incidents happened in V1, you might not need to worry too much as you are working on V2 now. Just to let you know

Viewing 7 posts - 1 through 7 (of 7 total)

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

Open Support Ticket