When editing a product field group, all fields are empty

Hi @wildvanvorm

This usually indicates a javascript error. You can find out by opening the developer console in your browser and checking for errors. Here is a handy article: https://www.ads-software.com/support/article/using-your-browser-to-diagnose-javascript-errors/ (see step 3 “diagnosis” on how to open the developer console).

1) open the developer console
2) navigate to the product fields group with the issue
3) check if an error appears in the console, and let me know.

• This reply was modified 2 years, 7 months ago by Maarten.
• This reply was modified 2 years, 7 months ago by Maarten.

Hi @maartenbelmans

Thanks for your reply. No errors are showing up in the console. I’ll try a plugin conflict test and see if that resolves anything. I’ll keep you posted.

Best regards,
Wim

Hi @maartenbelmans

I’m unable to find the cause. In the console, I don’t see any errors and the problem persists after turning off every plug-in except for WooCommerce and Advanced Product Fields. Any ideas on what can be done next?

Best regards,
Wim

Hi Wim,

Can you try a simple test:

1) make a new field group. As title, add “test”.
2) click “add your 1st field”.
3) don’t make any changes to the field, and click “publish” to save the field group.

Now refresh the page and see if you can edit that field group.

Hi Maarten

This is also not working. Actually, from the moment I hit Publish, the fields added in the Fields section cannot be seen anymore. They appear in the front end, but I cannot edit them in the back-end.

They appear on a product but not in the WP admin edit screen?

Yes, that’s right. The fields appear in the front-end, but they are gone in the back-end from the moment I press Publish. When I edit an existing Product field group, for example to add a Rule, I get the error ‘Please add some fields first’.

Can you enable error reporting to check for PHP errors when saving?

[08-Feb-2021 05:09:00 UTC] PHP Warning: PHP Startup: Unable to load dynamic library ‘newrelic.so’ (tried: /usr/lib/php/20200930/newrelic.so (/usr/lib/php/20200930/newrelic.so: cannot open shared object file: No such file or directory), /usr/lib/php/20200930/newrelic.so.so (/usr/lib/php/20200930/newrelic.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0

Hi @maartenbelmans

The helpdesk of my hosting company is taking a look at this issue as well. newrelic.so should not have anything to do with it, so they say, and I have no doubts the issue is specific to my site. I myself am unable to find any hint that points to the cause.

Best regards,
Wim

Are you comfortable going into your database?

I can create a staging for this purpose. What should I do in the database?

I want to check the data that is in the database. If you’ve created fields via the menu WooCommerce > product fields, then they are stored in the “posts” table.

I’ve found it in the database. The post_content shows this:
a:5:{s:2:"id";i:22768;s:4:"type";s:12:"wapf_product";s:6:"layout";a:3:{s:15:"labels_position";s:5:"above";s:21:"instructions_position";s:5:"field";s:13:"mark_required";b:1;}s:6:"fields";a:2:{i:0;a:10:{s:2:"id";s:13:"624c1ce297738";s:5:"label";s:16:"Naam van je kind";s:11:"description";N;s:4:"type";s:4:"text";s:8:"required";b:1;s:5:"class";N;s:5:"width";N;s:7:"options";a:0:{}s:12:"conditionals";a:0:{}s:7:"pricing";a:3:{s:4:"type";s:5:"fixed";s:6:"amount";d:0;s:7:"enabled";b:0;}}i:1;a:10:{s:2:"id";s:13:"624c1cf74ea49";s:5:"label";s:25:"Geboortedatum van je kind";s:11:"description";N;s:4:"type";s:4:"text";s:8:"required";b:1;s:5:"class";N;s:5:"width";N;s:7:"options";a:0:{}s:12:"conditionals";a:0:{}s:7:"pricing";a:3:{s:4:"type";s:5:"fixed";s:6:"amount";d:0;s:7:"enabled";b:0;}}}s:11:"rule_groups";a:1:{i:0;a:1:{s:5:"rules";a:1:{i:0;a:3:{s:5:"value";a:1:{i:0;a:2:{s:2:"id";s:5:"21906";s:4:"text";s:45:"Van Ster naar Ster, vzw Kong - 27/08 - 14.00u";}}s:9:"condition";s:8:"!product";s:7:"subject";s:7:"product";}}}}}

Other than that, there’s a post title, a post name and a url, but all other database fields are blank.

Hi @maartenbelmans

Any news on this?