Activities of "BobIngham"

Thanks Aaron, it's as a result of recently upgrading to 6.8.0 from 5.4.1 so I missed that update.

Hi @ismcagdas, I managed to get hold of version 5.1 Metronic, that will do me for now until I upgrade to Zero 7 and I believe that will include Metronic 6. Cheers.

Thanks @ismcagdas. Ok. Where is it? You guys sent me a link for this version of 5.5.5 but I can't find the default version in the unzipped file.

This seems to be a material interface. Where, for example, are portals?

Jeepers, creepers, Aaron, the amount of time you spend on here helping people out I thought you were full time with Volosoft. I sincerely apologise for anything I may have said in haste and thank you very much for all the help you have given me in the past. I commend you on your attention to detail. From now on I will defend you to the hilt and sorry for any offence I may have caused. And any time you're looking for a job just drop me a line!

Thanks Aaron, I don't want to change service-proxy.module.ts. As I said, I have no idea how a lot of this stuff works which is why I'm grateful for you guys for giving me a framework I can copy from. Your post led me to google some more based on the fact that I needed to remove headers from the request without changing the underlying framework. The answer is to pass a null value for the headers parameter in the get request.

return this.http.get<{ ip: string }>('https://jsonip.com/', null);

This may seem obvious to you, but if it is then maybe you should have suggested it in the first place rather than sending me round the houses by pointing out that I didn't even know what the nature of the problem was, then telling me that Zero has .AllowAnyHeader() set and then asking me how to reproduce the problem. If it wasn't obvious to you then I apologise for calling you out.

Inject httpClient into any component in Angular Zero:

import { HttpClient } from '@angular/common/http';

Add a new method:

    getClientIP(): void {
        this.http.get<{ ip: string }>('https://jsonip.com/')
            .subscribe(data => {
            console.log(data);
        });
    }

Call the method from the ngOnInit() event:

this.getClientIP();

And you will get the same error. Tell me Aaron, just as an aside, do you get more pleasure from:

1. proving you are a better coder than others,
2. helping people out when they have a problem, or
3. just pissing people off?

It's something I have often wondered when I have defended your comments on here and in the github pages....

Aaron, thanks very much for pointing out that I have a problem which is different to the one I thought I might have. I am now happy we have established the problem. Thanks. Should I raise a different post for the header problem or would you like to suggest a way I can fix the problem? How do I change the header from within the code? As I said, I am no CORS genius, in fact I am no genius at all and bow to your superiority in this field. Any help and suggestions you can give are gratefully recieved.

Hi @ryancq, yes that option is set. However I will take a closer look at this because I have not enabled Hangfire using abp.hangfire, I simply implemented Hangfire in the Core project using Nuget.

Hi @ryancq, understood, I took a look at the code. The user can enable Google Authentication regardless of whether the option is set. As soon as you set 2FA Google Authentication is enabled at the user level. Switching it off at the host level does not change this.