Linked types do not migrate
This topic contains 31 replies, has 5 voices, and was last updated by Kiran 6 years, 11 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
November 23, 2018 at 2:48 pm #455621
I’ve just run a v2 test update and linked data is not staying linked. Am i missing something or is this feature not supported yet?
November 23, 2018 at 4:50 pm #455658Can you say more? What addon are you updating, V what to what?
November 23, 2018 at 5:07 pm #455667I can give you a login too, but:
gd_blogs -> links to -> gd_places
gd_events -> links to -> gd_placesBut when I upgrade to v2, that connection is gone.
1. It doesn’t set up the custom field to reflect how the linking works in v2
2. If you add the custom field ‘Linked post: places’ the data doesn’t show
3. The connections don’t exist in the geodir_cp_link_posts tableNovember 23, 2018 at 5:12 pm #455670Rather.. there is *some* data in geodir_cp_link_posts, but the linkedID doesn’t exist.
November 24, 2018 at 11:17 am #455762I’ll flag this for kiran to look at on Monday, as far as i know the conversion was done and that should work.
Thanks,
Stiofan
November 24, 2018 at 2:13 pm #455764Dang I was really hoping to get this done over the weekend. I’ll run a few more test upgrades and see if I can work out the pattern. Thanks!
November 24, 2018 at 6:59 pm #455783Curiouser and curiouser.. I just ran another migration and the geodir_cp_link_posts table doesn’t exist at all.
I do wonder if it’s something to do with packages, and or the non-creation of the appropriate custom field to link them before populating the data.
November 24, 2018 at 7:17 pm #455785And neither category nor linked posts are saving.
November 26, 2018 at 12:55 pm #455944gentle nudge 🙂
November 26, 2018 at 1:33 pm #455948This reply has been marked as private.November 26, 2018 at 1:41 pm #455952Hi
That’s okay I’ll wait for the updated code. I’m happy to be a tester for you too if you want to send zips. Any idea of a timeline on this?
If I export all and reimport all, is that a viable workaround?
November 26, 2018 at 2:12 pm #455955Hello,
That’s okay I’ll wait for the updated code. I’m happy to be a tester for you too if you want to send zips. Any idea of a timeline on this?
The script will run if you are going v1 to v2 conversion 1st time. For existing converted site i need to do it manually. That’s way i asked for FTP & DB credentials, so i can apply patch on your site.
If I export all and reimport all, is that a viable workaround?
Can you clarify what data you asking about export/reimport?
Kiran
November 26, 2018 at 2:20 pm #455956That’s okay — I’ve only been running this on clone sites so far until it’s right — I didn’t want to take any risks with the data!
With export > import I was thinking that perhaps it would handle the data more cleanly this rather than a direct upgrade; but ignore it, it was just a thought.
November 27, 2018 at 2:00 pm #456074Hello Nick,
Here is patch to fix link post types v1 to v2 conversion data. Patch: https://github.com/AyeCode/geodirectory/pull/521/commits/e621ec1d38c8cd32722c83867b9d6eaf902c0f5d
After applying this patch, you can try v1 to v2 conversion on your clone site which have not performed v1 to v2 conversion before.Please follow instructions given here for conversion: https://wpgeodirectory.com/docs-v2/geodirectory/installation/#convert
Kiran
November 27, 2018 at 4:24 pm #456094Is this patch included in .38?
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket