Root Relative Linking not possible?

I'm trying to set up my site so that the links are relative to the Site Root, but it doesn't seem to allow me to do that. I can click on the Site Root button in Local Info, but when I click Save and then go back to it, it has reverted back to Document-relative links. I don't have a Web URL that I can enter in, and I do need to use the root-relative linking (I can go into detail as to why, but I'll save that for now).
Is there something I'm missing that allows me to do that?
I'm using the Mac version of Dreamweaver CC. There was no problem of this sort when I used a PC version of CS6 prior to switching computers.

We are unable to reproduce this issue. @bradthames or MurraySummers, can you please share a video of the issue?

Similar Messages

How to make site root-relative links work in DW and Server both?

See details on buggy DW image link behavior, below. My question is:
1) how to make site root-relative links work in DW and Server both? Or…
2) how to reliably automate the change of several hundred legacy root-relative links of the form
/images/image.jpg to document-relative?
That is, to
../images/image.jpg or
../../images/image.jpg or
../../../images/image.jpg etc…depending on where the directory is.
The old format (/images/image.jpg ) used to work fine in my previous DW 8 configuration but appear grey in DW after “upgrading” to DW cs5.5 mac. (they look fine on the server, but it’s hard to edit image-heavy pages locally when they are all grey).
I tried changing the files to how DW creates root relative links now:
/public_html/images/image.jpg, which is a very easy, attractive root flow since there’s a one-to-one mapping. These look great in DW but are broken on the server!
I looked at the “advanced” site setup, and it looked like it might be possible to nuke the /public_html/ part of my server info…but it also looked like there was the potential for doing damage changing these settings, which are automatically generated from our server connection settings, which seem to work.
The “links relative to document/ site root” toggle…does that change how DW interprets existing links, or just change the default when you are adding a link? I have made 80% of the file links document relative…before wondering if root-relative isn’t better?
It sure seems less ambiguous for all those images if theres a way to make root relative work for DW design view, DW link check, and server.
Summary of buggy behavior: (see test with images here)
"old style" site root link
      /images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: broken (grey w/ broken icon)
      Link check in DW: "external link" (i.e., uncheckable, + file could appear orphaned)
      Browser: good
      Ease of switching: n/a (existing format)
"new style" site root relative link
      /public_html/images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: good
      Link check in DW: good
      Browser: broken
      Ease of switching: easy
Document relative link
      ../../images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: good
      Link check in DW: good
      Browser: good
      Ease of switching: hard (how to automate?)
Absolute link
      http://www.oasisdesign.net/images/img_book/WScover120x150_NEW.jpg
      Design veiw in DW: broken (grey w/ broken icon)
      Link check in DW: external (i.e., uncheckable, + file could appear orphaned)
      Browser: good
      Ease of switching: n/a...not a real option
Thanks!
Similar discussion on "/"

Hello again Jon!
Thanks for jumping on this.
All clear and understood about where publc_html is etc.
No contemplation of nuking the actual public_html directory on the server, just the "/public_html" text string at the start of the DW-generated links.
"/public_html" is automatically added to the front of the link in DW if I create the link with any of the GUI tools, if I have "site root relative" selected. And ""/public_html" ends up in the code, and gets uploaded that way to the server, where it (obviously) doesn't work.
Doesn't sound like it is supposed to work this way. Also, what seems to be the usual root relative format (/images/image.jpg) shows as a broken link in the GUI and an external link in the DW link check. All this togther makes me thinkI have some obscure setting incorrect?
The setting that caught my eye is manage sites/ site setup/ advance settings/ local info/ web url, which is automatically set to http://www.oasisdesign.net/public_html/
it gives an option to change it but it makes every effort to make this NOT look like something users should mess with:
Having gone through the more careful thought process during this post, I'm ready to do the experiment of changing the remote server web URL (why is it wrong by default?)...think I'll eat dinner first so there's 45 min to avert disaster if anyone knows this to be a bad idea!
Art
PS--don't have a local testing server...don't think this will solve the GUI broken link/ link shows as external problems.
Is there an easy, automated way to change links sitewide from document to root relative?

Remote and testing server don't see root relative links the same

