 |
|
|
 |
Joined: 3/22/2008
Posts: 115
|
|
|
Déclic Vidéo FX wrote
My Greeting page have been changed this way (not the way you described):
3. Click the 'Add New Url' button, and in the new Url that is created, type in 'bonjour'
4. Set the Http Status to '302-Redirect' for the new Url
5. Click the 'Add New Url' button, and in the new Url that is created, type in 'hello'
6. Set the Http Status to '302-Redirect' for the new Url
When I click on the "bonjour page in french", I get language/fr-FR/greeting.aspx
When I click on the "hello page in english", I get language/us-US/greeting.aspx
That's perfect. But... If you look to the breadcrumb, it is language/us-US/hello.aspx and language/fr-FR/bonjour.aspx
So, I am wondering if it is SEO or not... Is it a good thing to have two URL pointing on the same page ?
In our case
language/fr-FR/greeting.aspx is the same than language/fr-FR/bonjour.aspx
and language/us-US/greeting.aspx is the same than language/us-US/hello.aspx
What is your opinion ?? Maybe should I do a 301-permanent redirect ???
Bruce, this problem is SOLVED !
I did not read carefully what you wrote. I usually read carefully and start testing. I should have missed something, because at first when I tried to put 200-OK for the 2 pages indicated, it did not accept a 200-OK for 2 pages (but only one was taken into accout), that's why I choose the solution I explained (which is bad)...
When reading your post again, and making a new test, if I strictly follow your way of doing, it WORKS PERFECTLY !!!! (should have TWO pages with 200-ok)
So, I have a solution which is working perfectly for this point. I am very happy !! I can migrate to 4.8.2 as soon as we have solved the problem of dual language with Google SiteMap. I will let you know when it is alive, so you can see and test it dual language. I will then later on do a specifi page explaining how I done, because I often have people asking me how to do this. ;-)
DV FX
|
|
|
|
 | |
|
|
|
Joined: 3/22/2008
Posts: 115
|
|
|
Dear Bruce,
I was too enthusiastic when trying... I forget child page (when using ADMIN > PAGE URLS).
And in this case, it does not work and we have an error like this:
A critical error has occurred.
Cannot insert the value NULL into column 'Url', table 'mytable.dbo.ifty_TabRedirect'; column does not allow nulls. INSERT fails. Error in ifty_AddTabRedirect. Stmt No.=1, Db=mytable,Err=515 The statement has been terminated.
For information, see what I am trying to add:
Any idea ???
DV FX
|
|
|
|
| |
|
|
|
Joined: 3/9/2006
Posts: 3292
|
|
|
I have had a similar error reported where a Url was left blank, and therefore tried to save a null value to the database. I've got it down as a bug to prevent 'blank' urls being saved. The blank url is probably not on the page you are looking at - it could be in any of the pages. The system stores up all the changes you have made and writes them out to the database once you click the 'apply changes'. This is why you can get an error even when the current page you are looking at seems normal.
To get around this, you'll probably have to 'discard changes' to dump the changes from the memory, and start again, unless you can find which page you have the blank Url.
As a side note, you have saved 'Tutorials, Tips & Tricks' as a Url name - you can see the encoded result. You should, instead, be using something like 'Tutorials-Tips-and-Tricks' for your Url. The idea with replacing Urls is to create something that isn't encoded, so that it looks better. The module won't stop you from saving an encoded-version, it just warns you what it will look like.
|
|
|
|
| |
|
|
|
Joined: 3/22/2008
Posts: 115
|
|
|
Bruce Chapman wrote
{...}
To get around this, you'll probably have to 'discard changes' to dump the changes from the memory, and start again, unless you can find which page you have the blank Url.
{...}
That's what I done, and it is not linked to any empty or null value. The error is occuring with this two specific values. If I modify them, it works. But I have understood where was the problem. I assume that your module is interacting with Locopon DSLocalistor more than we think (somewhere with the name of pages). DSLocalistor was disabled when I applied the settings. In such case, it creates the error I reported. Once DSLocalistor is enabled, I tried again (with exactly the same values), and no more errors. I tried many times to be sure that it was DSLocalisator which was interacting, and it is the case, I am 100% sure.
As for the "strange" URL with encoded character, this is something mandatory, as we already discussed together that we must use 200-OK for both translation (french and english). If I change it to "Tutorials-Tips-and-Tricks", then I have to rename my page like "Tutorials-Tips-and-Tricks" and it will appear like that in the menu, something I would like to avoid...
For the moment, I have migrated to DNN 4.8.2 and URLMaster, and I am still having some question/difficulties with that. I will make intensive test and reporting what should be the final setting to have a correct behavior. I admit that I have not understood how it works this 200-OK, I do not understand why you can have TWO 200-OK ??? Can you explain a little bit more, maybe it will help me to pinpoint the problem.
DV FX
|
|
|
|
| |
|
|
|
Joined: 3/9/2006
Posts: 3292
|
|
|
Déclic Vidéo FX wrote
As for the "strange" URL with encoded character, this is something mandatory, as we already discussed together that we must use 200-OK for both translation (french and english). If I change it to "Tutorials-Tips-and-Tricks", then I have to rename my page like "Tutorials-Tips-and-Tricks" and it will appear like that in the menu, something I would like to avoid...
Yes, I see the problem. That's a tough one then.
I admit that I have not understood how it works this 200-OK, I do not understand why you can have TWO 200-OK ??? Can you explain a little bit more, maybe it will help me to pinpoint the problem.
You can have as many 200-OK pages as you like, any page with a 200-OK setting will respond to the requested Url with no redirection. However, when the Module is generating the Friendly Url for use in internal site links, it will choose only one of the 200-OK urls to use. This is the first one in the list of Urls marked with 200-OK. This behaviour is how the module can work with the locopon module. The Locopon module replaces the tab name with a localised version (say, 'localised-page-name') - which is then passed into the Url Module to generate as a Friendly Url. Because it works by default on the page name, if comes out with 'localised-page-name.aspx'
Now, generating a Friendly Url is all well and good, but you must then have a Url Rewriter that can understand the new page name. This where having two pages with 200-OK on them comes in. Having two custom Urls means that the underlying page can respond to either Url. And because the Locopon module generates two (or more) different Urls - onw for each language installed, you need to set up a match for those localised-name based Urls.
I know it's confusing, I have to read back through my notes to re-understand it.
I'll try another way.
Normally, with a DNN page, the Friendly Url Provider (whether standard or Url Master) generates the Url based on the page name, so you end up with this : mypagename.aspx. When you install the locopon dslocalizator module, it fudges the way DNN works and replaces the page name, so that when you get the Friendly URl Provider to generate it, it comes out with a new name. However, the dslocalizator doesn't have a Url rewriter in it, so DNN can't re-interpret that page name when the page is requested. The reason is that in the old days of DNN before Human Friendly Urls, you could have any old value you liked for the tab name - it was the /tabid/36/ path that was used to identify which tab was requested. domain.com/pink-elephants/tabid/36/home.aspx and domain.com/home/tabid/36/default.aspx return the same value. What the Url Master module does is allow you to define a matching localised Url to the localised page name that dslocalizator generates, and then DNN can parse the incoming Url requested, and send back the correct page.
HTH
|
|
|
|
| |