#7450 – Problem with homepage and params

Hi

Is it a bug or is there some setting I should make?

This is as expected. If you add parameters to a URL, then it's not the same URL anymore, it can show a totally different page and the meta data or any other data attached to the home page does not apply anymore.

fbclid or gclid for the ads

We have a list of known tracking vars that are automaticall removed when checking for a URL meta:

'utm_source', 'utm_medium', 'utm_term', 'utm_content', 'utm_id', 'utm_campaign', 'gclid', 'fb_xd_bust',
		'fb_xd_fragment', 'hitcount'

fbclid is not one of them but you're right we should add it to the list. You can add any variable to the list by using a "filter", a line of code you can add in a specific file and that will survive future sh404SEF updates.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

Hi

Yes, that file will be overwritten at next update, although I have already added that variable to the list.

I did not understand the solution you described

I did not describe it enough to be really understood but if you can look into sh404SEF files, then I'm sure you'll be interested in that.

sh404SEF has the concept of "hooks" taken from WordPress. It means you can modify some of the data and code sh404SEF uses, without your changes being deleted by next updates. It's a bit like like template overrides but for the code.

In your case, you need to do the following:

- in /libraries/weeblr you'll see a file called sh404sef_functions.php

- if the file does not exists, just create it

- in that file, paste the following:

<?php
/**
 * sh404SEF hooks file: this file is automatically loaded by sh404SEF and you can use it
 * to create deep customization of sh404SEF behavior. We have added a few examples of
 * hooks but there are more.
 *
 * Note that we do not provide any support for using hooks. Please always mention that you created
 * custom hooks when asking for support on any other topic.
 *
 */

defined('_JEXEC') or die;

/**
 * Filter the  list of query variables that should be stripped from requests before doing
 * comparison operations, to lookup custom meta data or similar.
 *
 * @api
 * @package sh404SEF\filter\routing
 * @var sh404sef_tracking_vars_to_strip
 *
 * @param array $varList The list of query variables to remove from query.
 *
 * @return array
 * @since   4.13.0
 *
 */
ShlHook::add(
	'sh404sef_tracking_vars_to_strip',
	function ($varsList) {

		$varsList = array_merge(
			$varsList,
			array(
				'fbclid',
                'anotherone',
                'one_more' 
			)
		);

		return $varsList;
	}
);

Save the file and fbclid, anotherone and one_more are now added to the list of variables stripped from the URL before checking if meta data are associated with that URL.

To deactivate the file, rename it to something else. Like I said, you can update sh404SEF and that file will not be touched.

Best regards

Yannick Gaultier

weeblr.com / @weeblr