RICHACT
Registered Users
Nuke Newbie
Posts:4
 |
| 11/08/2007 7:09 PM |
|
Scott,
Can you tell us how much (if any) of the work that BruceChapman did in this thread was included in 4.7 http://www.ventrian.com/Support/ProductForums/tabid/118/forumid/35/postid/23277/view/topic/Default.aspx ?
Specifically, we're wondering if the hypens, 301 redirect, and the other items below are included... If they are not included, how much closer are we to getting this done... Also, if there is anything we can do to help, please advise. These changes really need to be in DNN out of the box.
Thanks,
Rich
_________________
Here's a list of all the things that this version can do:
- Url's are generated as friendly Urls by all code which uses the standard NavigateUrl() call in DotNetNuke.
- Choice of page extension - .aspx or any other extension (such as .page)
- Choice of using page extensions - options are "always", "never", "pageOnly". Always and never are self-explanatory, pageonly means only use an extension when the Url is for a page that contains no query parameters.
- 301 redirects for 'unfriendly' page requests. This can be on or off.
- 301 redirects to home page for deleted and expired pages
- A regex filter can be implemented to restrict 301 redirects for matching Urls
- Individual pages can be restricted from 301 redirects by placing in a delimited list
- Choice of two ways of handling parameters/query strings - ordered, in which the values are shown as consecutive levels in a path (key1/value1/key2/value2) and "firstparmlast" in which the first key value is placed last (value1/key2/value2/key2).
- Choice of detecting duplicate portal alias/page path combinations. It is possible to have portal1/test as a page, and a portal which has portal1/test as an alias, thus duplicating the same path on a single DNN install.
More information and the download files are on my blog at :
http://www.ifinity.com.au/Blog/TechnicalBlog/tabid/60/EntryID/24/Default.aspx
To see it working, have a look at http://www.auctionlink.com.au/TagList/Tag/Valuers/
(I haven't installed it on ifinity.com.au because it runs on shared hosting)
Please note that it is still under development, and further work will be done to include Scott's changes with mine to
|
|
|
|
|
bchapman
Registered Users
Nuke Super Newbie
Posts:21
|
| 11/21/2007 3:06 PM |
|
Rich
I can answer that for you - I don't think any of the changes I had developed are included in the 4.7 version. You never know what will happen in the future, but for the moment the work I have done exists only in my version. You're quite welcome to use my version, the one I am using now seems quite stable, I've fixed a few bugs that people have reported. Currently people are telling me there is a 4.7 compatibility bug (which is why I'm on the Ventrian forums, looking for an answer). I should have this fixed pretty soon though.
-Bruce |
|
iFinity DotNetNuke Modules |
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:11937
|
| 11/21/2007 3:39 PM |
|
What is a compatibility bug? I had a limited time to implement some of the changes, so, yes, some of the changes didn't get in.
How does your provider work with child portals bruce? |
|
Scott McCulloch
Site Administrator |
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:11937
|
| 11/21/2007 3:40 PM |
|
| One more thing, where did you make the changes Bruce - and how did it affect the host settings page if it was a custom namespace in 4.6 +? |
|
Scott McCulloch
Site Administrator |
|
|
bchapman
Registered Users
Nuke Super Newbie
Posts:21
|
| 11/21/2007 3:59 PM |
|
Hi Scott
compatibility bug...err that's probably bad terminology on my part. I think it's the same thing that you found with the 4.6+ version - a namespace clash with the Config section. I haven't got an install of 4.7 yet to try it out on, but I've looked at what you did to fix the problem and I'm just compiling a new version in my own namespace to see if it solves the problem. I'll send it to the people who have reported a problem and see if it works OK. I think that's what you are talking about with the host settings page and 404 errors.
On the question of what gets integrated, I'm totally easy and completely understand time pressures. Personally I think all the changes added into my version would be a bit much to put in a single release, it could easily create a lot of support traffic.
I've added a couple more features from user requests since I last posted on these forums - one is to force all Url's into the same (lower) case using a 301 redirect, and the other is to force to a single subdomain (ie either force the 'www.yoursite.com' or 'yoursite.com'). I believe this is installed at zymmetrical.com - if you enter Zymmetrical.com it out it redirects using a 301 to www.zymmetrical.com. I haven't bothered setting this up with any of my own sites as I don't think it is that big a deal personally.
As for child portals, I've set it up so that as long as you don't have a tab name/portal name collision, it should work fine with Child portals. I use the dictionary tab lookup, but instead of delimiting each piece of the url with '/', the portal path/tab name is separated with '::' in the dictionary. Doing this allows the code to determine what is the portal alias and what is the tab path.
Ie the dictionary keys look like:
- parent:tab1 - tab1 in parent portal
- parent:tab1/tab2 - tab2 path in parent portal
- parent/child:tab1 - tab1 in child portal
- parent/child:tab1/tab2 - tab2 in child portal.
When the incoming url is checked against the dictionary, it first looks for a portal/tab match, then a child portal/tab match. Obviously the performance decreases linearly with the number of child portals, but I've never come across any installs with a great number of child portals. It's probably something that free hosting companies do. I try to do a fresh install for each site personally.
The only restriction would be on a child portal called tab1 (because of the name collision with the parent tab tab1).
I've only done unit testing on this as I don't have a 'production' site which uses child portals. I did have one client who was going to set up a series of child portals, but I think that idea has been dropped now. I guess I need someone to try it out in 'the real world' and confirm it works OK.
I can email you the next version if you like, feel free to poke around and see how it works. |
|
iFinity DotNetNuke Modules |
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:11937
|
| 11/21/2007 4:29 PM |
|
For child portals, thats what I had discussed previously with Shaun, the ability to have a delimiter to separate the portal alias from the rest of the url. I assume you use your own tab dictionary rather then the core one for the lookup? The problem with storing the portal alias into the tab dictionary is multiple portal alias's cause a problem.
It's probably better to split the url, do a portal alias lookup and then do a tabpath lookup using the core tab dictionary.
If you could send me the latest, I can have a look at the compatibility bug as I have a bit of spare time today. Or do I just download the latest from your site? |
|
Scott McCulloch
Site Administrator |
|
|
bchapman
Registered Users
Nuke Super Newbie
Posts:21
|
| 11/21/2007 4:49 PM |
|
Yes that's right, I use my own tab dictionary. It is built up specially then cached. I understand what you say about multiple portal alias' causing problems. But the whole reason for me doing this was to get better SEO results from Google, in particular. And having multiple portal aliases isn't a very good idea on that front (allowing Google to index duplicate content on different url's).
I think a growing problem is flexibility vs SEO in this type of work. There will always be a camp saying 'we want to use whatever url we want' and another saying 'we must only ever have one simple url per unique page of content'. It might be a case that two providers are provided with the base install and it's up to the user to choose which one they use.
I haven't yet uploaded my new version to my website. I'll post back on here when I have, then you can just download it from there. I've just followed your lead and changed the namespace. |
|
iFinity DotNetNuke Modules |
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:11937
|
| 11/21/2007 5:09 PM |
|
If you change the namespace, it causes issues in host settings (as it expects a particular namespace). This really hurts any provider work you are trying to do, especially when the provider got pushed into 1 dll in the core.
It might be best to have a copy of the core dotnetnuke.httpmodules.dll with your changed friendly url files. A real pain I know - but I didn't make the changes to the core that added these dependancies. |
|
Scott McCulloch
Site Administrator |
|
|
bchapman
Registered Users
Nuke Super Newbie
Posts:21
|
| 11/21/2007 5:41 PM |
|
Oh, I didn't realise the problem with the host settings. I'll have to see how that affects things. When you say include the DotNetNuke module in with my code - do you mean the binary or the source? If the person doens't delete the existing provider, then it shoudl still work OK?
Anyway, I've released a new version, the updated page with the download links is at http://www.ifinity.com.au/Blog/TechnicalBlog/tabid/60/EntryID/24/Default.aspx (I really must implement the provider on that site!)
Another thing I should mention - some people have reported to me that using your articles module with my code results in a '+' for the last query string parameter. I assume this is because there is an uneven number of parameters in the article QueryString - do you pad the query string out with a space in this case, or is somethign else afoot? |
|
iFinity DotNetNuke Modules |
|
|
Scott McCulloch
Administrators
Nuke Master
Posts:11937
|
| 11/21/2007 5:52 PM |
|
| No I pass in the pageName attribute of the friendly Url methods - this normally adds the title of the article instead of the default.aspx, it is a parameter in the provider |
|
Scott McCulloch
Site Administrator |
|
|