[Resolved] Save post-id in metafield

[Author]

Posts

[bouchairY]

Hello
I have 2 cpt types : Offers and Formalities
A formality is displayed in offer if they have share the same destination (taxonomy)

[wpv-view name="liste-des-formalites-parametree" wpvportfoliocategory="[toolset_top_level_term tax='portfolio_category' id='[wpv-post-id]']"]

I need to save the formality "id" in the Offer metafield "formality_id"

Thank you for your help

[Shane Supporter Languages: English (English ) Timezone: America/Jamaica (GMT-05:00)]

Hello,

Thank you for contacting our support forum.

Actually I dont think that you need to save the IDs at all.

What you can do is to create a formality view and then add a query filter for your Destination taxonomy and then set it to filter by the taxonomy of the current page where the view is inserted. This will allow the view to be filtered by the same destination taxonomy as the offer.

Please let me know if this helps.
Thanks,
Shane

[bouchairY]

Hello
I agree with you, the formality is displayed in the offer page detail as I already mentionned in my question
The Formality id is need to be used away
Thank you

[Shane Supporter Languages: English (English ) Timezone: America/Jamaica (GMT-05:00)]

So to understand this better you want a list of all the formality ID's that are attached to the same taxonomy to be stored in the formality_id custom field.

If so then this is going to require some custom coding to achieve.

[bouchairY]

There is only one formality displayed in a given offer

When I add : [wpv-post-id] in the formality view
You can see the formality_id = 39073 displayed in the detail page offer

formality fields are not stored in offer cpt, they are only related by destination field

I create a metafield in cpt offer and want to store in it the formality_id

I want to use : update_post_meta( $post_id, $meta_key, $meta_value, $prev_value );

Can you help ?

Thank you

[bouchairY]

Hello
Any informations please ?
Thank you

[Shane Supporter Languages: English (English ) Timezone: America/Jamaica (GMT-05:00)]

Hello,

I have an idea but I would need admin access in order to test the solution.

Would you mind providing me with access so that I can try this.

Thanks,
Shane

[bouchairY]

Hello
You can find access in this ticket :
https://toolset.com/fr/forums/topic/display-only-some-selected-content-templates/

Thank you in advance

[Shane Supporter Languages: English (English ) Timezone: America/Jamaica (GMT-05:00)]

Hello,

So I took another look at it.

It seems that you dont have the CRED plugin installed.

However the idea that I have is to use a CRED form to update the Offers post with the ID of the Formality.

This would mean that any user would be able to update the formality ID and not just you.

Maybe explain to me whats the usage of the formality id and I could possible suggest another method .

Thanks,
Shane

[bouchairY]

It's not really solved, I'm using a work-around

[Mohammed]

Hi Bouchair,

I see that we can fix this issue but we only need more clear details to start working on it.

I will be happy If you agreed to re-open this ticket.

Just mentioned my name in a reply @mohammed to start working on this again.

Thanks.

[bouchairY]

Hello Mohammed
I'm happy that you can work again on this problem again
Please see attached image
Actually I have a form on the front where the admin can set the formality manullay and save it

Thank you

[Mohammed]

Hi Bouchair,

FYI, Me and Shane will work with you on this issue.

Please provide Shane the information he will ask you about and be sure that we will do our best.

Thanks.

[bouchairY]

Hello
Ok no problem
Please send me a private post and i will provide access infomations
Thank you

[Shane Supporter Languages: English (English ) Timezone: America/Jamaica (GMT-05:00)]

Hello,

I must apologize for the delay in response.

Could you explain to me the purpose of having the ID in the other post ?

Understanding the context should allow me to provide a solution that could be done through the backend automatically.

Please let me know.
Thanks,
Shane