Activities of "AlderCove"

Reopening

Hi, can you please provide us with a timeframe for the release, so we can inform our customers? Also, we are on ABP.io 6.01. Can we continue with this, or will the LeptonX release require an update to our ABP.io version too?

Just adding a little more info - with the tab issue resolved:

1. The lpx-inner-menu "collapsed" class is correctly being applied to the submenu unordered list element
2. The enclosing lpx-menu-dropdown div and child lpx-inner-menu-item elements are not being displayed

I have messed around a little to try and get these elements to display:

1-) Updated the outer-menu-item list item in \Themes\LeptonX\Components\TopMenu\MainMenu\Default.cshtml to conditionally (if not a leaf) have "has-drop" class:

<li class="outer-menu-item @(!menuItem.MenuItem.IsLeaf ? "has-drop" : "")"> @await Html.PartialAsync("~/Themes/LeptonX/Components/TopMenu/MainMenu/_MenuItem.cshtml", menuItem) </li>

2-) Added menu.js (as in https://support.abp.io/QA/Questions/3314/Adding-support-to-sub-menus-on-the-main-menu-for-keyboard-accessibility) that adds/removes the 'open' class for the list items with 'has-drop' on click events:

$(function () {
    var menuItems = document.querySelectorAll('li.has-drop');
    Array.prototype.forEach.call(menuItems, function (el, i) {
        el.querySelector('a').addEventListener("click", function (event) {
            if (this.parentNode.classList.contains("has-drop")) {
                if (!this.parentNode.classList.contains("open")) 
                    this.parentNode.classList.add('open');
                else
                    this.parentNode.classList.remove('open');
            } else {
                this.parentNode.className = "has-submenu";
                this.setAttribute('aria-expanded', "false");
            }

            event.preventDefault();
            return false;
        });
    });
});

3-) Added a bit of css to handle the open class:

.lpx-header-bottom .lpx-nav-menu .outer-menu-item.open > .lpx-menu-dropdown {
    visibility: visible;
    opacity: 1;
    height: unset;
    display: block !important;
}

.lpx-header-bottom .lpx-nav-menu .outer-menu-item.open > .lpx-menu-dropdown .lpx-inner-menu .lpx-inner-menu-item .lpx-menu-item-link {
    display: flex;
    color: var(--lpx-content-text);
    white-space: nowrap;
    padding: 0.4em 0.7em;
    border-radius: var(--lpx-radius);
    text-decoration: none;
    transition: background-color 0.5s ease, color 0.25s ease;
}

.lpx-header-bottom .lpx-nav-menu .outer-menu-item.open > .lpx-menu-dropdown .lpx-menu-item {
    width: 100%;
    height: auto;
    line-height: 1.5;
}

Although I'm pretty certain this isn't the preferred approach, it almost works. The issue appears to be the incorrect height of the submenu. In this example, the submenu should show two options but only part of the first is visible (hover works fine):

Appreciate your help on this - its very urgent for us.

Thanks

I fixed the tabbing issue by overriding the LeptonX/Components/TopMenu/MainMenu/_MenuItem.cshtml and adding the href="javascript:'" in the top-level menu item:

<a href="javascript:;" class="lpx-menu-item-link lpx-menu-item @(Model.IsActive ? "selected" : "")">
	X
	@if (!Model.MenuItem.Icon.IsNullOrEmpty())
	{
		<span class="lpx-menu-item-icon"><i class="lpx-icon @Model.MenuItem.Icon" aria-hidden="true"></i></span>
	}

	<span class="lpx-menu-item-text hidden-in-hover-trigger">@Model.MenuItem.DisplayName</span>
</a>

The menu still needs to dropdown on enter though.

Are you able to provide a fix that I can apply in the meantime?

I'm trying to use the module for a current project with 6.0.1

Shared a link by email:

Thanks

Closed with solution here: https://support.abp.io/QA/Questions/3579/Possible-to-connect-using-two-different-database-management-systems-in-single-solution

Thank you so much!

It was trivial in the end and seems obvious now I see the solution.

The migrations weren't an issue for me in my production solution but thank you for updating those too and the docker setup.

I have deleted the commercial github repo and created a new open source repo. https://github.com/jtasko/MultipleDbContextDemo

This is based on the community post you shared and that I have already reviewed.

I removed the MongoDb project and added a new MySql EF Core Project (MultipleDbContextDemo.MySql.EntityFrameworkCore). This project has DBContext for the MySql database.

I updated the solution to contain two entities; TestSqlServerEntity and TestMySqlEntity.

I added connection strings for the MySql Db Context.

I created migrations for each EFCore project and updated the databases. Each database has the appropriate tables.

I have the same issue with this solution and cannot connect to both the MySql and SQL Server databases. The order of the DependsOn results in the application using either the Sql Server or MySql connections. One or the other, but not both.

There could very well be something trivial that I have missed but I really, honestly, could use some help here.

Thanks

• UI framework: MVC
• Mobile: None
• Database provider: Entity Framework Core
• Database management system: SQLServer
• Public website: No
• Separate tenant schema: No
• Tiered: No
• Preview version: No

Hi

I have completed some additional testing in a simpler solution and have the same issues.

1. Created a new 5.1.4 application template using abp suite called EfCoreMultiContextApp:
2. Generated a test entity called TestSqlServerEntity
3. Added and configured new project to the solution for My SQL
4. Created test entity called TestMySqlEntity
5. Created and ran migrations - both the databases have the correct entities created
6. Added references in .Web app to the MySql EF Core project

I have the same issues where either MySql drivers are used or Sql Server drivers are used depending on the order of the DependsOn references.

I have uploaded the code to github: ** removed **

It's a very simple example and it demonstrates the same issues I am having with my more complex application.

Appreciate your assistance with this!

Thanks