randyhoyt

It sounds like the best approach will be to temporarily add a dropdown on all the subordinate posts like in this article …

https://janina.tumblr.com/post/3588081423/post-parent-different-type

… and then edit each sub post individually to select the parent. After that, you can remove the dropdown and edit them in the sub post popup.

(1) EXISTING POSTS: How are they connected now? Do you have the parent specified in a custom field? Here are some ideas:

* The fastest way to do it is to write a SQL statement to update the post_parent field on the posts table with the corresponding value from the postmeta table.

* If that sounds too complicated, then check out this code snippet: [https://janina.tumblr.com/post/3588081423/post-parent-different-type]. If you set it up correctly, will give you a dropdown field when editing the Bio where you can pick the parent Artist.

—- You’ll have to manually edit each one and save it, but it should be easier than recreating them all. Worst case, you’d have to select the parent artist from the dropdown …

—- … but if you are really clever with that technique, you can change the code that says ‘selected’ => $post->post_parent to something like ‘selected’ => get_post_meta($post->ID, “artist_id”, true) so that the parent is automatically selected. You’d just have to open every sub post record and hit save to get the connection established.

(2) DISPLAYING CHILDREN: You’ll want to use get_posts: [https://codex.www.ads-software.com/Template_Tags/get_posts] Specify the child post type for the post_type parameter, and then specify the parent post ID for post_parent.

[marking as resolved]

Thanks for reporting this issue. The Insert Into Post button is now working again. I’m still seeing some funny things in my environment: but I believe these issues are with my OpenPhoto account, not with the plugin or with the integration. The core functionality is working again.

I found the bug, and I have addressed it version 0.2.3. (I also added a WYSIWYG editor for the content editor.) Please upgrade and let me know if it fixes it!

Thank *you* for posting the fix to your problem. I’ll take a look at the plugin and update it so that it works even with a modified image path.

It’s working just fine for me on WordPress 3.4.2. I would suspect a plugin conflict. What other plugins are you running?

What version of the plugin are you running? The last version the original developer(s) released was 1.2.4, but that one will probably never work again. Have you downloaded my code from Github? I released 1.2.7 a couple of weeks ago, which you can download here:

* https://github.com/randyhoyt/wp-category-meta/tags

Actually, on closer inspection, this does not exactly work. This makes WP Syntax ignore the code block altogether. The HTML displays correctly (the code is not longer double escaped), but it does not have any of the syntax highlighting.

I’ll try to work on a patch to the plugin that will make it honor the data-escaped=”true” attribute and post it here.

I found a workaround for this. If you are switching back to the visual editor after editing the code, then instead of this …

escaped="true"

… you can use this …

data-escaped="true"

The WordPress visual editor won’t remove that because it is a valid attribute in HTML5. (You can create your own attributes that begin with data-. WP Syntax finds the escaped="true" part in there and treats it as escaped code.

[removed by original poster]

Good catch! I’m working on an automated deploy script to push code from Github to Subversion over here, and I outsmarted myself. :~) The version number says 0.2 now. Thanks for your help!

(If you upgraded to version %VERSION_NUMBER%, you may have to upgrade manually to 0.2. I’m not exactly sure how WordPress will handle versions that aren’t numbers.)

This has been resolved in version 0.2.

@brian Cruikshank, I have released 0.2 to address the ‘show_in_menu’ issue. Good find!

I just discovered the escaped=”true” attribute, which works nicely. The problem is that the visual editor removes that attribute. I’ll mark this one as resolved and then open a different support ticket for that.