MFredin
asked on
Trouble implementing custom tag
I'm trying to implement this... http://developer.fusium.com/tools/ses.cfm seems pretty straight forward but I'm just having some trouble getting it to work.
Basically, I downloaded the sesConverter.cfm file to my Includes/Functions directory.
In my included header, I added:
<cfoutput>
<!--- For SES Converter --->
<cfif isDefined("variables.baseH
<base href="#variables.baseHref#
</cfif>
</cfoutput>
And in my pages I included:
<!--- ses stuff --->
<cfset SESdummyExtension = ".cfm">
<cfset SESrBaseName = "baseHREF">
<cfinclude template="../Includes/Func
Then I'm just using regular href links:
<a href="details.cfm?listing_
What am I missing here? My ? are not being converted to /.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
according to the docs
"SES URLs will not work unless you use the basehref tag. BASEHREF is not a CF tag, it's standard HTML.
>>>SES URLs mess up your relative links when this tag is not used. "<<<
so it should work (but I've not tried it)
but seems like it from this
http://www.codeodor.com/index.cfm/2007/4/6/Did-you-know-about-the-base-tag/1101
"SES URLs will not work unless you use the basehref tag. BASEHREF is not a CF tag, it's standard HTML.
>>>SES URLs mess up your relative links when this tag is not used. "<<<
so it should work (but I've not tried it)
but seems like it from this
http://www.codeodor.com/index.cfm/2007/4/6/Did-you-know-about-the-base-tag/1101
ASKER
oh, very nice. when I added the base href tag, text that doesn't have a specific font-size assigned to it ballooned up to a much larger font size. Any idea why or how to fix that?
hmm..odd.
perhaps add your default font size to body in css
body {
font-size:12pt;
}
perhaps add your default font size to body in css
body {
font-size:12pt;
}
ASKER
tried that and no luck
Can't see how it's related to the sesconverter problem except that it must be due to a path issue (sesC doesn't do anything to styles)
are you defining all your css in an external file? Might try an absolute path to that css file
are you defining all your css in an external file? Might try an absolute path to that css file
ASKER
That makes sense and it's working now... but one issue. It's screwing with my relative paths. For example, the patch to the logo at the top of the page is ../Images/logo.jpg. Since I was always only working 1 directory deep, this worked fine. Now that I am using / in the url, the system things things are many directories deep. Will I have to use absolute paths now or what would be the best way to work this out?
Thanks!