[Résolu] Edit standard content field (wysiwyg) and featured image in child meta box?

[Auteur]

Publications

[NattapatP8602]

Just to clarify
I try to use the child/parent metabox to add/edit custom child/parent original fields like "content editor(wysiwyg)" and "Featured Image"
However the only standard field that comes up is "Post Title"
And then other custom fields come after.

The question is
Is it possible to add/edit those standard fields from child/parent metabox?

Or

Should I just disable original "Content Editor" and "Featured image" And Create the Custom fields to replace it.
Both for the add/edit and it might easy for CRED too.

[Nigel]

Hi there

You are correct, when adding a related post on the edit screen of another post, the only fields you can add/display are custom fields in addition to the post_title field. Other standard fields are not available.

The only alternative is, as you recognise yourself, to create WYSIWYG and image custom fields to use in their place.

We could propose this as a feature request (there is no technical reason why it could not be done), but it would only be implemented if we saw a lot of demand for it, so let me know if you would like me to proceed.

[NattapatP8602]

Yes, please proceed.
I will make features request
1. Edit standard content field (wysiwyg) and featured image in child meta box
2. Gallery fields that you can upload multiple image in one go.(not repeated field like what we have)
- Clients ask why I have to upload image multiple time, we're done man.
3. Option to make a number field to display with commas (1,000,000)

And I think it kind of hard for people to realize for themself since they will be okay with the alternative ways because most of us don't good at PHP and stuff.

I would love it ,if I can just use toolset and get things done without this little complication.
We are running on wordpress and most of us will put content in "Content editor" and the cover photo in "feature image"
However I can see that if you use toolset to create post template the content editor will not be available, fair enough .

And thank you as always Nigel
I appreciated your support

[Nigel]

Sorry for not replying sooner, but we were in the middle of changing the way we handle feature requests.

I have not updated anything internally with this because the Toolset product manager now wants to hear such requests directly from users where they can follow-up for more information if required.

Apologies for the inconvenience, but could you please add your requests at this page: https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/