nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

javascript include for cross-branch

ShovelFace

O/S: Solaris TS: 6.5 SP2

Find more posts tagged with

Comments

ShovelFace

O/S: Solaris TS: 6.5 SP2

ShovelFace

O/S: Solaris
TS: 6.5 SP2

When including a common .js library in FormAPI, if the .js is in the /iwmnt/default/main/ABC/WORKAREA/DEF/templatedata folder, works fine, as follows:

[HTML]
<script language="javascript" type="text/javascript" location="template-type" src="common.js"/>
[/HTML]

If I instead specify the full path to the common.js as follows, and change the location tag to 'webserver', it no longer works:

[HTML]
<script language="javascript" type="text/javascript" location="webserver" src="/iwmnt/default/main/ABC/WORKAREA/DEF/templatedata/common.js"/>
[/HTML]

Any thoughts? Once this works, the common.js file will then be moved to another branch and refereced according as per the broken example above.

Adam Stoller

PLEASE LEARN HOW TO FORMAT AND PREVIEW YOUR POSTS

You're saying this works:

<script language="javascript" type="text/javascript" location="template-type" src="common.js"/>

and this does not work:

<script language="javascript" type="text/javascript" location="webserver" src="/iwmnt/default/main/ABC/WORKAREA/DEF/templatedata/common.js"/>

Try changing

/iwmnt

/iw-mount

- the latter is a webserver virtual directory reference - the former is a filesystem path.

ShovelFace

change to iw-mount not having any effect. Any other thoughts?

ravio

change to iw-mount not having any effect. Any other thoughts?

if you are saying 'webserver' then it should be relative to the httpd used by TeamSite
So for your path, whatever you are setting there should be present under
$iw-home/httpd/

cc96ai

I put the js into $iw-home/httpd/iw/javascript

[html]
<script language="javascript" location="webserver" src="/iw/javascript/scripts.js"/>
[/html]

jkm

You can put all shared components like js,ipl,css etc in one branch for example say admin and then redirect the things using iwproxy_preconnect_remap. I find this way easy to mantain the code.

Annad

Hi,
My question is along the same line as the original post on this thread.
I have java script include in my DCT. I am on Windows and TS7.6.1.

The following works for me:


<script language="javascript" type="text/javascript" location="template-type" src="international.js"/>

However, when I put the full path of the .js file which exists on a global branch, it doesn't work.


<script language="javascript" type="text/javascript" location="template-type" src="Y:/global/main/iwcode/WORKAREA/iwcode/scripts/international/international.js"/>

Thanks,
Anna.

Annad

Hi,
My question is along the same line as the original post on this thread.
I have java script include in my DCT. I am on Windows and TS7.6.1.

The following works for me:
[html]
<script language="javascript" type="text/javascript" location="template-type" src="international.js"/>

[/html]

However, when I put the full path of the .js file which exists on a global branch, it doesn't work.
[html]
<script language="javascript" type="text/javascript" location="template-type" src="Y:/global/main/iwcode/WORKAREA/iwcode/scripts/international/international.js"/>

[/html]

Thanks,
Anna.

Annad

Any replies for my question??

I still couldn't get the full path starting at Y://global..../international.js to work.

Thanks in advance.
Anna.

Bhargav Coca

Anna,

I am taking a stride, is default not your root directory??

so your path should read something like this

[html]
<script language="javascript" type="text/javascript" location="template-type" src="Y:default/main/iwcode/WORKAREA/iwcode/scripts/international/international.js"/>
[/html]

Still wondering how can one get rid of "default"

Thanks

Annad

Thanks for the reply. We created a new store called 'global' and that's why there is no default store in the path to the script. I already tried what you suggested.

Now that I am thinking about it, I believe this has to do with permission to the global store more than anything. The datacapture.cfg file is probably not able to read the .js file from the global store.

Thanks,
Anna.

nipper

You are correct in that is it *probably* a permissions issue.

There are a few things you can do:

change from template-type to webserver and put the js under iwhome/httpd/iw

or

start making it a relative path (../../../../branch/WORKAREA/workarea/templatedata/....)

That will help figure out at what point the JS fails to load.

ISCBorisB

Thanks for the reply. We created a new store called 'global' and that's why there is no default store in the path to the script. I already tried what you suggested.

Now that I am thinking about it, I believe this has to do with permission to the global store more than anything. The datacapture.cfg file is probably not able to read the .js file from the global store.

Thanks,
Anna.

