We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello I have a problem when using the tool to export and import my post type that has the metabox.
when using metabox the xml file that the tools / export creates is as follows.
WRONG <wp: postmeta> <wp: meta_key> <! [CDATA [nfe_issued_mb_pdf_file]]> </ wp: meta_key> <wp: meta_value> <! [CDATA [11]]> </ wp: meta_value> </ wp: postmeta>
as would be the right meta_volue have the way of attachment as below.
<wp: postmeta> <wp: meta_key> <! [CDATA [_wp_attached_file]]> </ wp: meta_key> <wp: meta_value> <! [CDATA [2015/12 / CODE-OF-THE-ENVIRONMENT-IPI.pdf]]> </ wp: meta_value> </ wp: postmeta>
ie to import the xml it does not indicate to me the attached file via metabox
Somebody help me, please?
The text was updated successfully, but these errors were encountered:
The meta for media fields stores the id of the files, not the files themselves
Sorry, something went wrong.
No branches or pull requests
Hello I have a problem when using the tool to export and import my post type that has the metabox.
when using metabox the xml file that the tools / export creates is as follows.
WRONG
<wp: postmeta>
<wp: meta_key> <! [CDATA [nfe_issued_mb_pdf_file]]> </ wp: meta_key>
<wp: meta_value> <! [CDATA [11]]> </ wp: meta_value>
</ wp: postmeta>
as would be the right meta_volue have the way of attachment as below.
<wp: postmeta>
<wp: meta_key> <! [CDATA [_wp_attached_file]]> </ wp: meta_key>
<wp: meta_value> <! [CDATA [2015/12 / CODE-OF-THE-ENVIRONMENT-IPI.pdf]]> </ wp: meta_value>
</ wp: postmeta>
ie to import the xml it does not indicate to me the attached file via metabox
Somebody help me, please?
The text was updated successfully, but these errors were encountered: