@Macrow-Willson said in Facebook sso - essentials:
yeah, i tried that too, https://myurl.com:4567 renders the forum inaccessible since it doesn't return encrypted http, obviously.
Not really obviously. The URL in your config.json should be the one you're using publicly. Thus whatever your Apache reverse proxy is configured for. The configuration is used to create the URLs on your site. It has no impact on the actual communication with your reverse proxy.
My hunch is, you also need to remove that port. Because your Apache reverse proxy probably is providing your site over the standard HTTPS port. So it probably is just https://myurl.com. Also don't change anything about your reverse proxy configuration when you change this url parameter. Your reverse proxy still fetches the forum over HTTP at the port 4567. This has nothing to do with the url parameter.
Re: Private Posts
Hi julian, curious for your reply below:
Fairly slim, as it is not in use so there is no incentive to keep it updated. A dedicated forum with stripped down permissions is doable already in core (though you don't get to allow users to reply to their topics only...)
I have tried some but didn't make it possible for user to see only their own posts in a forum. Otherwise I have to make a new plugin, but maybe I don't need to reinvent the wheel
It is possible on the group page itself, for example if you search users on https://community.nodebb.org/groups/gamers it will only search that groups members. The front end doesn't have that option on /search though.
@pichalite said in Category doesnt exist on 1.2.1:
@exodo @torn2 v1.x.x branch is now updated with working composer. Pull again and run upgrade.
Hey I'm having the same problem. I'm up to date on branch v1.x.x but no luck on the error.
Also composer is on 4.2.13 for my site.