Skip Navigation

[Resolved] Custom Fields Not Showing

This support ticket is created 5 years ago. 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
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 9 replies, has 2 voices.

Last updated by Beda 5 years ago.

Assisted by: Beda.

Author
Posts
#1374429

I am trying to:
Add Custom Fields
Link to a page where the issue can be seen:
hidden link
I expected to see:

Instead, I got:

#1374431

I've tried deactivating all plugins and my theme, but nothing works. Custom Fields don't show in the custom post types i assign to them. I when i don't assign them to any post type, they also don't show up.

#1374535

For this we will need log in details, because you mention the backend.
Could you provide so in the next private reply after making a few tests?

1. Test without any other Plugin but Toolset (You have done that)
2. Test with another Theme (To Do)
3. Check if you have any PHP errors in the Logs (You can activate Debug as shown here https://codex.wordpress.org/WP_DEBUG) (To Do)

If then the issue persist, can you send us the login details to preferably a testing site, or, if you have one - a Duplicate of the site?
https://toolset.com/faq/provide-supporters-copy-site/

Then we can look into this and effectively provide solutions.

#1374819

I made a mistake. The login is this:

hidden link

#1374849

There is an error
ERROR: Invalid username.

Can you edit either your own private reply to update it, or use my private reply I activated in the next step?

Thanks!

PS most likely you miss either eval() or mb_string() support on your server.
Please check this:
https://toolset.com/toolset-requirements/

#1374927

I fixed the username issue. You can now log in.

FYI, both eval() or mb_string() are supported on my server, so that's not the issue.

#1375783

Any luck?

#1376105

My apologies, my weekend (https://toolset.com/forums/users/beda-s/) came in-between us and my colleagues had no spare time to check in here.

I was able to login now, and saw you have CF's (Custom Fields) assigned to Products, Shows and "All Post Types".
We should see a Date CF on Shows, several different CF's on All Post Types, and the Product CF's are the standard ones added by WCV (WooCommerce Views).

You have no Show Posts yet, so I created one.
The Fields do not appear, as well in the Shows post Type settings, it appears there are no fields assigned to the Post Type.
I did not create a Product, as you also have no products on this site, and I also cannot see the Fields on posts or pages (the ones for All Types).

I can however not confirm if this issue does nt happen without other plugins or themes as this seems a live site.
I can also not further debug this online, as it will require database access and tools that function only when I have control over the server and direct, local access to it.

I could not spot any obvious errors or misconfigurations.

I saw that you have Duplicator installed and a package from the 1st of November, is I allowed myself to deploy that locally, I do hope this is fine, please let me know if not, I will delete the local anyway after testing.

I will be back here as soon I have some findings.

#1376109

You can do whatever you want with the site. It's brand new. Don't even worry about backing it up.

#1376117

OK, the first error on your duplicate happens on deploying it:

Fatal error: Uncaught Error: Class 'Memcached' not found in .../wp-content/object-cache.php:858

I have disabled the object cache to proceed because even if I enabled MemCache on my server the error does not disappear.
I logged in and all fields appear as they should.

We have had an issue with cache in past that is quite similar, but not the same, and they are solved:
https://toolset.com/forums/topic/memcached-prevents-field-group-title-from-saving/
https://toolset.com/forums/topic/internal-field-group-title-not-saving/
https://toolset.com/errata/views-features-affected-by-servers-who-change-the-wp-object-cache/

I also tested the back then "fixing version" of Types on the Duplicate, with MemCache back active which did of course not solve anything, because of the fatal error that came back up.
I guess that requires some setup with WPMU DEV Dashboard to have that working?

For now your site should run if you remove or rename the object-cache.php file in the wp-content folder.
Please let me know how I can make the object-cache.php work locally without any fatal error, it seems clearly there is another codebase missing, as fatal errors of that kind indicate there is a missing piece somewhere.

Note, that the Fatal error occurs on the Duplicate without any other plugin but that file in the content folder.
It should hence not be related to Toolset, but it could be that when "working" (speak - no errors thrown) something with the cache makes Toolset's Fields break.
I can analyze that as soon I know how to activate the object-cache.php File without error.

Can you elaborate on the steps you took to use that file?
(It does not seem the default file of the memcache plugin, hence I could not use that either)