Activités de "ageiter"

In this case; Account & Security logs pages are on AuthServer project which is an different MVC project. You have to configure your AuthServer as TopMenu too.

How can I do that? Where do I have to configure this?

Aaaah, yes exactly, that's the point. I wanted to try the public site (with the CRM module). But since the CRM module can only be used on the public site and not in Blazor, we discarded it and generated a new app without the public site.

Thanks, it's clear to me now. :-)

Thank you for the explanation.

Then there was probably a problem with the version 6.0.0-rc.3. Because with a newly generated app (Blazor Server non-tiered) I had an exception that pointed to the missing Redis cache. So I had to install this on my PC and then was surprised that it did not need it on Azure. But maybe that was a bug you guys fixed in 6.0.0-rc.4.

Ou... I just found something else related to the TopMenu.

9. TopMenu layout is not consistently applied everywhere: When you go to "My Account" or "Security Logs", the view changes to the SideMenu layout.

Hello, this ticket has been closed although my question has not yet been answered....

Why does it work without the Redis service in Azure App Service? And when would it be important to use it?

Thanks for the feedback about issue 2. Since these issues are probably not public, will you let me know when it is resolved?

About issue 5: I have now created a new app with Abp Suite, taking the latest template (Blazor Server 6.0.0-rc.4). Changed the layout to TopMenu and started. The problem is there from the beginning.

You can also press F5, each time the user menu will open automatically.

Hi, I have now created a new app with the latest template (Blazor Server 6.0.0-rc.4), run it and the problem occurs immediately. To illustrate it I made a screencast: AbpBug3705.mp4


Edited on 16.11.2022: Unfortunately, I can no longer reply here because the ticket is locked. But I think the problem is not solved yet and I would like to know for which version the bugfix is planned (currently I have version 6.0.1).

I have a solution for number 4. I have implemented the boxed layout with the following CSS:

.lpx-topbar-container, .lpx-content-container {
    margin: 0 auto;
    max-width: 1280px;
}

8. Footer height is too big: I have discovered another new problem. The footer height is way too big (is calculated wrong). Probably the style is good for a blank / small page. But if there is content on the page, the footer becomes huge. The problem here is the min-height:

.lpx-content-container .lpx-content {
    max-width: 1280px;
    min-height: calc(100vh - 192px);
    margin: 0 auto;
}

I changed the image and had problems with the size and alignment. Now I have set the following CSS styles and so the image is set as background for this column. This way it looks great even with different screen sizes.

.lpx-login-image-area img {
    display: none;
}

.lpx-login-image-area {
    background-image: url("/Themes/LeptonX/Global/assets/img/login-bg.jpg");
    background-position: right;
    background-repeat: no-repeat;
    background-size: cover;
}
Affichage de 141 à 149 sur 149 entrées
Made with ❤️ on ABP v8.2.0-preview Updated on mars 25, 2024, 15:11