Activities of "mpvismer"

Thanks! Appreciate that. This will work until the content fills the screen and then scrolling never enables.

I think we need to find the place where the minimum height of the main content view is calculated and adjust that to be a few lines shorter.

(I.e. i don't think a generic fix is possible - it will have to be an adjustment which is tweaked specifically to the height of your footer.)

Thanks

• ABP Framework version: v5.1.4
• UI type: Blazor Server (but I think applies to WebAssembly as well)

Thanks, this helped, but in the end, in the end the answer came from reimplementing the ExternalLoginProviderBase and LdapManager classes in the source. Thanks

Thank you.

Is there perhaps any documentation on how to use that? The documentation here only seems to show what it does as a standalone module.

Is there a way for a user to upload a file and then use that file within the rest of the application?

We resolved this. Some of the URL are derrived from the incoming requests and our reverse proxy was changing these.

We had to config the app to use forward headers as in here: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-5.0

and then update the nginx configuration as below:

server {    

server_name sub.example.com;

underscores_in_headers on;

 

   location / {

                rewrite /(.*) /$1  break;

                proxy_pass         http://10.216.2.11:8083;

           proxy_redirect     off;

           proxy_http_version 1.1;

            proxy_cache_bypass $http_upgrade;

            proxy_set_header   Upgrade $http_upgrade;

            proxy_set_header   Connection keep-alive;

            proxy_set_header   Host $host;

            proxy_set_header   X-Real-IP $remote_addr;

            proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;

            proxy_set_header   X-Forwarded-Proto $scheme;

            proxy_set_header   X-Forwarded-Host $server_name;

    }

 

    listen 443 ssl; # managed by Certbot

    ssl_certificate /etc/letsencrypt/live/sub.example.com/fullchain.pem; # managed by Certbot

    ssl_certificate_key /etc/letsencrypt/live/sub.example.com/privkey.pem; # managed by Certbot

    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot

    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot


 

}server {

    if ($host = sub.example.com {

        return 301 https://$host$request_uri;

    } # managed by Certbot

 

server_name sub.example.com;

    listen 80;

    return 404; # managed by Certbot
 

}