Quote:
Originally Posted by Terisa de morgan
I don't think I'm able to run from source code (not enough time), but I'll take into account as I even have some plugins for myself that using a lot get metadata... and I've got a lot of composite columns.
|
FWIW: if you can, you should use get_proxy_metadata() instead of get_metadata(). Proxy metadata uses lazy evaluation for all field accesses, making it much faster for applications that use some of the metadata from a book.
It is usually a direct replacement for get_metadata(). However, it can't be used if you use mi.set() to modify the metadata. Other metadata methods that can't be used are smart_update(), template_to_attribute(), set_user_metadata(), set_all_user_metadata(), set_identifier(s)(), remove_stale_user_metadata(), and all_non_none_fields().