Skip Navigation

[Résolu] I am trying to determine X for "wpcf-fields-radio-option-XXXXXXXXXXX"

This support ticket is created Il y a 2 années et 2 mois. 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 contains 5 réponses, has 2 voix.

Last updated by Beda Il y a 2 années et 2 mois.

Assigned support staff: Beda.


Tell us what you are trying to do?

A table to holds custom fields is not displaying one data type. I noticed the option "wpcf" value is the same as another but the fields are different.

Is there any documentation that you are following?

Is there a similar example that we can see?

Follow the link below scroll to Motor Charateristic option and notice the single lenthg is blank.

What is the link to your site?

hidden link


What is the issue we can help you with?

That key is an. option key, which you cannot edit or manipulate or use at all in the WP Admin, it's internal, for Toolset.

If you want to "guess" the "X" in your example, you can't.
That is a random encoded string (numeric) that changes for each option.
You can't possibly guess it neither with Code or just by logic, it is on purpose unique, to differentiate the options.

Each option created will have such new "unique" part of the option key.

Maybe if you can describe the desired result, and what you get instead, I can suggest some solution?


Thank you for your help.

Best email:

OK, Perhaps I should explain: I am filling in temporarily for my company as our web admin recently retired. I have been doing small updates and changes using WordPress and one of the plugins we use is Toolset. I can read code and have experience with a lot of different languages. So perhaps I simply need to take some lessons to learn Toolset. Either way, my current issue is that one view does not display the data that is entered.

hidden link

The motor characteristics for the NEMA 17 single stack do not display. (1.png)

So I need to figure out why this data is not displaying. The custom field looks good and displays some of the information. (2.png)

I do have another problem that is similar. Our datasheet download page shows four items (which there are four of) but only displays 3 of them. (3.png) Again, NEMA 17.

I apologize as I am a newb, but I need to fix this problem and then I can take some time to learn more. I wouldn't mind taking a course or tutorial if you have suggestions.

Best Regards,



Ok, the "Motor Characteristics" is hidden in a folded element, tricky to find, but I located it.
It looks like the field is not populated for those posts.
Also, the values displayed for that column (where displaying) are not what you show in the Screenshot to be the options of that field.
It shows 8.5 (3.8) and 10 (4.5) and that is nowhere defined in the Field you show

I guess that's because the field is another, and that field, has no value for the Holding torque and other items but does for Radial load limit and Axial Load Limit

I'd need to confirm that but I am pretty sure this is the cause, and you can't "switch" Field within one column, the column will always be for ONE Field only.
So either you use the field you show in the screenshot and need to populate that for all the posts, or you use the other field and need to populate that for all posts if you have that value in ONE column

Each column is one field
Each row a post.
(if created in a View)

Does this help?
I would need log in details to a staging site if not, so I can show you 🙂



I am getting closer to the solution. I found the single stack (LMD single) did not have radial or axial loads listed, when I went to create them I got an error that the slug was already in use. I dug around and found the LMD Triple had the single length slug. (See picture) Fixing these slugs did not resolve my issue. I am wondering if it something that is wrong with my taxonomies.

This control type displays the correct single length data, but now I lost the loads for single and triple. I will keep digging, but I would appreciate it if you would take a look around. I do not have a staging site, but I do have regular backups. I will perform another one right now.

I do appreciate your help. I am still working through the Toolset tutorials. I am starting to understand how everything interacts. Here is a new user I created with admin privileges. I will remove the account when we are done.


Best Regards,



Those are not taxonomies, those are Fields.
When you change the slugs of Fields, you completely change the information for each post.

Meaning, you can't then later display the older field - you'd have to change to the new slug if you change it.

But Toolset Types is actually quite smart here, meaning, you can change a field slug and the plugin will make sure the old posts get the new slug.

Let me make an example.

1. You have a field "my-field" and populate many posts with it
2. You also display that field with [types field='my-field'][/types] in many places
3. Now you change the slug of my-field to my-field-updated
4. All ShortCodes of [types field='my-field'][/types] will stop working, but as soon you just change them to [types field='my-field-updated'][/types] they'll work again because all existing fields were updated during the process already in the background by Types.

Now, whenever a field is empty, it will also not display any value, and often that results in the scenario you shared in the begin (empty places)

I am however not sure what I should look at in the backend at this point.
I would need one precise post, for example, where you are sure the data you expect to see, is saved.
Also ensure, the data you expect to see is shown with the right shortcode.

Then, if the data is still not shown, I can take a look at this single post or View and suggest edits, so you can apply it to the template, or view.

It would be much easier for you to have a staging site, also for future development.
This can be just a subsite on the same server, some hosts also offer full staging packages. It helps a lot when debugging or even just testing an update.
On a live site, I couldn't make edits, but on a staging site, we could do this in a safe way.