|
|
Rank: Member
Joined: 12/22/2009
Posts: 4
Points: 12
|
I am using the trial version of Mobile Entree on a MOSS site. Whenever anyone enters the home page url: http://site.com, they get redirected to the pages library because the url gets changed to: http://site.com/medefault.aspx?__p=%2fpages%2fDefault.aspxIt looks like it is appending the pages/Default.aspx to the query string and taken the user to that library. Why is it doing that instead of taking the user to the home page?
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 75
Points: -204
Location: VA
|
Whenever the HTTP Module detects that you are using a mobile device, it will redirect you to medefault.aspx and send where you were trying to go as a parameter. This allows you to build mobile applications that can display mobile versions of regular URLs using the same link. It sounds like your HTTP Filters need to be tweeked if all traffic (even IE/FireFox on the desktop) is getting auto-redirected. Check out the HTTP Filters section of our documentation http://www.mobileentree.com/docs/Wiki%20Pages/HTTP%20Filters.aspx.One other thing to note: the out-of-the-box functionality of Mobile Entree revolves around SharePoint data in the context of SharePoint. So, Lists, Document Libraries, etc... It does not have the ability to automatically format things like pages in a publishing site. If that's what you are looking to do, you would want to take a look at creating a custom mobile app using the API that displays those pages. I kind of rambled there, but I hope this helps a little bit :)
|
|
Rank: Member
Joined: 12/22/2009
Posts: 4
Points: 12
|
Thanks for your reply. But, I think I might not have been clear in my description. All traffic isn't getting auto-redirected, I was speaking specifically about mobile devices. Ex: I go into my BlackBerry and type http://site.com. I expect to be redirected to http://site.com/medefault.aspx, but instead I get redirected to http://site.com/medefault.aspx?__p=%2fpages%2fDefault.aspx.It's almost like it is appending the default.aspx page to the query string because MOSS technically redirects you to the pages/default.aspx page when you type the regular url in (i.e.: http://site.com). Does that make sense? I am not sure if you have experienced this on any other MOSS site before. Could this be an AAM thing or a Load Balancer thing? It's weird. p.s. Thanks for the explanation of the pages. I caught onto that while demoing the app. Luckily we only have the requirement to show lists right now and will consider upgrading to the custom mobile app if the requirement changes.
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 75
Points: -204
Location: VA
|
Technically that is "working as intended".
Microsoft has an HTTP Module in place for publishing sites and wiki sites (and a few others I think). Our HTTP Module gets fired after theirs. The page never loads, but ME thinks that the request is for "/pages/Defaul.aspx". That URL parameter is there so a developer can know where the user was actually trying to go. Once the mobile device is at "medefault.aspx", all traffic flows through medefault.aspx (AJAX and POST).
Think of it this way: You have a custom alert that gets sent out in email that has a link in it to "/MyAlertPage.aspx". You can set up a mobile application (using the ME API) that will only be run if the user trys to go to "/MyAlertPage.aspx" on their phone. This is called the "Path Regular Expression" that is defined in the mobile app's configuration. You can see it at work with Access Requests. When a user generates an access request, SharePoint generates an email with pre-defined links and sends them to the site admin. If you have ME installed and activated on that site, you can grant access from your phone using that same link that's in your email.
-joe
|
|
Rank: Member
Joined: 12/22/2009
Posts: 4
Points: 12
|
I understand what you are saying, but if a user goes to the main url, I would expect them to go to the home page (i.e.: home page of the mobile app). I don't think the user will understand what is going on.
Is there anyway to overwrite this default behavior for the default.aspx page without doing custom development (i.e.: using the basic installation with the out-of-the-box functionality)? I'm just trying to get a simple mobile solution for our users on our site using simple functionality. We think the user will expect to go to the home site, see the lists they can navigate to and then navigate to them.
Is this possible with the basic functionality? If so, how?
Thanks,
Greg
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 75
Points: -204
Location: VA
|
ahh, I think I get it now.. It's sendig them to the details of the Default.aspx file right? I will have to get back to you on that one. This is most likely a byproduct of an update that we made, definately fixable. I will get back to you in the morning through email.
|
|
Rank: Member
Joined: 12/22/2009
Posts: 4
Points: 12
|
Actually, it is sending them to the list view of the pages library (i.e.: they see a list of all the possible pages on the root site). We have to click the home icon after we access the site to get to the actual mobile home page.
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 75
Points: -204
Location: VA
|
You're absolutely right. This is an oversight on our part that will be fixed immediately. The problem stems from a "feature" that we implemented to allow users to access workflow tasks whether or not the list is visible (via ME Configuration). This "feature" spills over into other lists and libraries, and that's why you are seeing the index view of the pages library on your publishing site. Your work-around for now is to have mobile users go directly to http://site.com/default.aspx or http://site.com/medefault.aspx. We will be adding a configuration field that will allow you to set up paths that get ignored by the base plugin (like "/pages"). I will let you know when this fix is implemented and you can download it and upgrade your installation. Thanks for working through this with us. -joe
|
|
Rank: ME Staff
Joined: 1/12/2009
Posts: 75
Points: -204
Location: VA
|
Update: The latest release has addressed this issue.
There is now a field in ME Config where you can set up paths to be ignored, like "/Pages".
|
|
Rank: Member
Joined: 2/3/2010
Posts: 1
Points: 3
Location: Nashville, TN
|
I too am having this issue. I am using the latest version with the included Path field, but it doesn't seem to be working. I've entered "/Pages" into the Path field, but I still am getting the Pages library as the home page vs. the actual default.aspx page.
Update: I took out the / and just put in Pages and it works fine now.
|
|
|
Guest |