[nodebb-plugin-link-preview] Rich Embeds and Link Previews

[julian]

It's bundled but not activated, perhaps that's what you need to do?

[mschwartz]

@julian

I do not see it under installed plugins…

[mschwartz]

[mschwartz]

I finally found and installed it and it works mostly.

It doesn’t recognize https://m.youtube style URLs, so I have to manually edit the m. part out.

That’s the only embed I tried.

[mschwartz]

https://m.youtube.com/watch?v=sOW8ONwzL7Y&pp=ygUgc29mdGJhbGwgc2xvdyBwaXRjaCBoaXR0aW5nIHRpcHM%3D

(No embed!)

[crazycells]

hi @julian , iframely was showing pdfs as preview, so you did not have to click the page to read on another tab, you could just read the pdfs in the forum... Can this plugin be expanded to include pdf previews?

[crazycells]

I do not know if it is possible, but I still think it would be very cool to have a pdf previews in the forum, so users do not have to leave the forum to check the pdf documents...

[darkpollo]

@julian Just to confirm that this plugin did not come bundled when I installed it.
I found and installed and activated with no issue, but it was not part of the basic install.

[julian]

@darkpollo you're right, the plugin isn't bundled with new installs

[benyto]

@julian works fine, thanks
would be nice to have links opened in new tab or configurable at least

[julian]

thanks for commenting @benyto . The plugin follows NodeBB's behaviour in not modifying anchor target. The end user can ctrl-click the link to open in a new tab, shift-click to open in new window, etc.

[Paweł]

I installed the plugin via dashboard plugins.

NodeBB v3.10.3

I did a rebuild, the plugin appears, but saving settings does not work.
In addition, I have this error in the console: “admin.min.js?v=o50k63atqko:1 error loading admin/plugins/link-preview
Error: Cannot find module './plugins/link-preview'”

What did I do wrong?

[nhl.pl]

What kind of hosting? Some container based and one click installs do not support updating plugins from dashboard. Please try to do the same thing from command line.

[Paweł]

I have VPS, and other plugins works fine, I have only problem with this. Save button dosen't work in plugin settigns.
/admin/plugins/link-preview

When I click "Save changes"/"Zapisz zmiany" - nothing happen, and after refresh page changes on checkboxes are gone.

[julian]

@Paweł hello again, when you run ./nodebb build, do you see any errors?

[Paweł]

Hello! I have one error, and the build is successfully

2024-12-02T14:00:40.772Z [4567/43946] - info: [build] admin control panel styles  build completed in 5.442sec
2024-12-02T14:00:40.773Z [4567/43946] - info: [build]                  templates  build started
2024-12-02T14:00:42.294Z [4567/43946] - info: [build]                  templates  build completed in 1.521sec
2024-12-02T14:00:42.296Z [4567/43946] - info: [build]                  languages  build started
2024-12-02T14:00:47.214Z [4567/43946] - info: [build]                  languages  build completed in 4.918sec
2024-12-02T14:00:47.216Z [4567/43946] - info: [build] Bundling with Webpack.
315 assets
788 modules

ERROR in ./build/public/scripts-client.js 1960:5
Module parse failed: Unexpected token (1960:5)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| });
|
> ;CC0 1.0 Universal
|
| Statement of Purpose

webpack 5.94.0 compiled with 1 error in 19554 ms
2024-12-02T14:01:07.713Z [4567/43946] - info: [build] Asset compilation successful. Completed in 41.304sec.

[baris]

@Paweł check your plugins, looks like one of them is included a non-js file in the scripts block of its plugin.json

[Paweł]

@baris How should I find it in the admin panel or in the source code on the server?

Edit:
Ok I found the problem! grep -r ";cc0 1.0 universal" - there was problem with depreacted plugin nodebb-plugin-html5videoplayer - I removed this and know everythong works fine!

Thanks a lot for your quick help! This is my first time using NodeBB.

[baris]

@Paweł no problem, yeah you can grep for stuff in the node_modules directory to find the culprit. Or you can disable plugins one by one. ./nodebb plugins command shows active plugins.