- Posts: 9
- Thank you received: 0
Problem with URL / SH404
- extensrep
- Topic Author
- Offline
- New Member
Less
More
9 years 3 weeks ago #2341
by extensrep
Problem with URL / SH404 was created by extensrep
I have upgraded to Joomla 3.4 and thus from CP 2 to CP3.1.13.
I realize now that I have problems with CP tags urls. I use SH404 for SEF urls, that I upgraded too.
The tags URL have changed from tag/tag_name.html to tag/field_name-tag_name.html. The URL settings have not changed, still on "Name".
Is it due to SH404 ? or to the new version of CP ? Can I do something to come back to the previous URL format ?
I have an other issues with tag that have many pages. Previously the URL were like this : tag/tag_name/page-2.html
and now they are like this : tag/field_name-tag_name.html?lang=fr&limit=20&start=20
Many thanks for your help
Marina
I realize now that I have problems with CP tags urls. I use SH404 for SEF urls, that I upgraded too.
The tags URL have changed from tag/tag_name.html to tag/field_name-tag_name.html. The URL settings have not changed, still on "Name".
Is it due to SH404 ? or to the new version of CP ? Can I do something to come back to the previous URL format ?
I have an other issues with tag that have many pages. Previously the URL were like this : tag/tag_name/page-2.html
and now they are like this : tag/field_name-tag_name.html?lang=fr&limit=20&start=20
Many thanks for your help
Marina
Please Log in or Create an account to join the conversation.
- andrea_4g
- Offline
- Administrator
Less
More
- Posts: 1122
- Thank you received: 163
9 years 3 weeks ago - 9 years 3 weeks ago #2342
by andrea_4g
Replied by andrea_4g on topic Problem with URL / SH404
You can still change the URL format with the relevant parameter (Results Formatting > URL format) in Custom Properties main configuration.
I don't know if SH404 processes the URLS differently, however, if I recall correctly, there should be a way to selectively disable SH404 from processing CP urls and let native Joomla SEF do that, in case o trouble.
Pagination links should render and work just like previuos versions of CP.
I don't know if SH404 processes the URLS differently, however, if I recall correctly, there should be a way to selectively disable SH404 from processing CP urls and let native Joomla SEF do that, in case o trouble.
Pagination links should render and work just like previuos versions of CP.
Last edit: 9 years 3 weeks ago by andrea_4g. Reason: typos
Please Log in or Create an account to join the conversation.
- extensrep
- Topic Author
- Offline
- New Member
Less
More
- Posts: 9
- Thank you received: 0
9 years 3 weeks ago #2343
by extensrep
Replied by extensrep on topic Problem with URL / SH404
Thank you for your answer Andrea.
By relevant parameter, you mean that the format I have now is due to the configuration of Custom Properties ? What parameter should I choose to get my former format back ?
By relevant parameter, you mean that the format I have now is due to the configuration of Custom Properties ? What parameter should I choose to get my former format back ?
Please Log in or Create an account to join the conversation.
- andrea_4g
- Offline
- Administrator
Less
More
- Posts: 1122
- Thank you received: 163
9 years 3 weeks ago #2344
by andrea_4g
Replied by andrea_4g on topic Problem with URL / SH404
CP Tags may have 3 different formats:
1) Tag ID: (TagID=numeric) is language independent, but less SEF.
2) Tag Name: uses the field and value names to create URLS (TagName=field_name:field_value).This one is regarded as the more SEF.
3) Tag Label: uses the labels instead, thus allowing non latin chars in URL (TagName=FieldLabel:FieldValue)
In case 2) and 3) CP Tags are always expressed as field_name:field_value (or field_label:value_label) in order to discriminate tags such us the following example:
shirt => [red, green, blue]
socks => [red, green, blue]
Under this circumstance, if tags were made only by their values (red, green, blue), CP would not been able to tell which tag group they were referring to (red socks or red shirts ?)
Therefore I believe that the URL format you had (tag/tag_name) was a product of SH404 processing.
In other words, there's no configuration in Custom Properties to format tag URLS that way.
1) Tag ID: (TagID=numeric) is language independent, but less SEF.
2) Tag Name: uses the field and value names to create URLS (TagName=field_name:field_value).This one is regarded as the more SEF.
3) Tag Label: uses the labels instead, thus allowing non latin chars in URL (TagName=FieldLabel:FieldValue)
In case 2) and 3) CP Tags are always expressed as field_name:field_value (or field_label:value_label) in order to discriminate tags such us the following example:
shirt => [red, green, blue]
socks => [red, green, blue]
Under this circumstance, if tags were made only by their values (red, green, blue), CP would not been able to tell which tag group they were referring to (red socks or red shirts ?)
Therefore I believe that the URL format you had (tag/tag_name) was a product of SH404 processing.
In other words, there's no configuration in Custom Properties to format tag URLS that way.
The following user(s) said Thank You: marremp
Please Log in or Create an account to join the conversation.
- marremp
- Offline
- New Member
Less
More
- Posts: 4
- Thank you received: 0
9 years 3 weeks ago #2345
by marremp
Replied by marremp on topic Problem with URL / SH404
Thanks a lot for this very clear explanation.
It should have come from SH404 indeed. I am going to perform individual redirections.
Marina
It should have come from SH404 indeed. I am going to perform individual redirections.
Marina
Please Log in or Create an account to join the conversation.
Time to create page: 0.175 seconds