CS Form Reset button issue

Hi,

I am testing out the new Cornerstone Forms plugin. I am working on developing a filter form for Custom Post Type entries that will be based on various taxonomies. However, the font color styling for the “Form Reset” button isn’t applying, and the button label isn’t showing on the front-end.

It seems the issue is related to the auto-translation of “Reset.” I can’t find the Text parameters in the Form Reset Element Input Settings, similar to those found in the Submit Button Element. I also notice that the button label “Reset” is being translated on the fly into the default WordPress installation language. I can see the label in black color only (as styling not applied) inside CS Editor but not on front-end.

Hey John,

For this case, we’ll need to check your exact setup. Please provide the following details in the Secure Note.

  • WordPress Login URL
  • Admin username and password

You can find the Secure Note button at the bottom of your posts.

Thanks.

Hey @christian,

I have published the credentials in a Secure Note.

Hey John,

The style should be applied.
image

image

Disable the “Simulate Error” option in the Form element settings because this is what is causing the different colors applied to the Reset button.

Thanks.

Hi @ruenel,

I experimented with different action consequences with Simutate Error and haven’t found how to get rid of it. Sometimes it is not enough simply to switch it off, the button label is still not shown at the front end afterwords. I tried to add a new Form Reset with no success. Probably altering Outline behavior for other Form elements may also have an impact on this.

But this is not the worst thing. I’m having difficulty getting filters to function properly with my Custom Post Type in general. Here is another page example.

I revied the new YouTube video a few times and followed it along step by step. First I tried to make it work with a CPT loop component, but it didn’t. I tried copying the looper grid to another archive page as a set of elements instead of a component, but it still didn’t work.

Things I noticed along the way:

  1. If I keep the Form Method as POST it doesn’t change URL parameters. Meybe it is the way it should be but if I need URL parameters to change on terms clicks I need to use GET or PUT method. Is that correct? None of those really influence the sort of CPT. They stay unchanged and don’t work for Document Types and Owners in my case.
  2. Adding a Loading Area to the container with a CPT Looper and a Change Selector ID shows that they are connected. When I click on the terms, I notice the background color change along with the Lottie animation play. However, again that doesn’t change the output of CPT items on manipulations with Document Types and Owners.

I’ll share a different archive layout in Secure Note.

Oh, it seams like it works only with one taxonomy out of three I have for Documents CPT. And excluding empty terms will still leave some terms that could fit into other categories.

For example, every document is categorized by type, year, and owner. If I create separate archives for these document types and want a filter for year and owner within each Document type, I may still encounter terms that don’t exist in it but used in others.

When creating an archive, we specify conditions to display Documents CPT let’s say with the Orders Document type only. The Looper archive will exclusively display them by default. If we don’t have specific years or owners for this document type, they will be shown as they have been used in other Document types of the Documents CPT. Creating separate owner/year taxonomies for each document type would prevent us from using a single filter for year/owner in the overall Document archive. Please consider adding a feature in future releases to show terms that belong to the currently used Looper instead of a general term cloud for its CPT. Ideally also taking into account meta filtering as well if used and that is possible.

Coming back to the issue with the filter. What is the reason that it only functions with the ‘Years’ parameter while the ‘Owners’ and ‘Types’ are overlooked? Seach also doesn’t seam to work or not set properly. There was no info about it in the video mentioned. It was added but not explained.

Disabling the label inside the Checkbox List also disrupts the Options for custom font styling within the form element. To maintain font styles, we should keep the label as ‘On’ but remove the label text from the relevant property field in Cornerstone.

I have tried Select field but the result is the same. Only Years taxonomy terms are working.

I have another question, though. Is there a way to define terms blank on page load and/or to make them preselected? By default, it selects the very first one in the array. I tried to put this {{ term.name({"term":"470"}) }} inside Value parameter of the field but it didn’t help to pre-populate the term I wanted. How does it work if it does at the current version of CS Forms?

This issue with the Select not selecting based on your value is something we are fixing in the next Forms release. Stay tuned and have a great day.

1 Like