Hi Tomasz,
From your description the Accordion initialization script is not rendered
in a nested master page scenario, correct? Is there a ScriptManagerProxy
put in the content page where the Accordion resides?
Could you send a demo project to me that can reproduce this problem? My
email is
v-******@microsoft.com. I'll try to repro it on my side to see
what the root cause of this behavior is.
Regards,
Allen Chen
Microsoft Online Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Tomasz J" <oe****@nospam.nospam>
| Subject: Accordion (Ajax Control Toolkit relelase 20820) problem after
migration to .Net 3.5
| Date: Thu, 28 Aug 2008 18:01:42 +0200
| Lines: 30
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
| Message-ID: <OA**************@TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| NNTP-Posting-Host: bwz5.internetdsl.tpnet.pl 83.18.233.5
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.dotnet.framework.aspnet:74835
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Hello developers,
|
| After migrating my web project application (using the old model) to .Net
| Framework 3.5 and Ajax Control Toolkit release 20820 the Accordion
control
| no longer works correctly. In certain cases (only) it renders but is dead
-
| does not initialize. Before the migration it worked, no changes have been
| made.
|
| Here is the complete scenario description:
|
| 1. There are two nested master pages, ScriptManager is defined within the
| grand master page, no ScriptManagerProxy.
| 2. There are two content pages using Accordion control. Accordion control
| works fine on whatever page opens first when the application starts
(tested
| with both pages), but does not work when I navigate to the other page.
| 3. The page where it does not work is missing Accordion initialization
| script:
| Sys.Application.add_init(function() {
| $create(AjaxControlToolkit.AccordionBehavior
| 4. All the control html tags render correctly, so the Accordion shows up
but
| is dead - panes cannot be expanded/collapsed.
| 5. All the other Ajax Toolkit Controls on this content page render and
| initialize. Only the Accordion control does not.
|
| It seems that ScriptManager thinks this script is already rendered. It
can
| also be some kind of caching problem. I am clueless.
|
| Thanks,
| Tomasz
|
|
