mark500
Forum Replies Created
-
Ok, I see, thank you.
Haha, that’s the difference from free and paid plugin developers. The latter would never direct their user to a competitive product, if they would see it would solve their problem. They are income oriented, but you actually care to solve users’ problems. Thank you.
Can both plugins be used at the same time – do they write to the same WordPress “tables” (I don’t have many knowledge on this subject)?
Anyway I think I’m still gonna use PODS though xD
Forum: Plugins
In reply to: [Pods - Custom Content Types and Fields] Import relationshipsYes, it does help! Thank you for explaining this to me.
I’ve contacted CIO’s support and they are helping me figure it out how to achieve this.
P.S.: On the side note, they wrote:
By the way, due to a bug in pods two way relationships, some customers experience issues when importing two-way relationship fields. The issues were gone when changing the fields to one way relationship. You may consider using one-way relationship (one to one, or one to many), and use custom template/custom query to list the related items. PODS two-way relationship fields write index twice, not efficient, and are difficult to scale when the data accumulates.
Do you know what they are talking about, maybe this is a new bug or already fixed?
Forum: Plugins
In reply to: [Pods - Custom Content Types and Fields] Import relationshipsI found some instructions on the web for the combination of WP All import & CIO Custom Fields Importer plugin, but i still can’t make it work:
https://vipp.com.au/cio-custom-fields-importer/how-to-match-and-import-relationship-fields-into-pods/It gives this example of importing relationships into pods:
—————————————
Example 3, custom field related to a custom field using pods table storage
For example if you have a custom field related to the “translations” field of custom post type “book”, and you created the “book” custom post type using pods table storage, (storing custom fields in a separate table instead of wp_postmeta table). You have a source CSV file and the translations are stored in a column called “translations_available”. The actual translations are separated by a comma.
When you import, you can write in the import template:
MATCH in PODS TABLE ( translations : {translations_available[1]} )
or
MATCH for item id in PODS TABLE, from column translations ( translations : {translations_available[1]} )
—————————————
Is this “import template” supposed to be the field in the WP All import plugin? I’ve tried it, but doesn’t seem to work…
Any help?