pods conflicts with any Theme with built in custom content types?

What sort of conflict are you talking about? I don’t think we’ve seen any conflicts so far with content types in any other themes. Can you expand a bit more and maybe we can help get it compatible with Portfolio theme?

I will reactivate it soon and take note of the error. My recollection is that it was a open_basedir restriction in effect error.
thanks

to clarify it is Portfolio Post Type Plugin and Options Framework with the Portfolio Press Theme by Devin Price. Here is the error:

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/var/sessions) is not within the allowed path(s): (/home:/tmp:/usr) in /home/xxxxxx/public_html/xxxxxx/wp-content/plugins/pods/includes/general.php on line 1832

thanks

This isn’t a theme conflict.

Try contacting your host about your session path and see if PHP sessions are properly configured.

thanks!

What is the exact solution of this trouble? Because my server logs is full of this warning message.

PHP Warning: file_exists(): open_basedir restriction in effect.
File(/var/lib/php5) is not within the allowed path(s): in /home/monsite/server/public/wp-content/plugins/pods/includes/general.php on line 1832

I don’t understand Scott’s solution? What is session path not properly configured?

Scott was saying that this error is generally caused by a problem with server configuration that needs to be addressed by your hosting provider or system administrator.

What version of Pods are you using?

I am using 2.3.18 version.
Ok I understand it’s a problem of to change session.save_path from /var/lib/php5 (not writable) to /tmp (writable)!

But if I upgrade Pods to the latest version, I would not be anymore to do that?

Pods 2.4.3 should resolve this, though I can’t guarantee that. Still, correcting that error in your configuration is a good thing to do.

The other reason to upgrade to Pods 2.4.3 is because of the security vulnerability it patches. See: https://pods.io/2014/06/23/full-details-pods-2-x-security-vulnerability-patched-pods-2-4-2/

ok thanks, I gonna upgrade it. Just to replace the Pods directory by this new version is it sufficient? There is no change in database structure?

Yes that will work. Database is unaffected by the update.