Thanks, that certainly helps. The file on our plugin where this function date_default_timezone_set
is used (here), is only loaded for really old versions of WooCommerce (before 3.0). Even for those versions, that function sets the timezone back to the original eight after making transformations, so it only does this temporarily. There’s another file (here) calling this function, but here too it’s temporary and set right back to the original afterwards (and in this particular case, this is only called during the creation of a PDF file, not in the WordPress backend).
WooCommerce does the same thing (source here). This is harmless because it’s set back to the original timezone right after making those changes.
I think your host found that function in our plugin and assumed it was the line date_default_timezone_set( 'UTC' );
that caused the issue without looking further. But I can only conclude this happens somewhere else – your site uses WooCommerce 4.6.0 which means that the code I referred to above from our plugin is not loaded and the WooCommerce functions are used instead.
It is more likely there is custom code on your site somewhere calling date_default_timezone_set
.
Perhaps you could ask your host for a list of all files on your site that call this function?