Skip Navigation

[Resolved] Post form not functioning causing a critical error

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
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10: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/Kolkata (GMT+05:30)

This topic contains 4 replies, has 3 voices.

Last updated by Mateus Getulio 1 month, 3 weeks ago.

Assisted by: Minesh.

Author
Posts
#2779625
Screenshot 2024-10-28 at 7.21.51 pm.png

Tell us what you are trying to do? One of my Post forms - to enable logged in users to edit existing posts has stopped functioning properly. Rather than editing the post it causes a critical error.

Is there any documentation that you are following?

Is there a similar example that we can see?

What is the link to your site? techboard.com.au

#2779642

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

That is strange.

Just to ensure that is no conflict with the existing plugins/theme you use:

Could you please try to resolve your issue by deactivating all third-party plugins as well as the default theme to check for any possible conflicts with any of the plugins or themes?
- Do you see any difference? if no:

Can you please share admin access details and problem URL where you added the edit form as well as frontend user access details if required to edit the form on frontend.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#2780129

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

There is a field you added to your form with label "Investors":

<div class="cred-field cred-field-investors">
			<label class="cred-label">
Investors
</label>
			[cred_field field="investors" placeholder="Insert Names of individuals or companies that have invested in the Company" post="company-profile" value="" urlparam=""]
		</div>

When I checked that field on custom field group:
- hidden link

The Investors field is setup with conditional display based on the field "investment-status":

($(investment-status) > 0)

As you can see with the following screenshot:
- hidden link

The issue is that field is not available with the form. Is it ok to remove that condition with your edit form?

#2780382

I tried deleting that from the staging site and it seems to have resolved the problem.

but when I tried the same on the production site it made no difference and I still get the critical error after submitting the edit form.

hmmm.

any more ideas?

#2780529

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello there,

Minesh is not available today so I'll be responding on his behalf.

Are the staging and production sites totally synced, or there are changes there were made to the production site for example that are missing in the staging?

Instead of having us debugging it in the live site, would it be possible for you to try to recreate the staging site using the production site as the model, if the error starts happening in the staging site as well we could do the debugging in there without affecting the live site.

I'm enabling private fields for your next reply in case you create a new up-to-date staging and need to share new access details or in case you decide to share the access to the live site.

Thank you, please let us know.
Mateus

#2781414

Thanks Minesh and Mateus

I copied the changes I had made to staging to the production site... as I thought I had done before. This time it worked and the problem I had has disappeared. Thanks for your help

Peter