[Closed] Follow up https://toolset.com/forums/topic/new-update-has-developed-a-conflict/

[Author]

Posts

[christopherH-3]

I am trying to:
Hi, please review the unresolved problem I raised many months ago here: https://toolset.com/forums/topic/new-update-has-developed-a-conflict/

I have let this sit for some time in the hope that future updates would resolve the issue. They have not, and consquently i am still using Types 1.7.2 which is the most recent version I am aware of that does not create this problem.

However, I now have some futher observations to add from my most recent attempt to update the plugin, as follows:

I have isolated the occurrence of the problem to when the user saves a new child custom post, within the admin page for the parent post type, by using the individual line SAVE button, rather than the header SAVE ALL button. And in fact I now realise that even in 1.7.2 this problem occurs if you used the individual line Save button. The problem is that when i update to the current version (last tried 2 weeks ago) the current version seems to have discontinued the SAVE ALL Button. Can this be reinstated?

Thanks
Chris

[Luo Yang]

Dear Chris,

Are we talking about the conflict between Types parent/child relationships your custom PHP codes?
Could you locate the PHP codes, and describe details to duplicate same problem?
Since it is custom PHP codes problem, it is out the range of our support range, see our support policy:
https://toolset.com/toolset-support-policy/
You can also contact our certified partners for it:
https://toolset.com/consultant/

[christopherH-3]

Hi, I don't really understand what you're asking for above.
I tried to add comments to the previous ticket, so that all the information I have provided on this issue is available in one place, but your system would not permit it. Please do read that thread as well as this one.
What we do know is that the conflict developed after we had invested many hours into building the sort and display code needed to display the custom posts in the tables we needed - then Types updated and now we have the problem. I am very concerned that I can't go on forever using a very old version of Types without compromising the security of our entire site.
I realise this is a complex issue, but to begin with I need an answer to a fairly simple question - why is the 'save all' button no longer appearing, and when will it be reinstated in a future update?

Thanks
Chris

[Luo Yang]

The 'save all' button has been removed, since it will trigger a lots of compatibility problem, and I don't think it will be able to reinstated in the future update

[christopherH-3]

Ok, well then i am back to my original problem. We invested hundreds of dollars having php code written to sort and display data entered via the Types Plugin, and now updates to Types render that code unusable. If the save all button is not coming back, then the issue i need investigated is why the individual 'save' functions are not preserving the correct sorting of the data for use in our display/

[Luo Yang]

For the question:
why the individual 'save' functions are not preserving the correct sorting of the data

Could you describe detail steps to duplicate same problem?
Is there any custom PHP codes in this case?
I need test and debug it in my localhost