[Resolved] Related to #2708577 – Support with field not mapped anymore

[Author]

Posts

[pierreB-9]

I am trying to:
I have been working with a technical support but he decide to close the ticket without resolution. #2708577
This is unacceptable 9the ticket is also frozen... I cannot edit anything anymore) !!! I have a PRODUCTION ISSUE !!! I have disable all plugins using 'Health Check & Troubleshooting' and the problem is still there. IF you open any of the Custom post type you see the CPT post content data from previous posts created and the other fields are still available 9see screenshots attached).

Now please collect the inforation from the previous ticket as the situation is still the same!!!

Link to a page where the issue can be seen:

I expected to see:

Instead, I got:

[pierreB-9]

Additionaly I have create a new paper-opinions post and the same issue is happening
See attachment

[Minesh]

Hello. Thank you for contacting the Toolset support.

if you can share the ticket URL where I can see the #2708577 that would be great.

Can you please share more details and share exact steps that I should follow to see the issue and what is your expected results.

Please share all problem URL and step by step information that should help me to see the issue.

[pierreB-9]

Hi Christopher/Minesh
I am not able to view your video... I am in currently at a location where my download is very slow.
I had to create a loom account to download it but still not able to view the video.

What I have describe is clear from my side and I am able to reproduce the issue each time
1) the content field seems to be NOT MAPPED anymore...
2) It is still possible to see previous data saved on the content field but it seems that if anyone try to edit it it vanishes...
This has worked for 3 years and not it is broken even when I disable ALL plugins BUT the Toolset plugins as specified in the screens I have send.

Could you please seriously debug the issue? Also make sure I am still able to provide answers
Thank you

[pierreB-9]

Hi Christopher,
I was finally able to see your video!! Thank you for that.
No the issue is a little bigger than what you experienced... nevertheless I will try to record a video of all the issue I am facing.
I am glad at least that you are not saying it is a plugin conflict and then leaving for me to guess what is hapening with your plugin
anyway... to be follow with my recording

[pierreB-9]

Hi Christopher,

I just recorded a Loom showing some strange behavior on the live and staging environments regarding the content field being read-only in our toolset form.

It's a bit puzzling, and I could really use your insight on this issue. Check it out when you have a moment!
Hopefully you can see the video prperly
\
hidden link

[pierreB-9]

Hi Minesh/Christopher
Any update on this crucial production issue?
Thank you for updating me with an update

[Christopher Amirian]

Hi there,

Thank yo for the video and your patience. I already answered back int he other ticket. But I will also add this:

Thank you very much for the information. It seems that the problem is a conflict with the "Kadence Pro - Premium addon for the Kadence Theme" plugin.

I explained the details in the video below:

hidden link

To be able to report the compatibility issues we need to replicate the issue on a clean installation.
I'd appreciate it if you follow the steps below:

- Use the link below to login to a clean installation of WordPress and Toolset:

hidden link">Click here

- Install the "Kadence Pro - Premium addon for the Kadence Theme" plugin.
- Add a sample form with Wysiwig.
- Replicate the issue so I can report this to the compatibility team.

This will help us to report the probable issue to the compatibility team and solve the possible problem faster.

Thanks.

I suggest that we follow the issue in the other ticket and close this one.

Thanks.

[pierreB-9]

Dear support,

With the help of KadenceWP support, I was able to isolate the issue conflict with "CookieYes | GDPR Cookie Consent". This plugins doesn't need to be active since I already unabling it via Google Tag Manager. I believe that was causing the issue and not the Kadence Pro Theme plugins.
Thank you very much for your active support... That was a difficult one, especially since it has been working fine for over 3 years and broke suddenly out of no specific changes anywhere on that site