Go 4 Sharepoint

Search:

Welcome: Guest!

Sharepoint Forum

Home » Forum » Sharepoint

Ask a question

RSS Feeds

Content Editor Webpart - Relative Urls

Asked By: Dana Barnes Date: Sep 22, 2007 Category: Sharepoint Views: 1556

In Share Point, i am using CEWP to add content. if i put
relative urls through Rich Text Editor, after i save the content and
again open it, it changes to absolute url.

i have two environments, Production and Development. Both on
different systems.

in Development environment, i am giving relative url, due to the
problem of above, in my production environment i am getting the wrong
urls(due to absolute urls..). so site is not usable any more......

it's the big problem...
is there any way other than the CEWP.
please help me out..
i completed all my site, due to this, i stopped to push into
production.

Tagged:content editor webpart relative urls

8 Answers Found

Answer #1 Answered By: Ruth George Answered On: Sep 22, 2007

These guys had the same problem. Here’s what they did:

“We had to switch out the CEWPs and use Publishing Control RichHTML fields
instead. These fields “fix-up” absolute URLs back to relative URLs when
content is published. There were a few places where we need to keep the CEWP
because we wanted Input tags that the RichHTML field did not support.
Unfortunately, in these cases, we had to fix-up the URLs by hand via the
Source Code editor in the CEWP.”

Full article at:
blogs.msdn.com/.../how-we-did-it-mission-cr
itical-hawaiianair-com-website-powered-by-moss-2007.aspx

Answer #2 Answered By: Peter Peterson Answered On: Sep 22, 2007

One limitation though of the Publishing Control RichHTML field to
be aware of is that it strips out any embed tags. The CEWP does not (nor
does the free Telerik editor). A quick test of the Telerik editor shows that
it too converts relative urls to absolute. So much for that alternative.

Answer #3 Answered By: Kalyan Pujari Answered On: Sep 22, 2007

their design point for the free editor was to emulate the
Microsoft editor, including what some might see as its shortcomings. The
commercial version of their editor is supposed to be enhanced beyond the
Microsoft offering; maybe it has different (or switchable) behavior.

Answer #4 Answered By: Isidro Berger Answered On: Sep 22, 2007

As the last line indicated, one can always go to the Souce Code Editor and
fix them by hand.

Wish there was a better solution...

Answer #5 Answered By: Schuyler Le Answered On: Sep 22, 2007

I think there are properties in SharePoint Designer you can set so
RichHTML fields don't strip tags.

Answer #6 Answered By: Kristina Cox Answered On: Sep 22, 2007

The biggest problem with RichHTML fields is that they only work on
Publishing sites.

Answer #7 Answered By: Delbert Frederick Answered On: Sep 22, 2007

Can you make a custom site definition that includes the
Publishing:RichText tag, or whatever that needs to happen to enable it
within a different type of site?

Answer #8 Answered By: Willard Valenzuela Answered On: Sep 22, 2007

As an alternative to completely changing out of CEWP's try removing the
http://[server <http://[server> ] from the url in the source code. I
couldn't get it to stick in the RTE, just in the Source Code editor.
Though you will be stuck with the same managed path structure in
production that you established in development, so think carefully.
Also I have found that no matter how you try to establish a partially
relative reference in a Wiki SharePoint changes it into an absolute URL
without fail.

Didn't find what you were looking for? Find more on Content Editor Webpart - Relative Urls Or get search suggestion and latest updates.