Hi,

I can get atlas to work just fine with a stand alone page (simple example of a button, linked to a trigger inside an update panel.  Button's method updates text in a label inside the update panel).

However nothing happens when I use a master page, and then have the update panel on the content page.
I have tried both with the script manager tag on the master, and also on the content page.  I have also tried the script manager tag on the master page combined with the script proxy tag on the content page.  Nothing works.

What am I doing wrong?

Thanks for any help,
Richard

I'm having the exact same problem.  I've got things working just fine when outside of <asp:Content> tags, but when things are placed between them, it doesn't seem to return to the page.

The event fires, gets caught, and the event handler runs... but instead of updating the page, it throws a Javascript error.

Thanks!

(also, but a different) Richard

I could do that (http://futbol.pablocastilla.com enter in "morosidad" and type pab in the textbox, there is an updatepanel there),

can you put the code of the master and content page?

 

Hi,

It does not seem to matter if you put the script manager, update panel and button all on the content page or all on the master page - neither seems to work.

I will keep playing to see if I get anywhere.  Not sure if this is a bug, configuration issue or I am not doing something right.

Thanks,

Richard (from original post)

Another update:  Got it to work with content and master pages with a fresh atlas web project.  I put the scirpt manager tag on the master, and everything else on the content page.  So either I have not enabled my existing application in the right way to work with Atlas or there is something else that I am doing that is conflicting with it in some way (???).

....Richard

And the conflicting bit was.....

I had my own javascripts at the top of the master page.  These scripts were for keyboard commands to help users of my app navigate around a series of text boxes (e.g. given a list of x number of text boxes in a column, pressing the down arrow would move to the text box below, etc).

Removing these and it worked.  Obviously I don't fully understand what the script manager can do, maybe I have to put these types of scripts under its control in some way.  Anyway at least I have found what I was doing wrong, and know that I need to read up more on the script manager.

...Richard

I'm using the AutoCompleteExtender from within a child page with the ScriptManager and the Atlas control within the asp:Contant tag and everything works fine. I don't have any Atlas references in the master page. fyi.

I have scriptmanager just after the form tag in the master page. Later I use atlas normally in the content pages.

See ya!

Personally, I would avoid placing the ScriptManager in the master page as this will make every page on your site (if using the master page) bootstap the atlas engine even if your content page does not make use of any atlas functionality. I would place the ScriptManager only on content pages that are using atlas functionality/controls.

Nikhil K has a good write up of the ScriptManager.

I'm agree with you, but I don't know why I had to put in the master page because if not my google map content failed.

I had the same problem, and found that simply having an empty <script language=javascript></script> in my master page caused my Atlas-enabled page to fail.  It would just sit there.  Removing the tags fixed the problem.

At least in IE.  Firefox still has a problem with my master page and Atlas combination.

Hello Friends..

erlier i also face same problem with master and content page and after doing lots of R&D  i came up with some solution.

- Please check your web.config file. ( if you are trying to implement atlats in existing project then the configration of web.config file should be same when you create new atlas project)

- make sure that you ID of your content place holder in master page and contect in child page must not have a "_" charactor.. means ID="contect_Plaace1" is Invalid. id must be without "_"

- if you are using your own javascript in masterpage. then some time you are some time you are using dual conditional script then atlas not working..means for ex.

   If (Screenwidth == 1024 && Screenheight == 769)

   {

      .................

   }

if like above is there in your master page then atlas is not working bue

   If (Screenwidth == 1024)

   {

      .................

   }

and if script is like above then atlas is working...

 

Remove such script and then try  to run atlats...

Hope this will helpful for you..

 

- Piyush

 

I had a similar problem. Make sure that your contentplaceholder ID does not use underscores. For me the following fails

<asp:contentplaceholder id="cph_Content1" runat="server"></asp:contentplaceholder>

But

<asp:contentplaceholder id="cphContent1" runat="server"></asp:contentplaceholder>

works fine.

 

 

Same problem as the original poster here.

- Initial page (datalist containing usercontrols per itemtemplate) renders fine.

- ImageButton click event gets called, it's code gets executed

- No refresh occurs.

- Page (aspx containing the datalist which in turn contains the usercontrols) has a master-page defined.

----

No javascript in masterpage
No underscores in contentplaceholders
None of the other `possible causes` (let's be honest here, they're just silly)

The -only- difference with a page that DOES work is the fact that the non-working one is in a masterpage.

----

Markup of the aspx page:

<%

@ Page Language="C#" MasterPageFile="~/core/MasterPage.master" AutoEventWireup="true" CodeFile="commentTest.aspx.cs" Inherits="commentTest" Title="Untitled Page" %>

<

asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"></asp:Content>

<

asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder2" Runat="Server">

<atlas:ScriptManager ID="s1" EnablePartialRendering="true" runat="server"></atlas:ScriptManager>
<atlas:UpdatePanel ID="u1" runat="server">
<ContentTemplate>
<asp:DataList ID="dalComments" runat="server">
<ItemTemplate>
<uc1:wucComment ID="wucComment1" CommentID='<%# DataBinder.Eval(Container.DataItem, "commentID") %>' runat="server" />
</ItemTemplate>
</asp:DataList>
</ContentTemplate>
<Triggers>
<atlas:ControlEventTrigger ControlID="cmdAddComment" EventName="Click" />
</Triggers>
</atlas:UpdatePanel>
<br />
<asp:TextBox ID="txtComment" runat="server" Height="48px" TextMode="MultiLine" Width="536px"></asp:TextBox><br />

<asp:Button ID="cmdAddComment" runat="server" Text="Add Comment" OnClick="cmdAddComment_Click" />

</

asp:Content>

----

Any ideas or suggestions in regards to this one or does Atlas simply not support masterpages properly yet ? Either way I'd like to know.

 Thanks