-
-
Save tpitre/79bc3fea541dbc759d060c39ddfa202d to your computer and use it in GitHub Desktop.
Byline XML
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<wp:term> | |
<wp:term_id><![CDATA[12068]]></wp:term_id> | |
<wp:term_taxonomy><![CDATA[byline]]></wp:term_taxonomy> | |
<wp:term_slug><![CDATA[kristen-seymour]]></wp:term_slug> | |
<wp:term_parent><![CDATA[]]></wp:term_parent> | |
<wp:term_name><![CDATA[Kristen Seymour]]></wp:term_name> | |
<wp:term_description><![CDATA[In general, the problem may happens for failing on <b>DNS lookup</b> . DNS is that network address that translates the website name to its internet address. Most often it causes for not getting the <b>internet connection</b> or misconfigured internet or network settings. | |
<h2>Heading</h2> | |
Another reason could be the <b>firewall</b> preventing Google Chrome to load the webpage. Also in those cases, you received the error and it says Error code:]]></wp:term_description> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[byline_bio]]></wp:meta_key> | |
<wp:meta_value><![CDATA[]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[byline_title]]></wp:meta_key> | |
<wp:meta_value><![CDATA[]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[byline_photo]]></wp:meta_key> | |
<wp:meta_value><![CDATA[100657]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[byline_email]]></wp:meta_key> | |
<wp:meta_value><![CDATA[]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[byline_facebook]]></wp:meta_key> | |
<wp:meta_value><![CDATA[]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[byline_instagram]]></wp:meta_key> | |
<wp:meta_value><![CDATA[]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[byline_twitter]]></wp:meta_key> | |
<wp:meta_value><![CDATA[]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[profile_photo]]></wp:meta_key> | |
<wp:meta_value><![CDATA[112924]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[_profile_photo]]></wp:meta_key> | |
<wp:meta_value><![CDATA[field_5e2efa66eac2c]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[twitter]]></wp:meta_key> | |
<wp:meta_value><![CDATA[https://twitter.com/T_Armstead72]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[_twitter]]></wp:meta_key> | |
<wp:meta_value><![CDATA[field_5e2f00b3eac30]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[facebook]]></wp:meta_key> | |
<wp:meta_value><![CDATA[https://www.facebook.com/swirlwinesnola]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[_facebook]]></wp:meta_key> | |
<wp:meta_value><![CDATA[field_5e2f0133eac31]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[instagram]]></wp:meta_key> | |
<wp:meta_value><![CDATA[https://www.instagram.com/kevinsharon/]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[_instagram]]></wp:meta_key> | |
<wp:meta_value><![CDATA[field_5e2f0182eac32]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[email]]></wp:meta_key> | |
<wp:meta_value><![CDATA[[email protected]]]></wp:meta_value> | |
</wp:termmeta> | |
<wp:termmeta> | |
<wp:meta_key><![CDATA[_email]]></wp:meta_key> | |
<wp:meta_value><![CDATA[field_5e2f01aaeac33]]></wp:meta_value> | |
</wp:termmeta> | |
</wp:term> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good question. It looks like in the export, WP is prefixing our custom field name with the taxonomy term name. My assumption is that this is for something that is used within WP's infrastructure. I would do it the way it's being filled in here, using only in the non-taxonomy term meta.