NPM page shows me that the latest version is 0.4.0, but on ACP plugins page and even with npm install the latest version is 0.3.4.
I have noticed since some time ago that there is always a delayed version with this plugin.
How to fix this?
[nodebb-plugin-sso-steam] Steam/OpenID register/login
-
@Ezra-Sharp said:
would be cool to get a steam icon or have the ability to link to one, there just a "tick" on the register screen for it atm.
The Steam icon must be customized on your template settings (CSS). FontAwesome doesn't provide the Steam icon in their set. There is an issue on Github requesting this icon: https://github.com/FortAwesome/Font-Awesome/issues/1035
By the way, another issue opened on plugin github project alerted me for one question: Steam users can have special characters on nicknames, witch is not acceptable by NodeBB username validations:
https://github.com/igorprado/nodebb-plugin-openid-steam/issues/4
@julian, @psychobunny, suggestions?
-
How can I replace the icon by an image?
-
@psychobunny said:
awesome
would be pretty cool to see a lot of gaming related forums powered by NodeBB, all thanks to you 
This is exactly what brought me to NodeBB. I am working on a project to create a new gaming site because I became completely disenfranchised with most forum based game sites out there. I find the technologies too static for today's web.
I have been doing great deal of research to find out more about nodebb and all the dependencies and I am somewhat confident of creating a platform to bring forum interaction to modern standard.
-
Has anyone got this working on 0.43? Running into the 404 issue when attempting to go to admin/steam
-
This plugin might need to be upgraded to work with 0.4.x...
-
@julian What does that mean? This is something I'm REALLY looking at and almost a make or break feature.
-
@shinyidol just meas the plugin dev needs to change something in the plugin for it to work with the latest version of nodebb, raise an issue over on github to update it.
-
@a_5mith Thanks
-
Any updates on this? I really want to use NodeDB but this makes it pretty much useless for me. :l
-
@Jurjee Hey, I have time to kill, I'll take a look.
Edit: Ready.
- https://github.com/igorprado/nodebb-plugin-openid-steam/pull/6
- https://github.com/igorprado/nodebb-plugin-openid-steam/pull/7
closed Use "nodebb-plugin-sso-steam" instead #7
-
Wow, that was fast! Thank you very much!
-
@julian tried updating to this and causing my nodebb instance to stop. ideas?
-
@shinyidol the pull request Julian submitted hasn't been committed yet, so it's technically not fixed yet. You've got two options, you can either wait until the plugin developer accepts the changes, or you can fork the plugin and make the changes manually to your forked version. I'm not sure if there's an unwritten rule when it comes to taking over inactive plugins. As the old plugin would still exist.
-
@a_5mith yeah. i did a fork and manually updated and it didn't work
-
I haven't tried it myself but will check it out later today to see if it does work for me.
-
Only the first one (#6) is required, #7 is just a renaming of the module for cosmetic purposes.
You can try to install my fork by running the following:
$ npm install git+https://github.com/julianlam/nodebb-plugin-openid-steam.gitIf at a late date you want to uninstall it:
npm unl nodebb-plugin-openid-steam, or just remove it from the ACP. -
@julian appreciate the help, but not working. Running 0.43. Removed all previous versions. Then ran the npm command above. Clicking on Steam still takes to 404 error.
-
@shinyidol Just want to confirm it is installed:
npm ls nodebb-plugin-openid-steam? -
@julian i think so.
[email protected]:~/nodebb# npm ls nodebb-plugin-openid-steam
[email protected] /root/nodebb
[email protected] extraneous (git+https://github.com/julianlam/nodebb-plugin-openid-steam.git#3c81e2c58720bd111d1949cadda1e602834616dc)
npm ERR! extraneous: [email protected] /root/nodebb/node_modules/nodebb-plugin-openid-steam
npm ERR! not ok code 0 -
@shinyidol Ugh, sorry about that, silly mistake. Please re-install.
When you re-install and run
npm lson that package again, the git hash should be:ca32b1a6e87b0682572c2cbf4400a17e42e1f4a4
