[Plugin: Types – Custom Fields and Custom Post Types Management] working with 3.5 yet?

Thank you for reporting this.

We’re about to start testing on WordPress 3.5 alpha this week. This version is very much not stable. At this point, we’re not going to make any changes in Types due to WP 3.5 issues, as they are likely to change. We’ll have a stable release with complete WordPress 3.5 support in time for the first WP 3.5 release candidate.

If you follow the WP development blog, you’ll see that this initial release includes a large number of unresolved changes and is not intended as reference for compatibility with themes and plugins.

Thanks for the reply. I see WP 3.5 is now up to beta 1 and “ready for testing by plug-in makers”, so I’m sure you guys will get it working with 3.5 soon ??

You’re right. It’s getting close to testing status. We’ll try to do this testing next week.

We’re also working on Types 1.0.5, so that new version will certainly be tested against WP 3.5.

Im using 3.4 and same problems

Notice: Trying to get property of non-object in
lugins\advanced-custom-fields\core\api.php on line 102
Notice: Trying to get property of non-object in

is there a HOOK to get this in:
if ( is_object($post) )
{
$post_id = $post->ID;
}
else
{
return false;
}

Folks, this thread is getting off topic and it’s really hard to track it.

To be more productive, would you mind opening specific threads about what you need in our own forum?

We have 3 developers tending to our forum and it’s difficult for us to spread over different support channels.

You can register for free:
https://wp-types.com/support/register/

I understand that it’s an inconvenience for you to create accounts in different places. Please remember that you’re getting support for a free plugin. This takes time and money and we’re trying to get our support people working efficiently. So, if you can take the few minutes to create these threads in our forum, we’ll be able to track progress a lot better.

Thanks. I really appreciate it!

How could it be getting off-topic? Its just two users reporting the seemingly identical issue, albeit spread across 2 versions of WP.

I paid for the product btw. Why assume I (or the other user) has a free version?