Setup OGProxy for use in NodeBB

[phenomlab]

@DownPW @dave1904 can you please replace your function code (found in function.js and used in the custom JS part of NodeBB) to use the below - please also remember to replace your proxy and apiKey values

ogproxy/function.js at main · phenomlab/ogproxy

Open Graph Proxy. Contribute to phenomlab/ogproxy development by creating an account on GitHub.

GitHub

I have found a couple of bugs this morning and fixed them. The original post has also been updated.

Thanks

[phenomlab]

I’ve added a new hover effect that will enlarge the image by 1.5 when activated. If you’d like this feature, you’ll need to pull the latest function.js code and use this to replace the existing in your custom JS console.

You will also need this additional CSS

.card-image-container {
    max-width: 100%;
    max-height: 250px;
    overflow: hidden;
    border-top-left-radius: 0.375rem !important;
    border-top-right-radius: 0.375rem !important;
}
 
#card-image {
    -webkit-transition: all 0.8s ease;
    -moz-transition: all 0.8s ease;
    transition: all 0.8s ease;
}
#card-image:hover {
    transform: scale(1.1);
  }

If you’d rather not have this feature, just remove the CSS block above.

[phenomlab]

Another update - code has been amended in GIT to fix the previewLinks() function crashing in chat

[DownPW]

Can you give procedure to update?

[phenomlab]

@DownPW Sure - you just need to copy the code from the below

ogproxy/function.js at main · phenomlab/ogproxy

Open Graph Proxy. Contribute to phenomlab/ogproxy development by creating an account on GitHub.

GitHub

And, of course, replace these two values with your own that you already have

var proxy = "FULL_FQDN_OF_YOUR_OGPROXY_HERE";
var apiKey = "YOUR_API_KEY_HERE";

No need to restart the OGProxy service

[DownPW]

Update done

Thanks for your work dude

[phenomlab]

@DownPW all good now?

[DownPW]

I will try chat ASAP
and it seems github private url doesn’t work but I think it’s normal because it’s a private repo

[phenomlab]

@DownPW that should still render but be replaced with substitute text and images. Anything in the browser console?

[DownPW]

nope nothing in log

And i Have this bug on the chat render (testing now)

[DownPW]

EDIT:

Nothing on, nodebb console but I have this on Browser Console :

it looks like the url is being misinterpreted. Symbols are appended to the URL.

Odd

[phenomlab]

@DownPW what’s the bug? CSS?

[DownPW]

[phenomlab]

@DownPW no, that’s URL encoding and supposed to look like that. If it were truly an issue, nothing would render.

[DownPW]

I don’t know my friend.

[phenomlab]

@DownPW I’ll check on your Dev server

[DownPW]

resolve my problem with add this to my custom CSS for rendering in the chat on smartphone :

@media (max-width: 1010px) {
    [component="chat/message"] .card.card-preview {
    margin: 20px 0 20px 0;
    width: 100%;
    }
}

And I add this custom css code for fix a bug (for me ) when you do a mouse hover on the image and the edges are not rounded. This bug is seen much more on clear themes :

.card-image-container {
    max-width: 500px;
    max-height: 250px;
    overflow: hidden;
    border-top-left-radius: 0.375rem !important;
    border-top-right-radius: 0.375rem !important;
}

Edit:

And same things for rendering in posts on smartphone:

@media (max-width: 1010px) {
    .card.card-preview {
    margin: 20px 0 20px 0;
    width: 100%;
    }
}

[phenomlab]

@DownPW Good point ref the missing radius on image hover - I’ve updated the original post. Good spot !

I’d actually go one step further and change the width to 100% otherwise on the light themes you land up with an odd looking space between the card frame and the image

.card-image-container {
    max-width: 100%;
    max-height: 250px;
    overflow: hidden;
    border-top-left-radius: 0.375rem;
    border-top-right-radius: 0.375rem;
}

[DownPW]

No problem dude, we are beta testers finally, we go back what we can and we propose the corrections if we find them

[phenomlab]

@DownPW thanks. Things look to be pretty stable to me. Haven’t heard from @dave1904 yet though