Skip Navigation

[Resolved] CRED Edit Form fields are empty when some users edit their posts

This support ticket is created 4 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 6 replies, has 2 voices.

Last updated by mikaelD 4 years, 11 months ago.

Assisted by: Christian Cox.

Author
Posts
#1401771

One of my users is trying to edit a post of theirs, and the fields he has already filled out when he published the post are coming in empty. He recorded a video of the behaviour here:

hidden link

I tried to replicate the issue myself but can't.

We cleared the site cache, he cleared his cache and tried a different machine, incognito window and another browser. Still the same issue.

Have you seen this before?

Regards,

Cameron.

#1402299

Hi, I'm not aware of any open issues like this but it's hard for me to diagnose without being able to see this in the browser.
- Is the problem reproducible with this User's login information? If so, can you provide that information so I can test?
- Is there a development environment set up where we can disable other plugins and test with a default theme?
- Is there any custom JavaScript code applied to this Form, page or template? If so, can you share it with me and give me a general idea of what it's supposed to accomplish?
- How exactly is the Form added to the page - is a shortcode inserted in a Content Template, or a widget in an Elementor template, etc?
- Is the page source code complete for this User? Sometimes if there is a server error, the HTML is incomplete and the page breaks unexpectedly. You would be able to tell by checking the Page Source (not the DOM inspector) to see if there is a closing body tag and closing HTML tag at the end of the document. If not, something is causing the server to stop rendering the HTML here.
- What is the full URL when the User tries to edit his own Profile post? It's cut off in the screen capture so I can't examine all the URL parameters. Those could help explain this behavior.

I'll look forward to getting your feedback so we can sort it out.

#1403045

Update:

I can replicate the issue logging in with his account. You can test it on staging. He has no errors in the Developer console

Creds:
josen.ruiseco
$peed_Week100

Full URL where user is seeing issue:

hidden link

#1404559

Okay thanks for the additional information. I logged in and could see that this Provider Profile post was in Draft status, not Published status. On a hunch, I published the post. Now I can see all the information visible in the Form here:
hidden link

Feel free to check that now, and set the corresponding post to Draft status again to see the problem return.

So it appears to have something to do with the post status. Do you plan to allow your Users to be able to edit these Draft status posts from the front-end like this, or should these Draft profiles be hidden/uneditable somehow?

#1404673

Hi Christian,

Yes, they need to be able to edit them in Draft mode because it is a public facing professional bio. They need to be able to review their changes before publishing. This issue does not occur for other users.

I am wondering if his profile is somehow corrupt because I can not replicate the issue using other user accounts.

Try this account:

u - camerontest
p - tester

You will see that it works fine in Draft mode

#1406143

Hi Christian,

I was able to resolve the issue by deleting the post and recreating it. Maybe it was something that was corrupt in the database.

Feel free to close the ticket.

Regards,

Cameron.

#1406145

My issue is resolved now. Thank you!