JJJ

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 48 total)
  • Author
    Posts
  • March 27, 2017 at 2:27 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #370118

    JJJ
    Expired Member
    Post count: 80

    ps: what about the display when GT is working: display of the home page of http://wpgeodirectory.com site?! Have you seen it?

    March 27, 2017 at 2:25 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #370116

    JJJ
    Expired Member
    Post count: 80
    This reply has been marked as private.
    March 24, 2017 at 5:06 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #369631

    JJJ
    Expired Member
    Post count: 80
    This reply has been marked as private.
    March 24, 2017 at 4:49 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #369622

    JJJ
    Expired Member
    Post count: 80
    This reply has been marked as private.
    March 24, 2017 at 2:30 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #369572

    JJJ
    Expired Member
    Post count: 80
    This reply has been marked as private.
    March 24, 2017 at 12:29 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #369510

    JJJ
    Expired Member
    Post count: 80

    Hi again Kiran,
    I am afraid it behaves the same than before! 🙁

    Multiselect CPFields stands as a problem: values are not recorded in tables (NULL instead, see geodir_Bars for instance).

    As a sign, on the front-end: these infos should appear in “More Info” (on Detail Pages), as it is set by parameters. And it does not.
    Btw have you seen how CPF parameters pages (in back-end) is displayed? Look stretched to me…

    Cheers,
    JJJ

    March 24, 2017 at 11:43 am in reply to: GT to GD conversion: some Custom Fields are now NULL #369495

    JJJ
    Expired Member
    Post count: 80

    Hi Kiran,

    Thank you very much!
    I will check right away.
    What was the problem: config. of my listings or GTtoGD addon problem?

    What do you mean by patch and how keep trace of it (do you mean changes in GTtoGD addon) ?
    So now, I can convert other listings right?

    Cheers,
    JJJ

    March 23, 2017 at 11:10 am in reply to: GT to GD conversion: some Custom Fields are now NULL #369279

    JJJ
    Expired Member
    Post count: 80
    This reply has been marked as private.
    March 23, 2017 at 10:56 am in reply to: GT to GD conversion: some Custom Fields are now NULL #369275

    JJJ
    Expired Member
    Post count: 80
    This reply has been marked as private.
    March 22, 2017 at 7:24 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #369201

    JJJ
    Expired Member
    Post count: 80
    This reply has been marked as private.
    March 21, 2017 at 5:48 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #368900

    JJJ
    Expired Member
    Post count: 80

    You’re welcome. Thank YOU :)!
    Looking forward to knowing what happens.
    Cheers,
    JJJ

    March 21, 2017 at 4:13 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #368865

    JJJ
    Expired Member
    Post count: 80
    This reply has been marked as private.
    March 19, 2017 at 1:39 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #368448

    JJJ
    Expired Member
    Post count: 80

    Hi 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,
    JJJ

    March 17, 2017 at 3:23 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #368108

    JJJ
    Expired Member
    Post count: 80

    Hi 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,
    JJJ

    March 17, 2017 at 1:27 pm in reply to: GT to GD conversion: some Custom Fields are now NULL #368024

    JJJ
    Expired Member
    Post count: 80

    Hi 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,
    JJJ

  • Author
    Posts
Viewing 15 posts - 16 through 30 (of 48 total)