Page 1 of 1
Internal Page Link uses own alias? no!
Posted: Mon May 17, 2010 12:34 pm
by nicmare
Hi there,
i use cmsms 1.7.1 with pretty urls and i have some pages and one internal page link.
i want the link to use the same alias like the target page. but for some reason i have to specify an alias in the options tab? when i try to use the same alias, i get an errormessage, of course.
is this a bug?
Re: Internal Page Link uses own alias? no!
Posted: Sat May 22, 2010 7:30 pm
by Rolf
nicmare wrote:
i want the link to use the same alias like the target page. but for some reason i have to specify an alias in the options tab?
I am not totaly shure I understand your question

but could you check this setting in the config.php in the first place:
Code: Select all
#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;
Grtz. RolfÂ

Re: Internal Page Link uses own alias? no!
Posted: Sun May 23, 2010 1:09 am
by Peciura
when i try to use the same alias
Alias is another form of page id - it is ment to be unique.
Re: Internal Page Link uses own alias? no!
Posted: Sun May 23, 2010 9:43 am
by RonnyK
nicmare,
why would you like to use the same alias? The page that will show as a link, and in the URL, will be the page linked to. So that pages alias will be visible, only in the backend the link-pages-alias will show.
Ronny
Re: Internal Page Link uses own alias? no!
Posted: Sun May 23, 2010 2:43 pm
by gdur
If this is about linking to an Anchor within the same page I think nicmare might be right. Just did a new page a couple of days ago using version 1.7.1 and I failed to link within the page a few times doing it the way I was used to. I had to create the link like ?page=pagealias/#anchorname. This worked for me but I do not remember how it was before but to my memory different.
Now if you select the anchor from the anchors box the anchorname appears in the Link URL box with a # in front. If you leave it like that it's a dead link so you have to edit the Link URL manually and put ?page=pagealias/ in front of the anchor name. What I remember from working with 1.66 it went more intuitive but too much trouble to downgrade to investigate....