Hi All,

I tried adding this code:

if (Request.Browser.IsMobileDevice)
{
  if (Request.Cookies["mobileUser"] == null)
  {
    HttpCookie appCookie = new HttpCookie("mobileUser");
    appCookie.Value = "true";
    appCookie.Path = "/";
    Response.Cookies.Add(appCookie);
    Response.Redirect("/Mobile/");
  }
}
 

to the default.aspx.cs file at the top of the Page_Load method. The idea is that mobile users would, at first, be directed to the mobile site and then be able to link back to the main site if their device can handle it. What I'm finding is that Page_Load is getting executed twice. You can actually see the mobile page for a second but the the code executes a second time, finds the cookie, and goes right back to the main home page. I even tried taking out the cookie setter and putting it in the home page of the mobile site, but still got the same effect. I've tried tweaking numerous things but nothing seems to be working. Any help?

Thanks,

John

I probably could've explained a bit more. I'm not really thinking this is specifically a mojoPortal issue. I was also having this issue with a custom module I created using the WYSIWYG editor. If I use the normal asp:Button that generates an input type form element, it works fine. If I use a <button> element on the form, it causes the page to load twice and I was getting two records inserted when adding something new. I did some testing with the button vs input in a project completely outside mojoPortal and was getting the same results. I just haven't been able to figure it out. I keep getting this occassional double page load method execution in random situations on my machine and it also seems to carry over to test and production web servers. And it also doesn't seem to do this on every computer. I checked around with a few other people and some see it and some don't. It doesn't seem to be browser specific but nothing I've tried seems to make a difference and I was just really hoping somebody here might have run into this issue and had a suggestion.

I looked at the default.aspx page and noticed that the autoeventwireup is false. In my layout.master of my skin it is set to true. I tried setting that one false and that broke everything. I do have wireup set to true on a module that I created but I'm not explicitly doing any event binding in the code for those pages. Would the wireup on ascx files included in the page cause the default page_load to run twice? Is it then in general necessary that any modules you create for mojoPortal should have AutoEventWireup set to false? (I don't think that would be a problem, but certainly good to know)

Well, that's a relief. That's initially how I understood it. I thought maybe my whole grasp of ASP.NET was about to go out the window. Oh well. I was hoping someone would have recognized my dilemna and just offered an, "oh, just go check that box over there." That seldom seems to be my luck. I'm just stumped as to why I keep running into these doulbe page loads. Maybe it's time to call MS. Or maybe it's time to stick a firecracker in my PC and get a new one.

Thanks again.