Hi,
just wanted to raise awareness of another PHP error. I already created a Git issue: https://github.com/ianhampton/Tealium-WordPress-Plugin/issues/7
Error Details
=============
An error of type E_ERROR was caused in line 24 of the file /data/www/bright-carrosserie.be/www/wp-content/plugins/tealium/tealium.options.php. Error message: Uncaught TypeError: join(): Argument #2 ($array) must be of type ?array, string given in /data/www/bright-carrosserie.be/www/wp-content/plugins/tealium/tealium.optio
ns.php:24
Stack trace:
#0 /data/www/bright-carrosserie.be/www/wp-content/plugins/tealium/tealium.options.php(24): join()
#1 /data/www/bright-carrosserie.be/www/wp-content/plugins/tealium/tealium.options.php(85): tealiumFormatAsName()
#2 /data/www/bright-carrosserie.be/www/wp-content/plugins/tealium/tealium.options.php(261): tealiumGenerateBulkDataSourceList()
#3 /data/www/bright-carrosserie.be/www/wp-content/plugins/tealium/tealium.php(82): include('...')
#4 /data/www/bright-carrosserie.be/www/wp-includes/class-wp-hook.php(308): options_page_tealium()
#5 /data/www/bright-carrosserie.be/www/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#6 /data/www/bright-carrosserie.be/www/wp-includes/plugin.php(517): WP_Hook->do_action()
#7 /data/www/bright-carrosserie.be/www/wp-admin/admin.php(259): do_action()
#8 /data/www/bright-carrosserie.be/www/wp-admin/options-general.php(10):
require_once('...')
#9 {main}
thrown
]]>
I have the error on my WordPress application:
Notice: Undefined offset: 0 in /var/www/html/wp-content/plugins/tealium/tealium.php on line 381
It’s because the roles of my user are not beginning from 0. So to fix we should replace
$utagdata['userRole'] = $role[0];
to
$utagdata['userRole'] = $role[array_key_first($role)];
at /var/www/html/wp-content/plugins/tealium/tealium.php on line 381
Can somebody do it, please?
]]>I tried adding a custom script tag but it doesn’t seem to work. Is there any setting within the plugin i can use?
]]>Since we switched to the Tealium integration connected to Google Analytics, we noticed our bounce rate increased.
I think is mainly because we were tracking few events like Depth Scroll and this was helping to consider some hits as bounces.
Is possible to add them again?
]]>The current integration is tracking the traffic from administrators and other authors. Can you please guys add the option to don’t track it?
]]>Is there any way to add post_id to the list since that would be a unique value that could be targetted in Audience Stream? The title may change.
]]>Hi there,
We have a custom namespace for the Data Layer JS Object. Can you add a possibility to override the default namespace “utag_data” to the plugin?
Thank you,
Livio
Hello,
I have been receiving PHP notices for some fields that are undefined (postCategory, postTags). In my settings, for Data Layer Style is set to underscore
, while the legacy option is camel case
.
When I switch to camel case
the PHP notices go away, however I would prefer the underscore
option (which is defaulted on several of my sites and all have the same issue).
Is there a solution for this?
Can this be fixed on the next update?
All Advanced Custom Fields uTag displays are pretty pointless in their current state. Look like so:
"book_now_system": [
"field_562c493397c4e"
]
All of the ACF-generated fields show this. Pretty big pain since I don’t know of an easy way to de-register the 100+ fields used across the site in one fell swoop.
]]>Currently the snippet is included on all pages including the wp-admin pages. Easy enough to resolve, but I don’t think this should be default behaviour.
We’re using the “Advanced Tag Code” section under the “Advanced Settings” tab.
]]>Hi Support,
When I use your plugin, it shows me the following error:
Undefined index: edit_last tealium.php on line 175
Undefined index: wp_page_template in tealium.php on line 175
The line number 175 look like this:
$underscoreArray[$newKey] = convertCamelCase( $val, $underscoreArray[$newKey] );
If I change that line to this:
$underscoreArray[$newKey] = convertCamelCase( $val, $utagdata[$key] );
the plugin works correctly (no errors or warnings) and I show the correct information in the tag.
Can you please tell me if this change is correct?
Thanks in advance
]]>Line 274 in tealium.php generates a “Deprecated: Assigning the return value of new by reference is deprecated: warning. If you change it from:
$searchResults = &new WP_Query( 's='.str_replace( ' ', '+', $searchQuery.'&showposts=-1' ) );
to
$searchResults = new WP_Query( 's='.str_replace( ' ', '+', $searchQuery.'&showposts=-1' ) );
you will get rid of the warning.
]]>I suggest updating line 26 from:
add_options_page( 'Tealium Tag Settings', 'Tealium Tag Settings', 8 , 'tealium', 'options_page_tealium' );
to:
add_options_page( 'Tealium Tag Settings', 'Tealium Tag Settings', 'manage_options' , 'tealium', 'options_page_tealium' );
because using roles instead of capabilities is depriciated (and throws a long warning on my test site!).