Passer la navigation

[Résolu] when I try to modify the content template, a fatal error appears

This support ticket is created Il y a 3 years, 3 months. 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
- 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 -

Fuseau horaire du supporter : Asia/Kolkata (GMT+05:30)

Ce sujet contient 4 réponses, a 2 voix.

Dernière mise à jour par chelhwanS Il y a 3 years, 3 months.

Assisté par: Minesh.

Auteur
Publications
#2566117
toolset 20230305-1.png

I am trying to:
I can search the details page of the store.
However, when I try to modify the content template, a fatal error appears and I am unable to modify it.
Please refer to the video below.

Link to a page where the issue can be seen:
lien caché

video
lien caché

staging
lien caché

#2566733

Minesh
Supporter

Les langues: Anglais (English )

Fuseau horaire: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Can you please check now:
- lien caché

I've fixed the issue and the related improvement will be added to our plugin in near future release.

#2567211

Thank you for your effort.
One solved, but the other still gives an error.

content Template -> edit product manage

I would like to know why this phenomenon occurs. Then I will be careful.

lien caché

#2567447

Minesh
Supporter

Les langues: Anglais (English )

Fuseau horaire: Asia/Kolkata (GMT+05:30)

Can you please check now: lien caché

The issue was with both "edit product manage" and "Template for product" content templates. I fixed the issue for both of the content templates.

As shared the issue is known to us and we are going to ship the fix with the hotfix version with next release.

#2568851

My issue is resolved now. Thank you for your effort