Skip Navigation

[Resuelto] Custom Select Field Filters in WordPress archive, created with Toolset Layouts, do not work

Este hilo está resuelto. Aquí tiene una descripción del problema y la solución.

Problem

I created an Archive using a Toolset Layouts Archive Cell and inserted Custom Searches as select Fields.

Those custom fields do not show any search options on the archive page’s front-end.

This support ticket is created hace 6 años, 9 meses. 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.

Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.

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)

Este tema contiene 23 respuestas, tiene 2 mensajes.

Última actualización por Beda hace 6 años, 8 meses.

Asistido por: Beda.

Autor
Mensajes
#619090
Diamants – MASSILIA DIAMANT.png

I am trying to display a search result page with filter but the result don't work, the customs fields are hidden.

What's the problem ? thx

#619103

I get a 404 on the Login URL that you shared.

Can you send a link to the issue as well, so I can see it?
Eventually, a screenshot of where you expect to show Fields would help to immediately see what you miss on the output.

#619113
#619296

I can see that even if the fields exist and hold values against the French Products, the Search seems to not find those values and shows the Search handle empty.

This is unusual as it does not happen on a clean install, but there are several things that could have provoked this problem:
- switching default language in WPML
- a problem with WPML WooCommerce Multilingual, since that plugin is now outdated on your install
- another plugin or Theme interfering.

Does this not work properly since the begin, or did it start to break after an update or change of settings?

I think the fastest would be if I can deploy this locally and skin the site down to a minimal setup, which will use WooCommerce, the Multilingual add-ons and Toolset.

Would it be possible to send me that using these instructions?
https://toolset.com/faq/provide-supporters-copy-site/

On the current live site, you shared I would consider it safer not to make major changes - which we do not know the outcome of, yet.

I already tried to recreate the search on your site, this did not help.
It must be something deeper, which is possible to narrow down by skinning the site and analyse the query with a debug tool.

#619424
#620077

I am sorry, but this cannot be the copy of your site.

There are 30 outdated plugins, WordPress inclusive, and the front end is completely different than what we analysed here.

Please, can you provide me with a copy of the site where the problem is visible?

Please also make sure your plugins are updated first (I see that now WooCommerce Multilingual - which is involved here, is outdated)

Thank you

#620199
#620510

I still get an error on deploying the package using the native Duplicator Interface.

So I proceeded manually, however with wp-admin I get a 404 and with your custom login URL I get a The requested URL /your-custom-url was not found on this server.

So, I cannot duplicate this site.

Please provide me with an unaltered copy, where the native paths of WordPress are not hidden, or eventually, there are instructions to install the site that I miss.

#620518
#620532

No, that is the URL to your live site, and locally your Custom WP-Admin rewrite does not work.

The duplicator you shared, is this a copy of a site where WordPress has not been modified?
I suspect it is the same site.
I cannot use this to replicate it, as it fails.

Maybe you can point me to the customizations on WordPress you made so I can try to solve them so to replicate it.

#620542

if you delete a security plugin (wp cerber) i think that's work.

#620596

OK, finally I managed to log in and deploy this site.
On the Front End (Log In) it seems some PHP Script is echoed instead of executed, I thought you want to know.
You see it on the WordPress Admin Log In Page:

'Widget Social', 'id' => 'new-widget-area', 'before_widget' => '
', 'after_widget' => '
', ) ); } add_action( 'widgets_init', 'social_widgets_init' );

Then there are several PHP errors on the front end if WP Debug is enabled:

( ! ) Deprecated: Function create_function() is deprecated in .../wp-content/plugins/easy-social-icons/easy-social-icons.php on line 1455
( ! ) Deprecated: The each() function is deprecated. This message will be suppressed on further calls in .../wp-content/plugins/sitepress-multilingual-cms/lib/dqml2tree.php on line 475
( ! ) Warning: Cannot modify header information - headers already sent by (output started at .../wp-content/plugins/sitepress-multilingual-cms/lib/dqml2tree.php:475) in .../wp-includes/pluggable.php on line 1216
( ! ) Notice: Undefined index: Sorry! We tried, but we couldn't install Jetpack for you ?. Please go to the Plugins tab to install it, and finish setting up your store. in .../wp-content/plugins/wpml-string-translation/classes/mo-scan/wpml-st-mo-scan-storage.php on line 87
( ! ) Notice: Undefined index: Sorry, we couldn't connect your store to Jetpack in .../wp-content/plugins/wpml-string-translation/classes/mo-scan/wpml-st-mo-scan-storage.php on line 87
( ! ) Notice: Undefined index: Your site might be on a private network. Jetpack can only connect to public sites. Please make sure your site is visible over the internet, and then try connecting again ?. in .../wp-content/plugins/wpml-string-translation/classes/mo-scan/wpml-st-mo-scan-storage.php on line 87
( ! ) Notice: Undefined index: Your store is almost ready! To activate services like %s, just connect with Jetpack. in .../wp-content/plugins/wpml-string-translation/classes/mo-scan/wpml-st-mo-scan-storage.php on line 87
( ! ) Notice: Undefined index: automated taxes in .../wp-content/plugins/wpml-string-translation/classes/mo-scan/wpml-st-mo-scan-storage.php on line 87
( ! ) Notice: Undefined index: automated taxes, live rates and discounted shipping labels in .../wp-content/plugins/wpml-string-translation/classes/mo-scan/wpml-st-mo-scan-storage.php on line 87
( ! ) Notice: Undefined index: live rates and discounted shipping labels in .../wp-content/plugins/wpml-string-translation/classes/mo-scan/wpml-st-mo-scan-storage.php on line 87

The list goes on.

Please report the WPML errors to the WPML forum here:
https://wpml.org/forums/

Due to this errors, I disabled all Plugins but Toolset on the local duplication.

Then, I reactivated also the WPML Plugins.
The only remaining error now is:

( ! ) Deprecated: The each() function is deprecated. This message will be suppressed on further calls in .../wp-content/plugins/sitepress-multilingual-cms/lib/dqml2tree.php on line 475

Not really a biggy, but if possible please report that to WPML.
I already updated the supporters there.

Now, please share with me the exact URL of the:
- page where I see the issue
- the Archive I need to edit
- The Layout that is showing all this

I need this details as it clearly seems that on the duplicator the things are very differnt to your live install.
Locally, none of the exyisting Layouts actually applies to any archive at all, and on the live site, the issue is in an archive as far I recall, but nowl the Login URL you shared is again a 404.

With this limited instructions on the issue, and no clear path to replicate it, it's not possible to solve this.

Can you submit the exact information as required?

Thank you.

#620619
#620621

Please share with me the exact URL of the:
- page where I see the issue
- the Archive I need to edit (url)
- The Layout that is showing all this (url)

I need this details as it clearly seems that on the duplicator the things are very different to your live install.
Locally, none of the existing Layouts actually applies to any archive at all, and on the live site, the issue is in an archive as far I recall, but now the Login URL you shared is again a 404.

#620625

ok :

enlace oculto

the archive is "WordPress Archive" enlace oculto

enlace oculto