You can not use location="template-type" for the cross-branching JS reference.
As stated in the FormAPI guide "template-type...In this case, src specifies a location relative to the template type directory".

Instead, you should be using location="webserver" or no location at all, webserver is a default. So:

<script src="/iw-mount/global/main/iwcode/WORKAREA/iwcode/scripts/international/international.js"/>

Note:
- iw-mount should be used verbatim, this is a URL prefix (NOT a virtual drive reference!)
- leading slash before mount indicates absolute URI reference
- all of that, including iw-mount for cross-branches is documented in FormAPI Developer’s Guide, Chapter 2, paragraph "The DCT <script> tag"

Annad

Thanks,
As I mentioned earliar, if the javascript resides in the same branch as the datacapture.cfg everything works. So I decided to call the same script in the same folder, but this time by specifying the full path (see html code below) to the script instead of just mentioning the script name.

[html]
<script language="javascript" type="text/javascript" location="template-type" src="Y:dfait-maeci/main/internet-internet/international/international/WORKAREA/site/templatedata/pages-pages/generic-generique/international.js"/>

[/html]

To my surprise, this doesn't work. So now I know that the problem is not with permission, but with the way I reference the js script (full path Y://...) or something else.

Got any ideas on this one???

I NEED HELP!

-Anna-

nipper

I assume you missed Bo's post just a few minutes ahead of yours.

Adam Stoller

You can not use location="template-type" for the cross-branching JS reference.
As stated in the FormAPI guide "template-type...In this case, src specifies a location relative to the template type directory".

Instead, you should be using location="webserver" or no location at all, webserver is a default. So:

<script src="/iw-mount/global/main/iwcode/WORKAREA/iwcode/scripts/international/international.js"/>

Note:
- iw-mount should be used verbatim, this is a URL prefix (NOT a virtual drive reference!)
- leading slash before mount indicates absolute URI reference
- all of that, including iw-mount for cross-branches is documented in FormAPI Developer’s Guide, Chapter 2, paragraph "The DCT <script> tag"

Additional note: Even though TeamSite accepts script as an empty element - you'll be better off in the long term if you specify both a beginning and ending tag for it - i.e.:

# not-XHTML-compliant, not-portable
<script .../>
# XHTML-compliant and portable
<script ...></script>

ISCBorisB

Additional note: Even though TeamSite accepts script as an empty element - you'll be better off in the long term if you specify both a beginning and ending tag for it

I would disagree. The fact that DCT's <script> Tag resembles identically tagged HTML entity does not mean that we have to propagate IE idiosyncrasies
into templates. DCTs are not written in (X)HTML, are not and never will be parsed directly by browsers and there are no benefits whatever in making
certain parts of DCT's XML XHTML compliant.

Adam Stoller

I would disagree. The fact that DCT's <script> Tag resembles identically tagged HTML entity does mean that we have to propagate IE idiosyncrasies
into templates. DCTs are not written in (X)HTML, are not and never will be parsed directly by browsers and there are no benefits whatever in making
certain parts of DCT's XML XHTML compliant.

Welllll, okay as far as DCTs are concerned, I guess it's not a big point - but it can make a difference in generated output if you're planning to be XHTML compliant ...

Annad

Ok Guys,
Thanks a lot for all the replies. Yes I just missed Bo's reply. It did help me and I am already playing with the script and everything works fine.

Thanks a bunch!

-Anna-

Migrateduser

Sorry to resurrect an old topic, but this is no longer working in 7.3.x TeamSite - any ideas how to reference JS files within templates on the

drive (teamsite install folders)

ISCBorisB

Sorry to resurrect an old topic, but this is no longer working in 7.3.x TeamSite - any ideas how to reference JS files within templates on the drive (teamsite install folders)

Take a look at [post=172268]this post[/post]. Note that although Andy is talking about WFM there, that same technique *should* work in DCT.

claudiag

It's probably easiest just to reference it from the TS webserver. Anything placed in <iw-home>/TeamSite/httpd/iw should be accessible at <yourserver>/iw/myscript.js.

ETA: just read the post linked by ISCBorisB. That's exactly what I was thinking about. Try it and let us know if it works!

ShashankJain

It's probably easiest just to reference it from the TS webserver. Anything placed in <iw-home>/TeamSite/httpd/iw should be accessible at <yourserver>/iw/myscript.js.

ETA: just read the post linked by ISCBorisB. That's exactly what I was thinking about. Try it and let us know if it works!

Above solution will definitely work, try one more solution of referencing the code from different branch by ../../../../../new_branch/scripts.js