blacklodgebeer

Hi

I’ve tried those things, a couple of times now. It does seem only affect a specific pod which is a taxonomy extension and given the complicated way I’m trying to use and display it would be best for me to rethink it anyway. I will try and recreate it though on some other websites I’m working on and see if I can find a common cause.

That seems to have worked, thanks for your help.

Here’s some info from the WooCommerce log

2022-09-13T18:21:10+00:00 CRITICAL Uncaught Error: Unsupported operand types in /var/www/html/wp-content/plugins/pinterest-for-woocommerce/src/TrackerSnapshot.php:88
Stack trace:
#0 /var/www/html/wp-content/plugins/pinterest-for-woocommerce/src/TrackerSnapshot.php(61): Automattic\WooCommerce\Pinterest\TrackerSnapshot::parse_settings()
#1 /var/www/html/wp-content/plugins/pinterest-for-woocommerce/src/TrackerSnapshot.php(43): Automattic\WooCommerce\Pinterest\TrackerSnapshot::include_snapshot_data(Array)
#2 /var/www/html/wp-includes/class-wp-hook.php(307): Automattic\WooCommerce\Pinterest\TrackerSnapshot::Automattic\WooCommerce\Pinterest\{closure}(Array)
#3 /var/www/html/wp-includes/plugin.php(191): WP_Hook->apply_filters(Array, Array)
#4 /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-tracker.php(181): apply_filters(‘woocommerce_tra…’, Array)
#5 /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-tracker.php(65): WC_Tracker::get_tracking_data()
#6 /var/www/html/wp-includes/class-wp-hook.php(307): WC_Tracker::send_trac in /var/www/html/wp-content/plugins/pinterest-for-woocommerce/src/TrackerSnapshot.php on line 88

‘It makes a lot more sense to name one’s files and folders properly than to do the work twice, thrice or five times with cryptic filenames everywhere’

Some people don’t get that choice.

Also I do find it strange the reluctance to have the ability to give a ‘friendly name’ for each playlist, relying on deriving names from playlist urls seems to be a way of making something as user unfriendly as possible given that there’s no guarantee of any meaningful descriptive name within the url.

It seems strange that you would discourage multiple streams, not all live streams are traditional broadcast events requiring the viewer to listen – I could understand the conflict reasoning in that scenario – but multiple proximity landscape broadcasts for example or CCTV setups, things like that can have a requirement for multiple players, particularly CCTV.

I know audio can be an issue in some circumstances, particularly when viewing on iPads although I have managed to set up three live stream video players with flowplayer all three autoplaying on iPad and have managed to get audio to play on all three simultaneously, but in standard desktop browsers these issues are relatively minor or none existent – it just seems like you are purposely reducing your potential customer base by placing unnecessary conditions on your product.

Also, as I’ve just remembered why I haven’t persevered with the plugin, is there any reason why audio can only be played on one player when multiple players are present on a page and when multiple players are on the same page is there any reason why only one autoplays? I know these are not limitations of flowplayer so must be a feature of this plugin.

Perhaps I wasn’t as clear as i could have been, it simply needs a place where a custom name can be inputted, like a page/post name has a title field.

Thanks for the reply, I’ll have a look at that fix.

Cheers