Setup OGProxy for use in NodeBB

[phenomlab]

@DownPW are you sure there is no error in the console?

[DownPW]

nope no error

[DownPW]

for custom js script, API key is just on ACP/customJS and not on /home/XXXX/domains/proxy.XXXXXX.XXX/ogproxy/function.js file because not write in tuto

[phenomlab]

@DownPW function.js is just the code that gets pasted into the custom JS console

[DownPW]

[phenomlab]

@DownPW can you change the key so it’s 64bit? Just a theory I want to test. You’ll need to change it in the function and the server.js file.

[DownPW]

Ok I will test now

[DownPW]

Seem to be better. Just CSS problem I guess. I must see that

[phenomlab]

@DownPW yes, you can use the CSS I provided in the original post as a starting point.

I’m guessing that the server received a truncated API key because of the length so the authentication failed.

[DownPW]

But see the second link, I don’t think it’s a CSS problem no ?

[phenomlab]

@DownPW yes, try the CSS provided in the article.

[DownPW]

Already Done.
It seems i’m not be able to change text color after test. Idem with important

[phenomlab]

@DownPW that may be your local CSS. I don’t think any of my code would prevent that

[DownPW]

???

Example:

yep better with disable all the rest of my CSS code grrrrr

it’s not going to be easy to find but it shows that there may be conflicts with the master CSS used

[phenomlab]

@DownPW I don’t think that’s in the list of classes I provided?

[DownPW]

hmm yes

h4.card-site-title {
    color: var(--bs-body-color);
    text-transform: capitalize;
}

[phenomlab]

@DownPW no. Look at your screenshot. The initial target is #sitetitle. Also, there’s no enforcement of !important in that class.

[DownPW]

yes you are right.

I Have find the guilty: It’s my code to have an effect on URL link :

.posts .content a {
    color: var(--bs-link-color);
    /*background-image: linear-gradient(to right, var(--bs-link-color), var(--bs-link-color) 50%, var(--bs-link-hover-color) 50%);*/
    background-image: linear-gradient(to right, var(--bs-link-hover-color), var(--bs-link-hover-color) 50%, var(--bs-link-color) 50%);
    background-size: 200% 100%;
    background-position: -100%;
    display: inline-block;
    padding: 5px 0;
    position: relative;
    -webkit-background-clip: text;
    -webkit-text-fill-color: transparent;
    transition: all 0.3s ease-in-out;
}
 
.posts .content a:hover {
 background-position: 0;
}
 
.posts .content a:hover::before{
    width: 100%;
}

[DownPW]

But I wonder how to keep it without it coming into conflict with OGProxy, especially for the internal links to the site which do not have an iframe

[phenomlab]

@DownPW just needs carefully crafted CSS.