Option "using existing custom field values" in WordPress Archive page search form

This support ticket is created 3 years, 10 months 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.

This topic is split from https://toolset.com/forums/topic/toolset-maps-breaks-the-custom-post-type-when-set-up-correctly/

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 7 replies, has 2 voices.

Last updated by Luo Yang 3 years ago.

Assisted by: Luo Yang.

Author

Posts

September 1, 2021 at 7:23 am #2156739

reeceY

I am following up to this ticket with another issue that is persisting as well.
When I add a custom field search parameter on the archive page it never saves any of the custom values. It only works when it is set to "using existing custom field values".

Here is a video of it in action as well.
hidden link

Thank You

September 1, 2021 at 7:26 am #2156755

Luo Yang

Hello,

I can duplicate the same problem in my localhost, and I see below JS error after add an option in the dropdown field of custom search form:

Uncaught TypeError: c[e].replace is not a function

Can you confirm it is the same problem in your website? thanks

September 1, 2021 at 2:58 pm #2157223

reeceY

Yes, this is the same error I am seeing too.

September 2, 2021 at 1:54 am #2157801

Luo Yang

Thanks for the confirmation, I have escalated this issue, will update here if there is anything news, currently, you can use classic editor to setup the post view, for example:
Dashboard-> Toolset-> Settings-> General
In section "Editing experience", enable option "Show both the legacy and Blocks interface and let me choose which to use for each item I build".
Dashboard-> Toolset-> Views, setup the post view with classic editor, and test again.

September 2, 2021 at 5:58 pm #2158597

reeceY

To be clear... for both tickets you are telling me I have to start all over again and build using the classic editor to get the plugin to work properly?

September 3, 2021 at 1:38 am #2159069

Luo Yang

To be clear, that is only a temporary workaround, and it has been escalated to our developers, you can also wait for the fix.

September 3, 2021 at 2:14 am #2159099

Luo Yang

And there is another workaround without breaking your existed design.

You can try to setup the search field manually with shortcode [wpv-control-postmeta], and setup the URL parameter and options, see our document:
https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-control-postmeta

And add a field filter into the WordPress Archive on the URL parameter of above search field:
https://toolset.com/documentation/user-guides/views/filtering-views-by-custom-fields/
section "Source for compare value":
URL parameter
The value for the filter is set in the URL to the page

May 31, 2022 at 9:14 am #2374397

Luo Yang

Hi,

I wanted to let you know that we published plugin updates today that includes a fix for this issue.

If the updates do not show up on your plugin installer page (click the registered link beneath the plugin name to go to the custom installer page) click the Check for Updates button to update the list.

Or you can download the latest versions from your accounts page: https://toolset.com/account/downloads

Thank you.