Working on this as there are two other identical tickets. It’s a weird issue that is very difficult to replicate and narrow down.
I’ve narrowed down the issue. And I’m working on solving it. WordPress’s Transients are not respecting the expiration in place.
Short term solution for you, is to add this to your functions or config file:
define('GF_HUBSPOT_DEBUG', true);
It will force the transient cache to refresh. It also includes a pretty extensive log in your wp-content/uploads folder, but you can ignore that.
Thanks for working on the issue. For what it’s worth, adding that debug rule to my functions.php file didn’t allow the connector feed to see the new hub post fields. I even tried deleting the connector and adding a new one and it still only sees the old fields. I had to add it to my wp-config.php to get them to show up.
Not sure if that will help in your search for a fix or not.
Nah, that doesn’t help in my search.
I’m actually in the process of reworking the function to not use WordPress’s transients at all, but a custom one that I’m building myself. That way I can guarantee that it’ll work. Hopefully I’ll have a fix out later today, now that I know with certainty that it’s the set/get transient api.
The reason why adding that line didn’t work when you added it to your functions file, is likely because by that point, it was already defined… so yea, adding it to your wp-config makes sure that it proves dominant… good to know, though 🙂
Should be resolved with version 2.1 I’ve tested this extensively all day today, as I rolled my own caching solution instead of relying on WP’s built in ones.