Skip Navigation

[Gelöst] „Form Type or Post Type is not set“ error when using the Autogenerate button in CRED

Dieser Thread wurde gelöst. Hier ist eine Beschreibung des Problems und der Lösung.

Problem:

The issue here is that the user was getting the error "Form Type or Post Type is not set"

Solution:

This issue was resolved in our Latest Toolset Forms version.

This support ticket is created vor 6 Jahren, 6 Monaten. 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.

Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.

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

Supporter timezone: America/Jamaica (GMT-05:00)

Dieses Thema enthält 14 Antworten, hat 2 Stimmen.

Zuletzt aktualisiert von aaronM-9 vor 6 Jahren, 5 Monaten.

Assistiert von: Shane.

Author
Artikel
#870145

PS - I also noticed that I get an error message when editing forms now, which didn't start until I upgraded to the latest beta release. For example, when I try to click on "Auto Generate Form" it says "Form Type or Post Type is not set."

- Aaron

#870282

Shane
Supporter

Sprachen: Englisch (English )

Zeitzone: America/Jamaica (GMT-05:00)

Hi Aron,

Thank you for contacting our support forum.

Could you provide me with admin access to the site so that I can have a look at this for you ?

Also could you let me know the form that is having this issue.

Thanks,
Shane

#872817

Shane
Supporter

Sprachen: Englisch (English )

Zeitzone: America/Jamaica (GMT-05:00)

Hi Aaron,

Based on what is happening on the form, i believe this one might be a plugin conflict.

Would you mind temporarily disabling all the non-toolset plugins and trying again

Thanks,
Shane

#873078

The only non-Toolset plugin that was still activated was Error Log Monitor. I've deactivated it so now only Toolset plugins are enabled and the problem is still occurring.

#876853

Shane
Supporter

Sprachen: Englisch (English )

Zeitzone: America/Jamaica (GMT-05:00)

Hi Aaron,

Would you mind if I took a duplicator package from your website for further testing ?

Thanks,
Shane

#876855

No that's perfectly fine. Do you need me to do anything for you or are you able to do it with your admin access?

- Aaron

#883261

Shane
Supporter

Sprachen: Englisch (English )

Zeitzone: America/Jamaica (GMT-05:00)

Hi Aaron,

It seems the issue is only coming from your ad and ad responses CPT.

Could you try deleting these CPT and remaking them?

Thanks,
Shane

#883522

If I delete and recreate the CPT's, will it make me choose new slugs for the CPT's? This would just mean I have to go through and update any references to it in the site.

Do I also need to delete and recreate the custom field groups or will these "re-associate" with the CPT once I recreate the CPT?

Thanks.

- Aaron

PS: I tried deactivating the CPT and seeing if any of my forms started working, but they are still showing the same error. Will wait to try a full delete and rebuild until you answer those couple of questions.

#884954

Shane
Supporter

Sprachen: Englisch (English )

Zeitzone: America/Jamaica (GMT-05:00)

Hi Aaron,

I've tested this and you can use the same CPT slug for these CPT.

Once the CPT is deleted in Types you can then just remake it. Thats all.

Thanks,
Shane

#886281

I deleted and recreated both the ad and ad response CPT's and the problem is still occurring. Are you sure this doesn't have anything to do with the upgrade to the latest beta version? This is what immediately happened right before I started experiencing problems.

- Aaron

#890744

Shane
Supporter

Sprachen: Englisch (English )

Zeitzone: America/Jamaica (GMT-05:00)

Hi Aaron,

I'm going to escalate this for further debugging by our team.

Thanks,
Shane

#890745

Shane
Supporter

Sprachen: Englisch (English )

Zeitzone: America/Jamaica (GMT-05:00)

Escalated

#890976

Thanks - I have a hunch it's related to another ticket I have open (this ticket was split off of the original one):

https://toolset.com/forums/topic/fatal-error-displaying-post-after-upgrade-to-layouts-2-3-rc2/

Both issues seem to be related to relationships, and they started happening at the same time.

I have asked on the other thread, but have not received a response, regarding whether or not I'm supposed to change the cred_field "_wpcf_belongs..." field inside all the CRED forms. If I can get an answer to this, I would like to try migrating my site to the new relationships structure, but the wizard has told me my forms would have compatibility issues related to the _wpcf_belogs fields. I'd like to see if migrating relationships fixes the problem but am afraid to break anything further.

Thanks again for the help.

- Aaron

#894571

Shane
Supporter

Sprachen: Englisch (English )

Zeitzone: America/Jamaica (GMT-05:00)

Hi Aaron,

Thank you for the patience.

I've gotten news from our team that this was fixed in our latest update.

Could you update to Toolset Forms RC3 and let me know if it helps.

Thanks,
Shane

#894820

I can confirm the problem has been resolved with the release of Forms RC3. Thanks for the help.

- Aaron