New Opera Forums launched

emniss

emniss

Is there a chance to make Opera configuration links like...

opera://settings/?search=WebRTC

...automatically clickable by the forum software?

amatczak

amatczak Opera @emniss

@emniss Not easily - there's no confg option for that but everything should be possible with some source code modifications.

I am worried about security implications though. Can't such links be malicious in a way that a less tech-savvy user gets tricked into changing something with just one click on such link?

sgunhouse

sgunhouse Moderator Volunteer

Can you even do that? I thought all internal links had to be typed or pasted into the address bar - that even if a link was clickable the browser would ignore it if it is in an external page.

burnout426

burnout426 Volunteer @amatczak

@amatczak the opera protocol used to be supported on the iterations before last I think. There weren't any problems.

I would think that there'd be a list in the code somewhere or in config for the supported protocol names like ftp, https, https, mms, rtps, mailto, magnet etc., but just guessing.

I would also imagine then that the markup generator (maybe in the markdown code/config even) would use that list and the linkifier for plain-text URLs would too. But, just assuming / hoping.

burnout426

burnout426 Volunteer @sgunhouse

@sgunhouse said in New Opera Forums launching soon!:

Can you even do that? I thought all internal links had to be typed or pasted into the address bar - that even if a link was clickable the browser would ignore it if it is in an external page.

Don't think I've checked with new Opera.

emniss

emniss

Opening a new topic shouldn't be enabled on the subcategories page of "Opera for computers":

https://forums.opera.com/category/5/opera-for-computers

That's looking like a mess.

sgunhouse

sgunhouse Moderator Volunteer

Their decision. They wanted general (platform-independent) Opera for desktop questions there.

leocg

leocg Moderator Volunteer @emniss

@emniss It makes sense that non-plataform specific issues are discussed under 'Opera for Computers'.

emniss

emniss

In my opinion it would make much more sense to open a sixth subcategory in "Opera for computers" for non-platform specific issues than discussing them on the subcategories page itself.

julianlam

julianlam

@amatczak said in New Opera Forums launching soon!:

@burnout426 Let us know if you find anything! We're aware of this template and indeed it might be possible to tweak it so that it links straight to the post (would be my preferred behaviour too)

Hi, Julian from NodeBB here. Glad you're on board

In a pinch you can edit the template in the ACP to fix the link. However it does sound like a bug so we'll address it as well.

julianlam

julianlam @amatczak

@amatczak @burnout426 This is now resolved:

https://github.com/NodeBB/NodeBB/issues/6027

barisu

barisu

Hi guys,

Baris from NodeBB here, glad to see Opera is using NodeBB!

We just fixed the issue with the reply notification email not pointing to the correct post. https://github.com/NodeBB/NodeBB/issues/6027. It will be available in our next release.

If you discover more issues feel free to open issues on our github tracker. https://github.com/NodeBB/NodeBB/issues

Thanks.

burnout426

burnout426 Volunteer @julianlam

@julianlam @barisu

Thanks very much!

I looked at the diff too to see how you fixed it. Is there a list of supported template variables somewhere?

barisu

barisu @burnout426

@burnout426 not everything is available everywhere, for this particular email template the available variables are here https://github.com/NodeBB/NodeBB/blob/master/src/topics/follow.js#L256-L265. Some common variables are passed to all email templates those are listed here https://github.com/NodeBB/NodeBB/blob/master/src/emailer.js#L89-L97

burnout426

burnout426 Volunteer @barisu

@barisu Thanks.

burnout426

burnout426 Volunteer

@amatczak Looking at the diff, it looks like a super-safe patch.

burnout426

burnout426 Volunteer @emniss

@emniss said in New Opera Forums launching soon!:

Opening a new topic shouldn't be enabled on the subcategories page of "Opera for computers":

https://forums.opera.com/category/5/opera-for-computers

That's looking like a mess.

It is weird / different. If anything, I'd expect it to just be all the threads from the subcategories mixed together.

However, it's not a big deal for me and the current way it's set up is fine with me.

amatczak

amatczak Opera @burnout426

@burnout426 said in New Opera Forums launching soon!:

@amatczak Looking at the diff, it looks like a super-safe patch.

Applied manually already. Tell me if it works

burnout426

burnout426 Volunteer @amatczak

@amatczak Looks like it works so far. I'll test more on a notification for a post that isn't the last post in the thread though and let you know.

burnout426

burnout426 Volunteer @amatczak

@amatczak said in New Opera Forums launching soon!:

@burnout426 Yes, we're aware of that - redesigned email templates were only introduced less than a week before the roll-out, with 1.6.0 upgrade of NodeBB, and we simply didn't have time to style the email template like we'd like. It's on our todo list already. Be sure that after we're done it will look much better (the giant pic on top is a bit of an eyesore indeed )

The default notif_post template has a lot to it. Also, all the HTML comments are emitted in the outgoing email source. So, in playing around with things, I'm starting with this instead:

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title></title>
    </head>
    <body>
        <p>{intro}</p>
        <blockquote><p>{postBody}</p></blockquote>
        <p><a href="{url}/post/{pid}">Click here to read the full reply</a>.</p>
        <p>[[email:closing]]</p>
        <p>{site_title}</p>
        <p>[[email:notif.post.unsub.info]] <a href="{url}/user/{userslug}/settings">[[email:unsub.cta]]</a>.</p>
    </body>
</html>

In the source of the outgoing message, there will be a style tag added above the doctype by the emoji plug-in. I turn it off and restart the server before testing to make sure the markup in the source of the outgoing mail is correct.

In short, it might make sense to start with a simple template and go from there; adding back anything (like some of the meta tags) if needed.