GT to GD conversion: some Custom Fields are now NULL
This topic contains 40 replies, has 3 voices, and was last updated by JJJ 8 years ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
March 16, 2017 at 3:27 pm #367768
Hi there,
I converted GT to GD almost 2 month ago on my stage site.
And I just realized yesterday that some of the Places Custom Field that was set are now NULL (in Database), namely those for which you have to choose values (“Select”).
Any explanation/solution?
Cheers,
JJJMarch 16, 2017 at 4:42 pm #367798Hi JJJ,
I can only guess something was not formatted as expected and it failed.
How many listing do you have? is it something where you can export , fix and then re-import?Thanks,
Stiofan
March 17, 2017 at 1:27 pm #368024Hi Stofian,
Thanks for your quick reply.
I looked back on how I did the conversion(GTtoGD) on my stage site, and these are some conclusions:1) It appears that I was not using the last version of GTtoGD to convert my listings, but version 1.0.1. (Really couldn’t expect for such a fundamental process there would be versions!^^…)
And in this final version, apparently some Custom Post Fields problems have been fixed. Good!2) During the conversion, the process was not ending at all…
I thought it was a matter of max_execution_time/… (see one of my previous post about conversion). So I reloaded the process twice, and finally had all my listings. (maybe truncated of some Custom Post Fields then !!!…)
Well, don’t know exactly if this was the problem in fact, or if I was not waiting enough (I have about 1800 listings).But in the final version, timeout is apparently fixed, and you can even follow the process with the loading bar. Good news too!
So I’ve just tried to do the conversion on a local environment:
– The process manages to end!
– But Custom Post Field have not been converted at all.
On this point, I think it is because of some of unicode stuff (comma,etc…) set by the local env.Now here is my question (and I thing it was the sense of your questions too):
Should I try to do the conversion on a crash stage environment (with the last version of GTtoGD) and then include the corresponding converted tables to the database I am using on my current stage site?
Should I do the “exchange” with help of csv files? or through the database itself (in this case, which tables to remove and replace?)?Thanks in advance for help.
Cheers,
JJJMarch 17, 2017 at 2:34 pm #368096Hi JJJ,
If you have not had many changes to your posts since you converted it might be work trying it on a staging site until you get it right, other wise if you have already got lots of changes it might be better to export and import but that could be a much longer process.
Stiofan
March 17, 2017 at 3:23 pm #368108Hi again Stiofan,
Not sure to have it sorry 🙂
What I meant is :
I have one staging site to try things online : convert my initial GD data into GD’s ones (wrongly apparently !), set the GD parameters, setup a new theme, creat new pages and so on …
My question is : if I am using another staging env. to convert my initial GT data into GD (in a hopefully good way this time), how could I integrate them to the staging site I am currently working on? import/export is what you said? Or is it necessary to start the work from the beginning … :(?
Cheers,
JJJMarch 17, 2017 at 3:26 pm #368110If you get it working on a staging site then you could export listings from there and import into the live one, or you could simply switch the whole Database.
Stiofan
March 19, 2017 at 1:39 pm #368448Hi Stiofan,
Thanks for reactivity.
Ok, so I started the conversion from scatch on the staging site, with help of last version of GTtoGD.Same problems, in the _geodir_gd_places_detail table of the DB : CP Fields set as Multiselect are either NULL (when values are expected) or have nothing in it (when no values are expected, normal behaviour I guess).
The values are well recorded in _geodir_custom_field btw.In the original DB (with GT on), in _post_meta table: everything seems to be ok, meta keys/values are well assigned to the corresponding places id.
Any idea? Anything related with the extra-field called “Select” in _geodir_custom_field (whereas before It was needed to maintain the Ctrl tab to select values)?
Cheers,
JJJMarch 20, 2017 at 1:27 pm #368582Can you give us full access to the staging site, FTP and wp-admin and we will take a look.
Thanks,
Stiofan
March 21, 2017 at 4:13 pm #368865This reply has been marked as private.March 21, 2017 at 4:59 pm #368886I will flag this for Kiran to look at tomorrow, thanks for the info 🙂
Stiofan
March 21, 2017 at 5:48 pm #368900You’re welcome. Thank YOU :)!
Looking forward to knowing what happens.
Cheers,
JJJMarch 22, 2017 at 5:10 am #368988Hi JJJ,
Looked into your site backend and found all GD2GD Conversion steps done. But to find problem with custom fields, we need to perform conversion from our side. So please provide us site with original database where we can perform conversion to find what causes problem.
Also provide us database(phpMyAdmin) details so i can check old database data.Thanks,
KiranMarch 22, 2017 at 7:24 pm #369201This reply has been marked as private.March 23, 2017 at 6:31 am #369244This reply has been marked as private.March 23, 2017 at 10:56 am #369275This reply has been marked as private. -
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket