DB Schema difference

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

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

Open Support Ticket
  • Author
    Posts
  • #452488

    Kai Liu
    Expired Member
    Post count: 368

    I just noticed that the database table columns are different for custom CPT, some has post_address column, some don’t. I did not recall to disable those address setting while creating CPT.

    Attached are screen shots showing table columns of 2 CPTs, they are very different.

    Please advise where is the configuration for database columns?

    Also, the Ajax duplication alert seems not working? I loaded a csv for few thousand records, then accidentally click to other page. I have to reload it again. It seems that the system did not detect any duplication at all, so I have several thousand duplicate records. How to avoid duplicate records during reloading?

    Thanks

    #452500

    Guust
    Moderator
    Post count: 29970

    The Ajax duplication alert addon is only to give an alert for users when they add a listing from the front.
    To avoid duplication, make sure to tick the right options in the import/export section: https://wpgeodirectory.com/docs/core-export/#import

    The configuration of the database columns comes from the custom fields you add.
    If post_address is missing, then I suspect something went wrong somewhere.

    I’ll get a developer to have a look at your question after the weekend.

    Thanks

    #452503

    Kai Liu
    Expired Member
    Post count: 368

    I thought so. I created 8 CPTs, 3 of them have missing address fields (post_address, post_city, post_zip, post_country). They shall be necessary fields for any CPT.

    I have delete those CPTs and drop the associated tables. Will recreate and see

    #452504

    Kai Liu
    Expired Member
    Post count: 368

    I drop the related tables in DB, delete the CPT in GD, when recreating the same CPT, GD remembers the previous setting somehow, including schema. I suspect it could be something went wrong with Link Business process. Those 3 CPTs were linked.

    I have resolved it by dropping the table in DB, deleting CPTs, then at the same page, click Delete Data of the CPT. Well, it generates error message because I already deleted the table so no data to be deleted. But it resolved the issue somehow. I re-create the CPT again, table columns now showing post_address columns.

    there must be bugs in error and exception handling. My bad that I open couple of windows working on different task in GD. That could also be a reason for the DB schema issue (not working on the same CPT tho)

    It worth for your developers to replicate the error and debug it.

    cheers

    #452586

    Kiran
    Moderator
    Post count: 7069
    This reply has been marked as private.
    #452846

    Kai Liu
    Expired Member
    Post count: 368

    Hi Kiran,

    Thanks. I have fixed this as my last message.

    cheers

    Sam

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