Navigation überspringen

[Gelöst] New fields not showing on front-end

This support ticket is created vor 2 years. 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
- 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 13:00 – 18:00 13:00 – 18:00 -

Zeitzone des Unterstützers: America/Sao_Paulo (GMT-03:00)

Dieses Thema enthält 1 reply, hat 2 Stimmen.

Zuletzt aktualisiert von Mateus Getulio vor 2 years.

Assistiert von: Mateus Getulio.

Author
Artikel
#2699014

Tell us what you are trying to do?
Hello, I just made a new post type, HISTORICAL YEAR, which is meat to be used for graphs.

All the data was imported correctly, and you can by going to the individual year page in the backend. However, when trying to display this using a view, only the post name displays, none of the custom fields (even though I can see those fields are indeed populated)

The name of the view is "Year Graph" and you can see that on the homepage, it is not displaying the provided custom fields. The paragraph that is supposed to show "acres burned" just shows up empty.

Thanks!
Max

{edited}

#2699041

Mateus Getulio
Unterstützer

Sprachen: Englisch (English )

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

Hello Max,

Thank you for contacting our support.

I checked it and it looks like the issue was caused due to cache.

I edited the home page and added a cached="off" to the view and I can see the custom fields data now:

{!{wpv-view name='year-graph' cached='off'}!}

Can you please test it again to see if it looks fixed on your end as well?

Thank you, please let us know.
Mateus

#2699715

Hi now. I just want to not the provided response was incorrect. It turned out that the data was being ingested in the wrong format (unix) and the cache was not related to the problem.