Activities of "phil@travelengine.com.au"

FYI. I reverted the above changes and tried again.

After doing the switch to nightly builds using abp-suite there are a number of package references I had to manually correct but the result is the same:

[14:09:13 ERR] ABP-LIC-0003 - No modules found! There's no module found for your organization. Contact to license@abp.io for more information. [14:09:14 ERR] ABP-LIC-0013 - License exception: ABP-LIC-0023: An error occured while calling the license server! License check communication failed! The response was not successful: 400 - Bad Request [14:09:14 ERR] ABP-LIC-0001 - Couldn't check license within the allowed time period, please enable your internet connection. [14:09:14 ERR] ABP-LIC-ERROR - License check failed for 'Volo.Abp.Identity.Pro.Domain-v8.0.0.0'.

I used abp-suite to switch my solution to nightly builds.

I then updated all the EF Core references in my projects to: 8.0.0-rc.2.23480.1

I then built the application but get the error shown when I try to run.

Thanks. Will this be available in the nightly builds once your pull request in merged?

I am sorry Anjali but I am no wiser on how this is supposed to work.

The documentation says that LogoReverseUrl on IBrandingProvider should specify the application logo on a reverse color theme. This is ambiguous because 'reverse' means it is the relative to something else, but what that something else is, is not clear.

In an apparent attempt to clarify the documentation then says '(dark, for example)'. It is worded in a very confusing way and IMHO the documentation should be made much clearer - particularly for something that virtually very ABP user will want to customise right out of the box.

It also seems to be absolutely the opposite of what SideMenuLayout.cshtml actually does -- that component will cause the variable --lpx-logo to be set to IBrandingProvider.LogoReverseUrl for .lpx-theme-light, or to IBrandingProvider.LogoUrl for .lpx-theme-dark or .lpx-theme-dim.

So I still have no answer to my original question - the documentation and the code are total opposites of each other.

Thanks very much Anjali for getting back to me.

We are doing some prototyping and due to the lack of consistency in capabilities between Blazor and MVC we have now decided to build with the MVC version. It seems that this will require less dev effort at our end until ABP fully supports Blazor.

It might be worth correcting the documentation to show where samples are specific to a certain UI. E.g. this page: https://docs.abp.io/en/abp/7.3/Modules/Cms-Kit/Tags contains no indication that the instructions are only relevant for the MVC UI.

Cheers, Phil

What are the values for LogoUrl and LogoReverseUrl set on your IBrandingProvider

The styles you are showing on the right appear to have come from the .css file. IBrandingProvider values are injected directly into the header and override the CSS like this.

Then if ABP suite is no longer going to allow this. Then the option should be removed. Because right now it appears that it DOES support installation of that theme.

Please refund the credit for my question.

Yes. I am aware of the work around, which I have done.

But there was an indication that the problem would be fixed in an imminent patch. (around 2 months ago I think)

Has the problem been fixed in ABP Suite? If not, are you able to provide a timeline?

Thanks, Phil

Yep. That fixed it. Thanks!

I am unable to find any question at this URL.