owenwalz
Forum Replies Created
-
Thanks so much. That worked perfectly.
Forum: Plugins
In reply to: [Posts 2 Posts] [Plugin: Posts 2 Posts] Adding ID / Names for old connectionsThis worked very well, thanks. It did require referencing the table to get the right hashes, but it wasn’t too arduous.
Appreciate it.
Forum: Plugins
In reply to: [Posts 2 Posts] [Plugin: Posts 2 Posts] Adding ID / Names for old connectionsAwesome. I will try that. Thanks.
Forum: Plugins
In reply to: [Posts 2 Posts] [Plugin: Posts 2 Posts] Adding ID / Names for old connectionsThanks again Scribu.
I see a variety of solutions in the thread you’ve linked to. I’m wondering which is most appropriate for my situation.
I’m currently using P2P version 1.1.3. Currently the p2p_type column in my database is all filled in, mostly with auto-generated hashes (apart from a few recent named connections). I would like to add names in the registration, and have them attach to the proper existing connections somehow.
I have yet to upgrade, assuming there will be issues.
Forum: Plugins
In reply to: [Posts 2 Posts] [Plugin: Posts 2 Posts] Adding ID / Names for old connectionsAlso, is ‘name’ and ‘ID’ interchangeable in P2P registrations?
Forgot to tab that out (it’s part of the fields argument array).
Thanks. I agree a labels parameter would probably be the best way.
Forum: Plugins
In reply to: [Posts 2 Posts] [Plugin: Posts 2 Posts] Multiple connections getting crossedThanks. That’s been working well in my templates. To be more specific, I’m hoping to keep ‘spotlight’ connections showing up in the UI for ‘credit’ connections for types ‘person’.
Forum: Plugins
In reply to: [Posts 2 Posts] [Plugin: Posts 2 Posts] Multiple connections getting crossedThis is the new type that I just added:
p2p_register_connection_type( array( 'from' => 'event', 'id' => 'spotlight', 'to' => array('event', 'person', 'news'), 'title' => 'Spotlight', 'reciprocal' => false, 'data' => array( 'type' => 'spotlight'), 'show_ui' => 'from', 'sortable' => 'any', 'fields' => array( 'alt_title' => 'Alternate Title (Optional)' ) ) );
This was already registered and contains a lot of connections:
p2p_register_connection_type( array( 'from' => 'event', 'to' => 'person', 'reciprocal' => true, 'sortable' => 'any', 'title' => array( 'from' => 'Cast & Crew', 'to' => 'Credits' ), 'fields' => array( 'credit' => 'Credit', 'credit_cat' => array( 'title' => 'Credit Category', 'values' => array( 'Playwright', 'Director', 'Assistant Director', 'Cast', 'Production' ) ) ) ) );
I would add
data' => array( 'type' => 'credit')
to this second type, but I lose all my old connections when I do so.Thanks,
Ooop. I think I just figured this out.
Thanks for all your work on this issue. I’ll see if I can test some of it out.
Could this be accomplished by adding a filter that copies meta into the title during the publish hook? I’m a bit of a noob coding-wise so forgive me.
I’m running into the same issue. There are some custom post types in which a ‘title’ field doesn’t make sense, but the system still requires it. Having the title pulled from another meta field would be ideal.
Brilliant! Fixed. Thank you.
Thanks for the speedy reply. I suspect it is the same problem. I just tested a non-reciprocal relationship and it worked fine.
Should I then install the new alpha? Do I need to generate a javascript file to fix tabs as described in that thread?
Thanks,
Excellent. Thanks.