Base solution for your next web application

Activities of "alukaszewski"

Thanks for your reply DoubleDP,

Instead of L("string") if I just use "string" the project will not run/build and the editor shows a syntax error. If I use L("Microsoft") then the menu shows [Microsoft] instead of just Microsoft !?

Yes, the adjustment to C# may be a little tricky, but most of my custom code is JavaScript so I should be able to survive. I do have some WebService .asmx in my prototype that returns JSON data if you pass it the name of a .sql file or SQL query and I think what I will do with that is keep it as a separate project in VB.NET.

My project is fairly simple, so I'm hoping most of ASP.NET Zero I can leave alone and not have to worry about learning how it intricately works, or have to learn C# too much, I just want to throw in a good few dozen pages into the Mpa model each linked by the menu system or urls within each other. In my prototype, I centralised the whole navmenu into a single .ascx User Control and called this from each page, with a tiny JavaScript running on each page to set the desired menu item as "active". I am glad to see that the ASP.NET Zero project centralises the menu and takes care of this for me.

I hope some of the more advanced forums users might help us in overcoming some of these first hurdles in using ASP.NET Zero.

Thanks!

Andy

I think I've solved this by poking around with the page inspector. I have added;

font-size: 16px; color: #a7bdcd;

to the simple-line-icons.min.css.

looks much better!

I just noticed that this issue also manifests itself in the ASP.NET Zero demo we created, so I am glad it is not something I am doing wrong.

I have requested access to the GitHub repository so that I can follow this issue.

OK, so I might be on the right track - but can I actually use the customData parameter to add an id="myid" inside the <li> tag, or is customData simply a way of adding attributes in the menu object and not a means to output something in client facing html code?

I wish to be able to use JavaScript document.getElementById function to find an <li> in the DOM, by id, so that I can re-use my existing JavaScript code to inject a sub-item into the menu when the page has loaded. Here is my working function below;

<script type="text/javascript">
        // Add a Dynamic Menu Item linking back to the parent page and make it active.
        var li = document.getElementById('menu-parent01-child01');
        var dynul = document.createElement('ul');
        var dynli = document.createElement('li');
        dynul.classList.add('sub-menu');
        dynli.setAttribute('id', 'menu-parent01-child01-temp01');
        dynli.classList.add('active');
        dynul.appendChild(dynli);
        li.appendChild(dynul);

        dynli.innerHTML = '<i class=icon-bar-chart></i>MenuName';
    </script>

The function above would add a new menu item to the child01 menu item in the menu code I previously posted. or is there an alternative, more modern/MVC solution to finding the current menu item using the abp.application.navigation classes and then the page view adding in a new menu at runtime?

Thanks for your support.

Any idea?

I see that this issue has been resolved in 1.7.0 - how do I know which code or files to replace to fix this issue in 1.6.1.0? Do I need to upgrade all files to 1.7.0 - if so, what about my customisations to PageNames.cs etc.

Andy

I have removed the mpa/bundles files and also modified the .vbproj file to remove the include entries for the .css files as per the commits in GitHub, but the issue remains. When I publish the Release version I am getting 404 for the "/Bundles/img/sidebar-toggle-light.png", but if I publish the debug version of the project the file url is coming from "/metronic/assets/admin/layout4/img/sidebar-toggle-light.png" and works OK.

Why is the Release version going for the /Bundles folder and not the /metronic folder?

Figured it out. I had to republish the site and enable the option to remove extra files. Release version on production server now looking great!

Hi Hikalkan, although the code is good for rendering third level menu items - when you navigate to third level URL the parent and grand parent nav-menu <li> is not marked with class=active, so the menu is collapsed.

Answer

OK, maybe I asked my question incorrectly.

When I access my published site in IIS, how do I have it start with the Login page instead of the default "Home page" page? My Startup.cs is already set with LoginPath = new PathString("/Account/Login").

So, basically, I want the project to start with the Account Controller and not the Home Controller? Does that make sense?

Showing 1 to 10 of 43 entries