My site works fine on my testing server (Apache, MYSQL,
PHP). I use root relative links in a library
file (include file) so that it will work with all pages. For the testing server these links look like this:
/my_sites_root_folder/aaa/bbb/ccc etc.
If I use these same links on the remote server they won't work. To get hem to work I have to change all these links to the form
/aaa/bbb/ccc etc.
When dreamweaver uploads files to the remote server, the site name folder (my_sites_root_folder) doesn't go along for the ride--just the files in it. So on the remote all the site files are stored in htdocs. On my testing server, the files are stored in htdocs/my_site_root_folder.
I think it must have something to do with the way I'm setting up the remote and testing servers, but I'm read a hundred pages of instructions without being able to figure it out. I think I'm just seeing something wrong, but I've already spent days on this. Can someone please point me in the right direction?
I'm using DWCS5. Internet explorer 8, Windows 7.

Thank you for your prompt response. I'm afraid I'm still totally puzzled here. It sounds like you're very knowledeable about your comments, but I would like to know more. I accept that using the local site root in links would be bad, but I'm not clear WHY. Structuring the links as I have doesn't cause any links to break. I've structured them this way because it's the only way I can find that everything works. But I still do not understand WHY I have to do it. Using different libary include files doesn't seem like a good way to go, though
You suggest that if I use any root relative links at all, I need to use vitual hosts. I'm not finding any good coverage of what these are, and especially why they are necessary. If this is the case, does that imply that templates (which use root relative links) also will not work on the test server (at least without vitual hosts)? The conclusion I'm coming up with, given your remarks, is "Dreamweaver doesn't work with root relevant links when you're trying to test a site with a test server." Is this right?

Root-relative links & local testing server

Yesterday I figured out that I'd have to use root-relative links in an included SSI file so that it would work from both templates and pages in my main directory (or other directories, for that matter), e.g., 'src=/image/picture.jpg'. However, since my site is PHP, in order to test the pages or even to use Live View, I have to make use of a "testing server". I did this without much trouble using a package called EasyPHP, which sets up a local web server as well as the PHP module, MySQL support, etc. This all works very well.
The problem is that, in order to support several web sites, I have to use a "virtual directory" spec to direct the web server to the correct location for my site's files. In the setup for the testing server, I therefore have to specify a URL prefix such as 'http://localhost/corinthian' for this particular site. That has worked previously, but breaks when using root-relative links since the server sees the "root" as being the main "localhost" directory instead of "localhost/corinthian". So now my SSI doesn't display correctly because it's not being resolved to the correct directories.
I don't think that this is fixable unless someone else has run into it and can think of some gimmick I could try. Anyone? Breaking out some of my code into an SSI has definitely been more of a challenge than I expected!

I use 1&1 Internet as my hosting service. They apparently have my site set up in a virtual directory / virtual host fashion. Going to http://corinthian241.org, the root directory for root-relative links would have to be the directory pointed to by the URL. However, running phpinfo.php on the site shows the following result for $_SERVER['DOCUMENT_ROOT']: '/kunden/homepages/29/d246935068/htdocs/corinthian'.
So I'm pretty sure that a link from a page in my site home directory using this as a prefix would definitely not work, since the first "/" implies starting in the "corinthian" subdirectory -- not the real root of the server itself. Correct?
Doug

Undesired Root Relative Link

Document relative link changes to root relative link in new documents created from a template. When saving changes to the template, this link changes back to document relative in the new document. The link points to the content source for an iframe.
What will I have to do to make this link remain a document relative link? Making and undoing a change to the template and re-saving it every time a new document is created constitutes a workflow problem. It also unnecessarily updates all other existing documents based on that template and uploads all of them to the server during synchronization.
I looked through the preferences and couldn't find anything that I might have accidentally changed to cause this phenomenon.

Ah - that's not a root relative link, it's a file:/// link (I don't think there is any name for it), and it's definitely wrong if you are finding it in a file that you have SAVED. But it's how all links in a newly created child page will look BEFORE IT'S SAVED. Once you have saved the file within the site, then DW can manage the links so that they reflect the location where you saved the file.
I do that because the links in the header's navigation change whenever new content is added to a category and the current content moves to the archive. So far I changed the links in the basic template and re-uploaded all the child pages. That's getting a little too much already, so I want to have to update only a single file with the header that the iframes in the uploaded pages are already linked to.
Good golly man, use Server-side includes, not IFrames! This kind of this is exactly what SSI is for.
Not all child pages are at the same level. Most are just one folder down from the top, others are two and even three folders down. That's why proper updating is important. I may stick with the absolute URL.
You must use real ROOT relative links in the include files - then all things will work. With a root relative link it doesn't matter where the page carrying the link is located within the site.

Relative links not working in Safari

