Connexion
Aricie
Intégrateur de vos solutions d'avenir
Chercher :
Accueil
Expertise
Conseil
Développement
Formation
Hébergement
Portfolio
Produits
Modules DNN
Progiciels
Sur mesure
Télécharger
Support
Actualités
Accueil
Expertise
Conseil
Développement
Formation
Hébergement
Portfolio
Produits
Modules DNN
Progiciels
Sur mesure
Télécharger
Support
Actualités
Support
/
Expert Modules
/
Friendlier URL
/
FUP, Ventrian NewsArticle and print url
DNN Community Forums
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Friendlier URL
FUP, Ventrian NewsArticle and print url
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Sébastien Roeckel
New Member
Posts:
11/06/2013 10:04
Hello
We are currently working on a DotNetNuke web site where we have installed Ventrian NewsArticles and FUP.
We have developped a custom rewriting provider for the Ventrian NewsArticles urls (we needed some specific rewriting rules):
For example the raw url:
http://mysite.com/Default...p;amp;articleId=1063
is rewritten into the friendly url:
http://mysite.com/article..._of_my_article.aspx.
This is working well.
We have added the print link (tag [PRINTLINK]) in the pages displaying the content of Ventrian articles.
For the example given above the url of the print link is:
http://mysite.com/Desktop...7&PortalID=0
which is an absolutely non friendly url
I would like to know how I could develop a rewriting provider for FUP that could rewrite this print url into something more friendly; for example:
http://mysite.com/article...y_article.aspx?print
Technically this seems possible (as all the needed data are present in the raw url) but I would like to know if there is way to tell FUP to apply a custom rewriting provider for urls containing DesktopModules/DnnForge%20-%20NewsArticles/Print.aspx.
Thanks a lot for your help.
Sebastien
Sébastien Roeckel
New Member
Posts:
12/06/2013 09:33
Hello
I have tried to investigate this point a little bit further and I have found that when testing the print link in FUP's test feature, parts of the url are rewritten (according to the rule we have defined for News Articles urls and that is already in place).
It seems that the News Articles module does not convert the print link into a friendly url when rendering this link.
Sebastien
samyb
New Member
Posts:
12/06/2013 10:08
Hello Sebastien,
It's entirely possible that Ventrian doesn't pass the url to the DotNetNuke rewriting framework but rather writes it directly. In this case there is not much that can be done; FUP interacts with urls that are fed into the rewriting pipeline but cannot reach out of the pipeline to change other urls.
Your best bet would be to contact the Ventrian community to see if there are workarounds to the problem: maybe there is another token that is rewritten, or maybe the token system can be used to somehow force the print url into FUP.
Best regards,
Samy
Sébastien Roeckel
New Member
Posts:
12/06/2013 10:32
Hi Samy
Thanks for your answer.
I found a similar case for links inside the content of an article.
For example if in the content of an article there is a link to another article and if behind this link you have the raw url of the article:
- when you hover over this link you will see the raw url (when you hover over other links (in News Articles Latest module for example) you see the friendly url): probably also because the DNN rewriting framework is bypassed in that case
- but when you click on this link you are redirected to the article with the friendly url (because we have enbled option "301 redirects" in FUP)
A solution to this (to see the friendly url when hovering over the links in the content) would be to associate the friendly url to the link. But if doing this you will have broken links if you change the title of an article without refreshing the links in the other articles.
I will try to get in touch with the Ventrian support
Thanks
Sebastien
samyb
New Member
Posts:
12/06/2013 10:43
Well your findings are consistent with the way DNN handles structured content vs free content.
Free content (e.g. the content of a HTML module) is not rewritten, so any url that you write in the HTML module is left as is. Structured content (e.g. the Links module) is rewritten. The "Latest" module sound like a structured content module, hence the rewriting. An article is - of course - a free content module.
If i may suggest a possible solution for the print link, perhaps you could use a small custom skin object that builds the print link from the current url and displays it rewritten; then place it using css and/or js where needed, this way the link will be rewritten, yet look like its originating from the template to the end user.
Best regards,
Samy
You are not authorized to post a reply.