The custom fields stopped showing up on the front end of the site. Not sure why
Hi, can you provide a specific location on the site where I can see the problem?
here is a example page where the fields are not showing. All the property pages look like this, where there is the title and none of the info from the fields.
hidden link
thank you so much,
Mike
Okay I don't see anything obviously wrong, so please try the following troubleshooting steps:
- Update WP Bakery Visual Composer to the latest version, and try again.
- Temporarily switch to a default theme like Twenty Seventeen, deactivate all plugins except Types and Views, and try again.
- If the problem was resolved, reactivate your theme and plugins one by one until the conflict is revealed.
- If the problem was not resolved, create a new Content Template and add some testing text. Temporarily assign this Content Template to one property and see if the testing text appears on the front-end of the site.
Please let me know the results of these tests and we can go from there.
I changed themes, no luck. Deactivated all plug ins except Toolset and no luck. Updated Visual Composer and Theme no luck.
Then I noticed that all the content on the whole site disappeared, so there was only the header and footer. As soon as I deactivated just Views plug in all the content came back, but of course none of the custom fields did.
I think this has something to do with Views Plug in, can you check that?
thanks,
Mike
One more thing, when I tried to add a custom field to a new Content Template using Visual Composer, it was putting the filed in like this:
{!{wpv-post-body view_template='test'}!} instead of normal brackets, like this [wpv-post-body view_template='test']
mike
{!{wpv-post-body view_template='test'}!} instead of normal brackets, like this [wpv-post-body view_template='test']
Yes, this is expected when inserting shortcodes in a Visual Composer text block. Nothing to worry about here.
Then I noticed that all the content on the whole site disappeared, so there was only the header and footer.
This was because the "Test" Content Template was applied to the home page. When you activate Views with this Content Template applied to the home page, nothing will appear between the header and footer because it's an empty template except for the shortcode:
[types field='state'][/types]
Nothing shows up because the homepage doesn't have this field. The "state" field is only used on Property posts. I have reset the Home Page to use no Content Template for now, and the Home Page looks good. When I activate Twenty Seventeen, the Property custom fields begin showing up as expected on the Property single page. So it looks like a conflict with the Florida theme. I don't have access to that theme..can I create a clone of your site using the Duplicator plugin? I can install it locally and run some additional tests.
Okay after copying the theme into a fresh site, I was able to replicate the same issue on my local environment. This indicates a conflict between Florida theme and Views. I am escalating this to my 2nd tier support team now for some additional investigation. You mentioned that the fields stopped working - so they must have worked at some point. My guess is that the fields stopped working when you activated the Florida theme.
The fields used to work with this theme, as the theme has never changed. I think the client updated the theme at some point and then it stopped working. Just my guess.
But the fields worked for 3 years with Florida theme until now.
thanks for your help:) and I look forward to what tier 2 says
Okay following the steps listed here, I can see that the theme no longer provides a valid, dedicated function to render the post content: https://toolset.com/documentation/user-guides/editing-view-templates/theme-support-for-content-templates/
At this point we need to loop in the Florida Theme Developer and let them know that Toolset Plugins are not compatible with his theme because the theme does not use the native WordPress function the_content() or another dedicated function. The author may refer to our "Beyond Pages" program and contact us if s/he is interested: https://toolset.com/documentation/beyond-pages-program/
We will try our best to contact the author at hidden link and figure out a solution, but ultimately it's up to your theme author to collaborate on a solution here. It will probably be helpful for you to contact the theme authors as well, to let them know what's going on. They will be more likely to respond to a paying customer than to another development shop.
For now, it may be possible to downgrade to an older version of the theme, which you mentioned worked in the past. It may also be possible for a skilled developer to create a child theme, where the template files of this theme are customized to use the_content() or another dedicated function. Then Content Templates would begin working again. Here's the WordPress Child theme documentation: https://codex.wordpress.org/Child_Themes
Here's a link to our contractors portal where you can find skilled developers: https://toolset.com/contractors
hello. so I have switched themes to Divi, and the views plug in removes all content on the site as well. All I did was activate Views in Divi theme, with no other plugins on except Types, and all the content between header and footer goes away.
Any ideas? That's Florida theme and Divi theme this is happening to.
thanks,
mike
All I did was activate Views in Divi theme, with no other plugins on except Types, and all the content between header and footer goes away.
Typically this indicates you need to create Content Templates and WordPress Archives to populate the contents of the pages, but without more information I can't say for sure. Here's a guide for using Divi with Toolset:
https://toolset.com/documentation/recommended-themes/toolset-divi-integration/
If you a have specific issue, please create a new ticket so we can discuss in more detail.
ok. All I know is that I activate Views all content goes away. Even content that isn't part of Types or Views. I will open new ticket as I am confused.