Our web site has many PDFs and aspx files that link to each other. In a PDF, when we click on a relative link, the following message appears: Safari can't open "filename.pdf" because the first character of its address is not valid. When we loook in the error console for the page with the link, the warning says "Resource interpreted as Document but transferred with MIME type application/pdf." Our workaround has been to set up Safari to use Adobe Reader to open the PDFs, and everything worked just fine. With Safari 5.1, that is not possible, so we now need to figure out what the problem is. Thanks for any help you can offer.

With Safari 5.1, that is not possible
Read here > Apple Safari 5.1 and Adobe Reader/Acrobat Advisory

Template updates links not correctly

Dreamweaver CS3 for Mac:
I had to add the following into my already existing sitewide
template file:

but unfortunately links that are more than one level deep do
not update correctly on my HTML pages.
Is there a way to make this work?
Martin

>Ok, it seems that Dreamweaver is overstrained by altering
template links within conditional statements.
>Thats very sad, if this group is read by Adobe people
please fix this before Dreamweaver CS4!
>I prefer clean HTML files but it seems the only solution
is to bloat each and every file with browser specific CSS or
scripts
You are wrong - it is not a DW bug. The link to the
stylesheet has to be either relative to the root of the website
(href="/xxx" notation) or relative to the page (href="../xxx"
notation) NOT the template. You may not see this in the design view
of DW depending on what version you are using and how you have set
DW up to include links (See options/preferences).
If you have multiple levels of pages, then you HAVE to use
root relative links - that is the way of the web, it is not a DW
problem.
If you want to see the correct result in Design view, you may
have to use 'Design time stylesheets' : Look up the term in DW
help.
s

Root relative images and design view

I have many sites that have root relative image paths
(src="\images\sample.gif") that I've coded by hand in DW8.
I don't use design view that much, buy one of our designers
does. The problem is none of the images with root-relative paths
will appear in design view.
I have specified valid paths in my site definitions, so
what's the issue?

> I have specified valid paths in my site definitions, so
what's the issue?
Hard to say - perhaps the developer's site is not properly
defined. There
should be no issue displaying root relative linked images in
DW's Design
view, since DW knows where the root of the site is. What is
in the HTTP
address field of the local site definition?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Diodeus" <[email protected]> wrote in
message
news:g91jhj$imv$[email protected]..
>I have many sites that have root relative image paths
> (src="\images\sample.gif") that I've coded by hand in
DW8.
>
> I don't use design view that much, buy one of our
designers does. The
> problem
> is none of the images with root-relative paths will
appear in design view.
>
> I have specified valid paths in my site definitions, so
what's the issue?
>

Link to site-root relative style sheet not working CS4

I am trying to define links to site-root relative external style sheets - as I believe that IE conditional comments prevent Templates from correctly updating the links. The styles are not being applied when I use any href path begining with "/". So, the following do not work:
<link href="/styles/myStyleSheet.css" rel="stylesheet" type="text/css" />
<link href="/myStyleSheet.css" rel="stylesheet" type="text/css" />
Dreamweaver can open the css file from a right-mouse click and even give me warnings about css properties as a tool-tip as I hover over the file. The styles are applied fine with document relative paths:
<link href="../myStyleSheet.css" rel="stylesheet" type="text/css" />
Any ideas?
Jeff

Close your meta tag.
<meta name="description" content="blah, blah, blah...>
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb

Relative Links and Microsoft IIS not working, why?

I've searched high and low for the solution to this problem
and no one seems to give a definite answer.
I have a typical home server set up using Microsoft IIS on
Windows 2000 as a test server for websites.
The typical folder structure of the IIS is Inetpub >
wwwroot > content
Since I am working on multiple websites at a single time I
place my websites as such Inetpub > wwwroot > websiteFolder1
with multiple websites under wwwroot
Now I setup the dreamweaver sites with the root directory as
websiteFolder1 but when I go to use relative links, dreamweaver is
looking at the wwwroot level instead and the relative links won't
work. So incase that seems hard to understand when I have a css
file that is in Inetpub > wwwroot > websiteFolder1 >
library and I want to relatively link to it, dreamweaver is instead
of seeing websiteFolder1 as the main, it is starting with wwwroot
and that makes the file not found.
How do I get the relative links to see the folder under
wwwroot as the root directory instead of wwwroot?
Thanks Much!

