Hi Ben,

1. While it is possible in some cases to add content features right into the layout.master, it can be problem prone because most features really need to be connected directly to a specific page in order to enforce page level security. You can add a slide show directly in the layout.master as illustrated in andreasvicklund_02alt1 skin. It is also possible to develop whatever functionality you need in a UserControl and just add the UserControl into layout.master.

2. I am looking into doing away with the YUI tabs and switching to YUI tabs in the admin and edit pages. Mainly I want to make this change because there are more themese for the jquery and because I would like to just use all jquery and move away from using both jquery and YUI. However, I need to do a lot of testing first, when I attempted this change once before I ran into trouble with nested tabs in jquery and there may also be issues with using the wysiwyg editors inside jquery tabs whereas they work fine in the YUI tabs. I seem to recall there being issues with this in the jquery tabs when I tried it before.

3. Whatever gets the job done. You can definitely create a custom feature and register custom scripts from code. Or you could make a UserControl that registers your scripts and put it in layout.master. Inside the control you can have logic to decide whether to register the scripts based on url or whatever you like.

Hope it helps,

Joe

Hi Ben,

Look forward to seeing your site and blog post.

When using a PostbackUrl, of course the click event on the current page cannot fire because it doesn't post back to the current page, the postbackurl page receives the post instead.

Now the receiving page, in this case SearchResults.aspx has to know what to expect in the post in order to be able to handle it correctly. So in this case what it does is get a reference to the page that posted and it looks for the specific id of the search input from the master page of the posting page like this:

SearchInput previousPageSearchInput = (SearchInput)Page.PreviousPage.Master.FindControl("SearchInput1");

note that first it must check whether Page.PreviousPage is null or not, this is how it knows if it is receiving a cross page postback.

To make it work from a control that is not in the master page I would have to add an additional attempt to find the control in the PreviousPage itself instead of the master page of the previous page like this:

if (previousPageSearchInput == null) { previousPageSearchInput = (SearchInput)PreviousPage.FindControl("SearchInput1"); }

I just added this to my copy actually. However it still requires that your search textbox have the id "SearchInput1" in order to be able to find it.

Or actually it is looking for a control of type SearchInput not a TextBox so probably the way you did it with a redirect is more simple and reliable.

Best,

Joe