The core Drupal module that creates friendly page names (PATH) might work very well for the omniture module as a way for content creators to define a page name to use. Simply grabbing document.title is not the most reliable method as updates to Drupal may change how page names are populated into SiteCatalyst.

See attached image for path naming tool on the create a node page. The "Omniture Page Name" could be placed right under this.

CommentFileSizeAuthor
pagename.png7.23 KBClint Eagar

Comments

Clint Eagar’s picture

Clint Eagar commented

I'm currently using this script to populate pagename, channel, and page type:

	if ($title != "") {
		$scpageName = $title;
	}
	else {
		$scpageName = "Home";
	}

	if ($node->type == 'product') {
		$scChannel = str_replace('','',strip_tags($breadcrumb));
		$scmerchCat = $scChannel;
	}
	if ($scChannel == 'Catalog') {
		$scChannel = "Catalog » $scmerchCat";
	}

	if (($title == "Page not found") || ($title == "Access denied")) {
		$scpageType = $title;
	}

Then is in the SiteCatalyst Code:
s.pageName=" echo $scpageName; "
s.channel=" echo $scChannel; "
s.pageType=" echo $scpageType; "

Can this type of logic be placed in the module?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Version: » 6.x-1.x-dev
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Yes, that exact kind of code from #1 is what should go in the theorecical omniture.inc file or the proposed hook_omniture.

I think a system mimicking the path module is beyond what this module should do (not to mention a real administrative burden).