You would have to set up virtual sites in your IIS
installation. Google
that term, and I'm sure you will find lots....
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Visionology" <[email protected]> wrote in
message
news:ee18ce$jej$[email protected]..
> I've searched high and low for the solution to this
problem and no one
> seems to
> give a definite answer.
>
> I have a typical home server set up using Microsoft IIS
on Windows 2000 as
> a
> test server for websites.
>
> The typical folder structure of the IIS is Inetpub >
wwwroot > content
> Since I am working on multiple websites at a single time
I place my
> websites
> as such Inetpub > wwwroot > websiteFolder1 with
multiple websites under
> wwwroot
>
> Now I setup the dreamweaver sites with the root
directory as
> websiteFolder1
> but when I go to use relative links, dreamweaver is
looking at the wwwroot
> level instead and the relative links won't work. So
incase that seems
> hard to
> understand when I have a css file that is in Inetpub
> wwwroot >
> websiteFolder1 > library and I want to relatively
link to it, dreamweaver
> is
> instead of seeing websiteFolder1 as the main, it is
starting with wwwroot
> and
> that makes the file not found.
>
> How do I get the relative links to see the folder under
wwwroot as the
> root
> directory instead of wwwroot?
>
> Thanks Much!
>

Settlement of planned deliv. costs not possible if GR-related data entered

Hi gurus,
While doing T-code MRRL if i am entering the GR posting date and ticking the good + delivery check box an error message is trigerd 'Settlement of planned deliv. costs not possible if GR-related data entered'.PLZ reply the reson for this error.

I Have the same problem them I realise that :
This message just appear if i am using doc. selection = 4 .
tks
Teresinha

I have install last update for i pod(ios5) but during installation there was one problem....i have restore my ipod and now i have lost all my buyed music!!Is not possible download it....?What are the details, including any error messages, related to your

I have install last update for i pod(ios5) but during installation there was one problem....i have restore my ipod and now i have lost all my buyed music!!Is not possible download it....?What are the details, including any error messages, related to your question?

Have you not got the music on your computer and/or on backups on, for example, external drives or CDs/DVDs ?

New From Template Changes Relative Links to Local Root?

Thank you for taking the time to read and understand my plight with Dreamweaver CS3 for Mac. I apologize for the lengthy question, but in the effort to provide detail I shall go. First the background:
I'm updating, editing, and appending an existing site that was previously created with Dreamweaver.
I'm new to Dreamweaver but have a pretty good understanding of things
I created a new site on the local drive on my MacBook Pro and then downloaded the entire site via FTP (live site: domain.com)
I then replicated the site and exact file structure using FTP to a staging server (staging.domain.com)
There are three existing .dwt templates. I've successfully updated the template file and auto updated all other pages that were based on this template.
But my problem comes from creating new pages FROM the template. It appears that while the .dwt template file shows relative links (../xxxx) in the code, when create a new file from the template the url of these links is replaced by the path to the file on my local drive... I want non of this (.../xxxx) is fine.
What is happening is that a javascript drop down menu is disappearing when I create new from template. I am assuming it's because of the path changes.
This is the ORIGINAL (good) code from the .dwt:

<tr>
 <td height="31">
 <table width="718" border="0" cellpadding="0" cellspacing="0">
 <tr>
 <td width="24"><img src="../images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
 <td width="342" style="background-image: url(../images/Header-BG.gif);"><img src="../images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
But when I create a NEW page from the above template the code is changed to the local path:

<tr>
 <td height="31">
 <table width="718" border="0" cellpadding="0" cellspacing="0">
 <tr>
 <td width="24"><img src="file:///Grasshopper/Users/allan/Documents/clients/site/site staging master/images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
 <td width="342" style="background-image: url(file:///Grasshopper/Users/allan/Documents/clients/site/site staging master/images/Header-BG.gif);"><img src="file:///Grasshopper/Users/allan/Documents/clients/site/site staging master/images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
To be sure all links in the template file are changed too.
This is the .dwt file itself
This is a random page created from the above template.
And this page was created by simply altering the .dwt template file linked above and then SAVING AS. You can see the relative links remained and the navigation bar looks and operates as normal.
To provide easier visual reference I offer the following:
This is the .dwt file when opened in dreamweaver:
Note the black area where the javascript drop down menu is in the top navigation when the page is correct:
But when I create a NEW page from template this is what I get in the top navigation bar:
And then this is what it looks like when posted:
Ultimately what I'm trying to do is:
1) work on site files on my local drive
2) sync the local drive with staging.domain.com so my client can proof and approve
3) sync to the actual live site at domain.com
I assume I could simply do this by changing the ftp info and given the site structure and all files are same and ideally all links are relative this should be accomplished easily.
Though perhaps my problem stems from the fact my local site is buried several layers deep on my local drive Local Drive/Users/Me/Clients/Client.... etc... but I haven't checked this yet.

