I eventually used a combination of update_option and WP Cron: // Create the option. update_option(‘foo’, ‘bar’, false); /** * Schedule it to be deleted one week from now. * * @param int Expiration timestamp * @param string Hook that will be invoked * @param string Params to send to the hook callback */ wp_schedule_single_event( time() … Read more
but I’d like to know if there is a way to prevent them from getting into my database in the first place. The only way to prevent expired transients ever being a thing is to never use them to begin with. When you create a transient an option is created with a particular name. Eventually … Read more
What is the best option to fetch the different online statuses automatically “on-the-fly” in real time? What is the most efficient way of fetching (external) data like these? Optimally everything happens “on-the-fly” as soon as the source differ from the site. At least it should run a check every page update. -What about caching? I … Read more
No: each transient will need a unique name. Per the documentation: If a transient exists, this function will update the transient’s expiration time.
No, there isn’t. WordPress does not provide page caching mechanisms, and has no APIs for it. There is no generic way to say example.com/page is now stale and needs recreating. Nor is there any generic way to pre-generate every page short of visiting them all. Every plugin uses a different solution with different APIs and … Read more
So the answer was to use base64_encode and base64_decode. So basically doing something like this to set the transient: $json_contact_info = json_encode( $contact_info ); $transient_data = encrypt_text( $json_contact_info ); $transient_array = base64_encode( $transient_data ); $transient_set = set_transient( $transient_name, $transient_array, 60 * 60 * 24 * 7 ); And then to get the transient: $decrypted_transient_data = … Read more
First, you don’t need a raw SQL query, and by using one you give up all of WP’s optimisations. For example, if you run the query twice, it runs twice. If you had used WP_Query to getch those posts though, it would save them the first time to avoid making additional queries. It’s even possible … Read more
Without object caching plugins transients are stored using options API and, if set to expire, they have auto-load disabled. Meaning: First request to transient needs to fetch it from database. Subsequent requests will get data from memory. However note that “memory” here is memory space of single specific page load. It’s not shared and not … Read more
What is the code on line 3645? You didn’t specify. From what I see in your code, $transient_name should be something like “_my_post_list_transient” – a string. If $transient_name is returning a post object, then your call to this function may be the problem.
I don’t think a transient per post is a bad idea at all, and it’s certainly more efficient than firing the API call on every load. Just be sure to give your transient name a unique name – maybe append the post ID to it.