GT to GD conversion: some Custom Fields are now NULL

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

Open Support Ticket

Author

Posts
March 27, 2017 at 5:08 pm #370177
Stiofan O’Connor
Site Admin

Post count: 22956
@JJJ
```
NOTICE: If you are having this site show in your admin area, please edit functions.php and comment out or remove the following 3 lines:
add_action("admin_head", "checkForUpdates");
add_action("admin_head", "showNotifications");
require_once(TEMPLATEPATH . '/update.php');
```
March 28, 2017 at 4:19 am #370273

Kiran
Moderator

Post count: 7069

Hello JJJ,

> I forgot the screenshot for display of GPF Page in Back-end.
Here it is. Does it display the same for you?
<
It showing to me correctly. See attachment.

> what about the display when GT is working: display of the home page of http://wpgeodirectory.com site?! Have you seen it?
<
See above post by Stiofan for solution.
I have already fixed it on http://www.jjj38.byethost10.com/. Did you checked?

Please follow this if you have not: https://wpgeodirectory.com/geotheme-to-geodirectory/

NOTE:
In case you are going for conversion on another site then http://www.jjj38.byethost10.com/.
Please use recent geodir_gt2gd plugin files from your current site /plugins/geodir_gt2gd.

Kiran

March 28, 2017 at 2:26 pm #370400

JJJ
Expired Member

Post count: 80

Hi guys,

Thanks for the solution Stiofan!:)

Kiran :
– Field settings are now like yours when zooming out the browser. Good! 🙂
– I haven’t seen Stiofan solution fixed on jjj… site since you performed the conversion. Thank you anyway, I ‘ll look for the changes.
– Finally, thank you for the note!;)

One more question about this Kiran:
From now, if I export the cpf-well-converted listings on a site that has previously wrong-cpf-converted listings, geodir_dg_place_detail columns does not update correctly.
How would you do the trick then (erase all wrong-cpf-converted listings and import new one? erase cpf table and import new corresponding table?….)

Cheers,
JJJ

March 29, 2017 at 6:31 am #370516

Kiran
Moderator

Post count: 7069

You can not import just one or two table from one site to another. Because each table records are linked with other tables records by ids. So if you import only detail then there will be mis-match between detail table & other tables.

If you still want to import correctly converted data to another site then you have to import all DB tables (like geodir_custom_fields, geodir_gd_place_detail, geodir_gd_event_detail, geodir_event_schedules etc…). Try this and check if it works otherwise you have to do that i told in “NOTE:” in my last reply.

Kiran

March 29, 2017 at 10:54 am #370539

JJJ
Expired Member

Post count: 80

Hi Kiran,

Thank you.
As you suggest, I import all the GD tables (only). It seems to work…
Anything need in _post_meta kind of tables or other tables according to you?

Instead, through back-end, any tricks to make it carefully ? like for instance:
1) erasing all previously wrong-converted listing,
2) import cvs of the new ones.
3) and in between maybe go in DB and just update _geodir_custom_post_field, so that it corresponds to the new listing column?

Do you see what I mean? The idea is to solve the problem of new well written CPF between the old and the new listings.

Cheers,
JJJ

March 29, 2017 at 11:01 am #370540

Kiran
Moderator

Post count: 7069

The problem was in only custom fields table & details table. So compare post meta values in post_meta table if they are correct and linked to correct post then no need to import values in post_meta table.

Now you can manage listing via GD Import/Export by export CSV -> edit -> import CSV again will fix all the data.

March 29, 2017 at 11:16 am #370546

JJJ
Expired Member

Post count: 80

Good, I will check the values as you said.
On the second point I’m not sure to understand. Do you mean:
Export correct data, Edit AND ?, then import the correct data to update the incorrect ones?
Without the editing step I tried, the CPF does’t update and “new CPF” are not created.

March 29, 2017 at 11:20 am #370548

Kiran
Moderator

Post count: 7069

New custom fields are only created during conversion that’s why i told you “If you still want to import correctly converted data to another site then you have to import all DB tables (like geodir_custom_fields, geodir_gd_place_detail, geodir_gd_event_detail, geodir_event_schedules etc…).”

March 29, 2017 at 11:45 am #370557

JJJ
Expired Member

Post count: 80

ok I see.
Btw I am really sorry to bother you with all that Kiran 🙂

So I am asking last : then don’t you think a mix back-end/DB solution (that will avoid pure DB copy/past and eventually missing something in meta value table or more) :
1) erase and copy just geodir_custom_post_field table
2) and do the listings job though back-end : export / import well converted listings

will ensure everything works?
Cheers,
JJJ

March 29, 2017 at 11:52 am #370559

Kiran
Moderator

Post count: 7069

No it is not sure that work successfully with the way you are going. That’s why i already asked previously that “Try this and check if it works otherwise you have to do that i told in “NOTE:” in my last reply.”

Most safest way i told you in Note: at https://wpgeodirectory.com/support/topic/gt-to-gd-conversion-some-custom-fields-are-now-null/page/3/#post-370273

Thanks,
Kiran

March 29, 2017 at 12:31 pm #370571

JJJ
Expired Member

Post count: 80

ok, fair enough!

Thank you very much for your all help Kiran and specially your effort to understand what I was saying ;).

Have a good day.
Cheers,
JJJ
Author

Posts