Great... Thanks for your patience....
Here are links to all questioned files on the staging server:
This is the .dwt file itself
This is a random page created from the above template that shows the image/navigation incorrect.
And this page was created by simply altering the .dwt template file linked above and then SAVING AS. You can see the relative links remained and the navigation bar looks and operates as normal. (obviously the wrong thing to do.
And this page is one that was created prior to my working on the site and was based on the subpage template and displays correctly.
Now bear with me here as I notice this behavour too.
In the code snipped taken directly from the DW .dwt template (linked above)
<td width="24"><img src="../images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
 <td width="342" style="background-image: url(../images/Header-BG.gif);"><img src="../images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
you'll notice there are two images L-Header-Corner.gif and one that is Header.BG.gif.
The difference here is that the BG gif has a style attributed to it "Background-Image) which is followed by some strange code that says (url)../
Opening that file Background Image and it's a tiny slice of what I think is part of the entire missing gray bar:
In a page that displays correctly the code looks like this:
<td width="24"><img src="../images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
 <td width="342" style="background-image: url(../images/Header-BG.gif);"><img src="../images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
And in a page that is displaying incorrectly the code appears like this:
<td width="24"><img src="../images/L-Header-Corner.gif" width="30" height="50" border="0"></td>
 <td width="342" style="background-image: url(file:///Grasshopper/Users/allan/Documents/clients/koolfog/koolfog website staging/images/Header-BG.gif);"><img src="../images/spacer.gif" alt="" width="337" height="1" border="0"> </td>
So you can see that the link in this case (with the URL and style) has actually been converted to a site (my hard drive) relative link when saving.
So the pressing question stands: Why doesn't dreamweaver convert that URL link when saving a page created from a template back to the same directory?
Also, it appears that in that .DWT all the links have the leading periods and therefore are document relative... since I didn't set this up, how do you think this happened?

After new update we can not keep the "related links" off the screen. We uncheck it but it still keeps coming back.

Every time we start Firefox, the "related links" are on the screen. We uncheck the box and it goes away. But the next time we use it, the related links are back. I cannot see why we would have to reset this every time we use the program. It is not a serious thing but surely is aggravating.

You can also do a malware check with some malware scanning programs on the Windows computer. 
Please scan with all programs because each program detects different malware. 
All these programs have free versions.
Make sure that you update each program to get the latest version of their databases before doing a scan.
*Malwarebytes' Anti-Malware: http://www.malwarebytes.org/mbam.php
*AdwCleaner: http://www.bleepingcomputer.com/download/adwcleaner/ http://www.softpedia.com/get/Antivirus/Removal-Tools/AdwCleaner.shtml
*SuperAntispyware: http://www.superantispyware.com/
*Microsoft Safety Scanner: http://www.microsoft.com/security/scanner/en-us/default.aspx
*Windows Defender: Home Page: http://www.microsoft.com/windows/products/winfamily/defender/default.mspx
*Spybot Search & Destroy: http://www.safer-networking.org/en/index.html
*Kasperky Free Security Scan: http://www.kaspersky.com/security-scan
You can also do a check for a rootkit infection with TDSSKiller.
*Anti-rootkit utility TDSSKiller: http://support.kaspersky.com/5350?el=88446
See also:
*"Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked

Posting is not possible for the specified company code.

Hi SRM Gurus,
We have a four company codes in our org.structure and if we try to post manual invoice for a particular company code with its currency, we are getting this error :
"Posting is not possible for the specified company code "
We have all company codes defined and inherited for the particular user in BUK and we get all the company codes in the F4 help of this user in BBPIV02 -->Basic data.
Any suggestions pl.
I doubt this particular Cocode is deactivated for invoice posting in backend. Is it possible ?
Kindly suggest.
Reg.,
Sridhar.

Hi
Which SRM version are you using ?
Are you getting this error for a praticular company code only or for all the comapny codes ?
Please read this ->
Since you are trying to create Invoice with PO did you check the Vendor Root there is a attribute for company code. Please maintain the same, if not maintained.
Refer the link below for details.
Re: Company code for system missing in user attributes
Other related links ->
Try to change the chart of acct info in OBY6 for a company code that was copied from SAP template, there is no Financial posting or any other posting in this company code.
Re: Posting Period Error in Confirmation
Hope this will help.
Regards
- Atul

Root Relative Linking not possible?

Similar Messages

Maybe you are looking for