DotNetNuke 5.14 Search User Enter Key Issue

A04C0091

I recently upgraded a DotNetNuke installation and found several issues that are either different from the 4.x series or are now broken.

Most annoying is that there is now no longer any visual indication that a module is viewable by the administrator only.  Seems there should at least be a CSS class added to the module so that we can control the visual representation ourselves if we want.

Unfortunately there is nothing we can do about that.

But another issue that showed up is in the user screen.

There is a search box where you should be able to search for a user as the administrator.  If you put your cursor in that field, put in a name, and press the ENTER key on your keyboard, you are directed to the Admin icons screen.  This is a new screen that was added in 5.x.

This is because the Admin LinkButton is getting “clicked” when you press the ENTER key.

To fix it, all we need to do is wrap the three controls–textBox, DropDown, and LinkButton–in a Panel and make the LinkButton the default button of the panel.

If you’d like to fix this yourself, open up the Users.ascx file located in ~\DesktopModules\Admin\Security\ .  Make sure you don’t pick the User.ascx file–there are two files.  You want the one with an S at the end.

Change this code

<td class="Normal" align="left" width="*">
    <asp:textbox id="txtSearch" Runat="server">
        </asp:textbox>
    <asp:dropdownlist id="ddlSearchType" Runat="server" />
    <asp:imagebutton id="btnSearch" Runat="server"
         ImageUrl="~/images/icon_search_16px.gif">
        </asp:imagebutton>
</td>

To this code

<td class="Normal" align="left" width="*">
    <asp:Panel ID="Panel1" runat="server" 
       DefaultButton="btnSearch">
    <asp:textbox id="txtSearch" Runat="server">
        </asp:textbox>
    <asp:dropdownlist id="ddlSearchType" Runat="server" />
    <asp:imagebutton id="btnSearch" Runat="server"
       ImageUrl="~/images/icon_search_16px.gif">
       </asp:imagebutton>
    </asp:Panel>
</td>

and everything will work like it should.

Related Post

  • DotNetNuke Modules – Creating Base ModulesDotNetNuke Modules – Creating Base Modules Now that we have DotNetNuke installed into Visual Studio we can go ahead and create our first modules. Actually, creating the modules is pretty simple. But it is even easier to do it wrong, which...
  • DotNetNuke 5.x Can’t Move Module On A PageDotNetNuke 5.x Can’t Move Module On A Page As I mentioned a couple of days ago, the move to DotNetNuke 5 has brought about a few changes.  Some of them are design decisions that are just frustrating, like not being able to see that ...
  • DotNetNuke Response.End() Doesn’t EndDotNetNuke Response.End() Doesn’t End OK.  This one is just plain annoying! For some reason that I’ve yet to be able to track down, Response.End() seems to have no impact at all under DotNetNuke. I tried various hacks.  Including...
  • DotNetNuke Modules – Creating the PADotNetNuke Modules – Creating the PA By now you have the basics for creating a DotNetNuke module.  The only question we have left to address is, how do we package this all up so that we can install it on another server? The file...
  • DotNetNuke – Collecting Profile at RegistrationDotNetNuke – Collecting Profile at Registration Yesterday I was asked a question that I thought was one thing and ended up being another.  But the question I thought it was is one worth answering here because it takes so darn long to fin...