arturofez

Okey, thank you, I opened a issue in GitHub here

https://github.com/pods-framework/pods/issues/7272

Hi,

Thanks for your response. The target field of the condition does not support the comparator “IN” because it is a multiple selection field, as can be observed in the image:

The field “Técnico/Tecnológico” is a relationship field with simple custom list and multiple selection type.

I just installed Pods 3.0.5, and it works now! Thanks.

Some follow-up questions:

• When the field is required, I can’t hide it because it shows a required error upon saving even when it is hidden. Is this the expected behavior?
• Will it be possible to apply conditional logic to group of fields in a pod?

Perhaps for a new feature or enhancement? Should I open an issue on GitHub?

Thank you again, the conditional logic feature is fenomenal!

Yes, the issue occurs during the initial load when editing the CPT instances (post.php?post=1234&action=edit)

That’s exactly what I just did! And it works now. Thank you.

Do you know what could be happening?

Edit: Okay, it works, but only when I change the value and then select it back. When it loads, the field still does not appear

• This reply was modified 1 year, 6 months ago by arturofez.

Okey, I think I see the error, but I’m not sure why it’s happening. Comparison operator is ‘>’ in the console, even though it’s supposed to be set to ‘is’ (‘=’).

When I choose another value, which is greater than 78, the field is displayed!

That’s right, I’m using the term_id of the taxonomy term:

I’m using single select and radio buttons as display options in the field used for filtering.

Okay, I finally found the problem.

I tried to disable as many plugins as I could, but the problem persists. Then, I downloaded and installed WordPress locally, and the problem disappeared!

After a lot of debugging, I realized that the function session_save_path() wasn’t always working correctly. It works fine if the function is called in a code snippet, but when it is called from the Pods API php file, it returns false!

So I finally discovered that with my hosting provider, in order for changes in php.ini to take effect in all directories, you need to create a shortcut to php.ini in each directory. So, this would be a solution.

I also tried setting the session.save_path directive in the .htaccess file, but it failed because PHP was running in “CGI mode.”

Therefore, the simplest solution is to set the session save path in the wp_config.php file of WordPress, like this:

@ini_set( 'session.save_path', 'route/to/session/save/path' );

And it works every time! Thank you for the support, we can mark this as resolved.

Okey, here is the code.

$fields = [
	'nombre',
	'apellidos',
	'nombre_organizacion',
	'email_de_contacto',
	'telefono',
	'municipio',
	'mensaje',
	'entidad' => array( 'default' => $id, 'type' => 'hidden' ),
];

echo $pods->form( $fields, 'Contactar' );

The form is displayed, and I can submit it when I’m logged in, but it fails with anonymous users (users who are not logged in).