Error in card view displaying

Hi there,

It appears that you’re using a Custom Template for your View, but there seem to be some errors present.

In such cases, you can open the View and click on the Update button to pinpoint which line is causing the issue. You can then compare it with the Default Template to identify the problem.

If this doesn’t apply to your situation, please navigate to Settings-Debugging and generate a debug dump for the relevant View/Card.

Kindly send it to us at [email protected] so we can assist you further.

Hi, WP Lake

I have send mail to your Email yestarday 01/04/2024 but stil haven’t recieve any answer. Have your recieve it ?

• This reply was modified 7 months, 3 weeks ago by greensnail.

Hi Green snail,

After reviewing your log, we’ve confirmed that the issue stems from your field names, which are composed solely of digits.

Advanced Views generates Twig variable names based on field names, and using only numbers, such as “2”, is not valid in Twig.

If your website is in a development stage without real data, we highly recommend renaming these fields with proper names containing letters within the ACF Groups. Subsequently, you can recreate the associated View.

However, if your website already contains populated data, you can manually update the field IDs by following these steps:

a) Open the View.
b) Ensure you’re on the Fields tab.
c) Go through each field and change its ID in the Field Options tab

Hi, WP Lake

Acctualy I haven’t any fields with name “2”. Something goes wrong in this way. I have rerender View and Card and send you more data by email.

With best regards

Hi Green snail,

We’ve imported your CPT and related Group provided via email, and couldn’t recreate your issue.

The View for them works properly on our side, displaying the chosen fields as expected.

However, it’s possible that there might be a plugin/theme conflict causing the issue.

We recommend disabling extra plugins one by one and creating a new View (even with just one field) to confirm if the issue persists.

This step-by-step approach will help you identify the problematic plugin. Once identified, you can send that plugin to us, and we’ll attempt to improve compatibility if possible.

UPD:

We checked your demo website and noticed that the field IDs within the View were still incorrect.

It appears that the auto-generation of IDs based on labels doesn’t function properly for Russian.

Therefore, for now it’s necessary to define the field IDs in English manually within the View.

We’ll work on improving the compatibility for non-English labels in the automated ID generation process, and will include it in the next release.

Yeah. Thanks a lot.
Now I understand where is problem and what you mean when wrote about ”?Twig variable names”.

With best reagards