[todd-crowder]

1 year, 8 months ago #52787

I don’t have a Save button on the Data tab. I’ve tried deactivating and deleting plugin and reinstalling. Working with Elastic Search self hosted. Was working. Imported a lot of products with attributes and custom fields and now can’t setup facets because can’t save on Data page.

Please let me know how to fix/avoid this error. No idea what’s triggering this error.
thanks,
todd

I’m getting this php error on the data page:

[03-Jan-2025 06:33:32] WARNING: [pool www] child 2169 said into stderr: “NOTICE: PHP message: PHP Fatal error: Uncaught TypeError: wpsolr\core\classes\utilities\WPSOLR_Escape::echo_esc_html(): Argument #1 ($html) must be of type string, null given, called in /var/www/html/web/app/plugins/wpsolr-enterprise/wpsolr/core/classes/extensions/premium/includes/indexing-custom-fields.inc.php on line 81 and defined in /var/www/html/web/app/plugins/wpsolr-enterprise/wpsolr/core/classes/utilities/class-wpsolr-escape.php:130”
[03-Jan-2025 06:33:32] WARNING: [pool www] child 2169 said into stderr: “Stack trace:”
[03-Jan-2025 06:33:32] WARNING: [pool www] child 2169 said into stderr: “#0 /var/www/html/web/app/plugins/wpsolr-enterprise/wpsolr/core/classes/extensions/premium/includes/indexing-custom-fields.inc.php(81): wpsolr\core\classes\utilities\WPSOLR_Escape::echo_esc_html(NULL)”
[03-Jan-2025 06:33:32] WARNING: [pool www] child 2169 said into stderr: “#1 /var/www/html/web/app/plugins/wpsolr-enterprise/wpsolr/core/dashboard/dashboard_settings.inc.php(1335): require(‘/var/www/html/w…’)”
[03-Jan-2025 06:33:32] WARNING: [pool www] child 2169 said into stderr: “#2 /var/www/html/web/app/plugins/wpsolr-enterprise/wpsolr/core/dashboard/dashboard.php(564): include(‘/var/www/html/w…’)”
[03-Jan-2025 06:33:32] WARNING: [pool www] child 2169 said into stderr: “#3 /var/www/html/web/wp/wp-includes/class-wp-hook.php(324): fun_set_solr_options(”)”
[03-Jan-2025 06:33:32] WARNING: [pool www] child 2169 said into stderr: “#4 /var/www/html…”
2025/01/03 06:33:32 [error] 2155#2155: *386 FastCGI sent in stderr: “s different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=’selected’ => selected='selected'; PHP message: (WPSOLR) Attribute is different from escaped value: selected=
2025/01/03 06:33:32 [warn] 2155#2155: *386 an upstream response is buffered to a temporary file /var/cache/nginx/fastcgi_temp/3/00/0000000003 while reading upstream, client: 172.19.0.9, server: , request: “GET /wp/wp-admin/admin.php?page=solr_settings&tab=solr_option&subtab=index_opt HTTP/1.1”, upstream: “fastcgi://unix:/run/php-fpm.sock:”, host: “dev.cs.local”, referrer: “https://dev.cs.local/wp/wp-admin/admin.php?page=solr_settings&tab=solr_option&subtab=result_opt”

[wpsolr]

1 year, 8 months ago #52792

It looks like some of your imported post types’ custom fields have undefined meta_key values.

Can you check in table postmeta?

SELECT distinct POSTS.post_type, POSTMETAS.meta_key
FROM 	posts as POSTS INNER JOIN postmeta  AS POSTMETAS
ON      POSTS.ID = POSTMETAS.post_id

[todd-crowder]

1 year, 8 months ago #52797

257 records, all post types have multiple meta keys and none are blank.

[wpsolr]

1 year, 8 months ago #52798

Nothing strange on the meta keys, like blanks or special characters?

[todd-crowder]

1 year, 8 months ago #52799

No, alphanumerics and _ and – only. we do have about 150 meta keys on product_variation but they all look good. I can put a breakpoint and look at the code, I just thought it was a configuration issue but doesn’t sound like it is.