Skip Navigation

[Resolved] Uupdate custom field on pr_save_child_post

This support ticket is created 3 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 19 replies, has 3 voices.

Last updated by Waqar 3 years, 10 months ago.

Assisted by: Waqar.

Author
Posts
#1956003

Thanks for the update.

Your customization requirements are unique since they revolve around the WordPress admin area screens and not the front-end of the website. Most users would want the design and layout flexibility only on the front-end of the website, for which Toolset plugins provide a fair amount of controls, hooks, and filters.

I'll be happy to pass on your suggestion to introduce more control and flexibility for how the related posts section is shown in the admin area. However, until that happens the changes that you're looking for would require far more complex customizations, than what can be covered over the support forum. Most likely, they'll also require making changes in the plugins core files, which is never recommended or encouraged.

I hope you'll understand.

#1956353

Hello Waqar,

Thank you for your time and reply.
i can understand what you just wrote. On the previous version of toolset (2.3.5) used on our old site i was able to easily manage columns on the Parent Custom fields.
is there any risk to downgrade toolset current version used to the 2.3.5 where i'm more comfortable with( No Quick Edit/ No Popup...)

Thank you for your understanding and support

#1957761

Thank you for understanding.

There are serious risks involved in using an older plugin version and I'll recommend strongly against that idea. Newer versions not only include new features and improvements but also cover security and bug fixes and help maintain compatibility with WordPress and other plugins and themes. For this reason, this approach won't be safe or feasible in the longer run.

To provide a more customizable editing experience for your users, you should consider creating front-end forms for them that will replace the admin area edit screens. This surely means extra work, but, you'll have more future proof control over the design/layout of the input fields.

#1958661

thank you Waqar for your reply and your confirmation.

#1962281

You're very welcome and please feel free to start a new ticket for each new question or concern.

I'm going to mark this ticket as resolved.