Version: 2.9.0 Reporter: ErwinVanLun —
This is an archived bug report. If you are experiencing a similar issue, upgrade to the latest release and if that does not solve the problem, submit a new bug report
I have a problem with the {relative_url} tag. Since upgrading to 2.9.0 this is not working as it used to.
In my channels the Channel URL fields are all formatted like this:
<a href="https://www.domain.com/name/">https://www.domain.com/name/</a>
The {relative_url} tag used to render on my site as /name/ but not anymore. I have found that {relative_url} is rendered as follows with the following Channel URLs:
1. /name/ => /name (without the trailing slash)
2. http://www.domain.com/name/ => name (no slashes at all)
3. https://www.domain.com/name/ => /www.domain.com/name (when using https it goes completely wrong)
In the documentation at https://ellislab.com/expressionengine/user-guide/add-ons/channel/channel_entries.html#relative-url it says about {relative_url}:
“The URL stored in your Channel URL setting under Channel Management, with the domain information removed. For example, if your setting is http://example.com/index.php/site/index/ the variable will output /index.php/site/index/.”
I use the {relative_url} tag throughout my site in links like this, but they are now broken:
<a href="{relative_url}{url_title}">
According to the documentation when my Channel URL is https://www.domain.com/name/ then this code should render as /name/url_title/ Isn’t that correct?
ExpressionEngine implements Markdown Extra and BBCode. Please see the Markdown Extra docs and the BBCode Wikipedia article for a full reference.
**bold**
, __bold__
, *italics*
, _italics_
, ~strike/del~
, `code()`
bold, italics, strike/del, code()
Link: [link title](https://example.com)
Image: ![alt text](https://example.com/image.jpg)
[blockquote]...[/blockquote]
, [quote]...[/quote]
, and Markdown style:
> Some quoted text. > > This is all one quote.
[code]...[/code]
, and you can also specify the language for syntax highlighting, [code=php]...[/code]
GitHub flavored Markdown code fences are also supported:
``` public function decoderRing($str) { return str_rot13($str); } ```