@baris I'm really trying to stick to actual releases (looking at github it doesn't look like 1.17.1 has been officially blessed yet). However, staying on v1.17.0 and bumping the socket.io and socket.io-client versions seems to have done the trick!

@baris d'oh! I could have sworn that I'd updated them all to latest. Thanks.

@pitaj hmm...looking more closely at this...updating the dependencies might do it. But if not, that one seems to use the Amazon published SDK so it should definitely work. Thanks!

The only schema change in 1.14.0 is https://github.com/NodeBB/NodeBB/blob/master/src/upgrades/1.14.0/fix_category_image_field.js, at worst you would have broken category background images.

This was reported: https://github.com/boomzillawtf/nodebb-plugin-youtube-embed/issues/9 I can't reproduce, but the report says they get an error when navigating to the settings in the admin area (NodeBB 1.7.5, youtube-embed v0.6.7). Does anyone have an idea about what's going on here? Unable to load template: admin/plugins/youtube-lite (anonymous) @ ajaxify.js:333 (anonymous) @ require.js:7 (anonymous) @ require.js:23 y @ require.js:6 emit @ require.js:23 (anonymous) @ require.js:11 y @ require.js:6 v @ require.js:11 onScriptError @ require.js:30 require.js:7 Uncaught Error: Script error for "/assets/templates/admin/plugins/youtube-lite.js" http://requirejs.org/docs/errors.html#scripterror at F (require.js:7) at HTMLScriptElement.onScriptError (require.js:30) F @ require.js:7 onScriptError @ require.js:30 ajaxify.js:333 Unable to load template: admin/plugins/youtube-lite (anonymous) @ ajaxify.js:333 (anonymous) @ require.js:7 (anonymous) @ require.js:23 y @ require.js:6 emit @ require.js:23 w @ require.js:12 (anonymous) @ require.js:12 y @ require.js:6 w @ require.js:12 (anonymous) @ require.js:13 y @ require.js:6 C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:13 setTimeout (async) C @ require.js:13 (anonymous) @ require.js:26 setTimeout (async) g.nextTick @ require.js:32 a @ require.js:26 requirejs @ require.js:32 ajaxify.loadTemplate @ ajaxify.js:332 (anonymous) @ benchpress.js:163 a @ benchpress.js:162 (anonymous) @ benchpress.js:184 (anonymous) @ benchpress.js:77 e @ benchpress.js:76 l @ benchpress.js:183 e @ benchpress.js:222 d @ ajaxify.js:185 (anonymous) @ ajaxify.js:98 success @ ajaxify.js:317 l @ jquery.js:3268 fireWith @ jquery.js:3398 c @ jquery.js:9305 (anonymous) @ jquery.js:9548 XMLHttpRequest.send (async) (anonymous) @ VM7656:1 send @ jquery.js:9600 ajax @ jquery.js:9206 ajaxify.loadData @ ajaxify.js:291 ajaxify.go @ ajaxify.js:86 n @ ajaxify.js:362 (anonymous) @ ajaxify.js:413 dispatch @ jquery.js:5183 g.handle @ jquery.js:4991 require.js:7 Uncaught Error: Script error for "/assets/templates/admin/plugins/youtube-lite.js" http://requirejs.org/docs/errors.html#scripterror at F (require.js:7) at HTMLScriptElement.onScriptError (require.js:30)

@PitaJ said in Bookmarks / Favourites breaking change 1.2: How do you recommend this be done? If you want a changelog, you can look at the milestone on GitHub. But milestones only cover issues. There iare of course lot of changes and addition that arent referenced on issues. There were some helpful topics of breaking changes on the past with a little explanation. I guess a topic with centralized information would be nice for 1.2 1.3 1.4 at least updates ( including new or uptades hooks explained + breaking changes on plugins explained + breaking changes on themes explained + a simple explanation of new features) It doesnt need to be all changes just important things Please remember that not every body know to code but with some little explanations and documentation some of us can keep runnin and doing small fixes and learning and improving nodebb

@teh_g you can use n to install a later version of Node if you want. Look up "n install NodeJS" it's super easy.

I'm sure he's still there. Nothing wrong with forking though, you could always merge later.

@exodo said in Upvote Notifications: working without core modifications? Yep. Only lightly tested so far (but based on my previous code that had automated tests written). Next I'd like to figure out how to make automated integration tests for plugins.

sent PR to hide setting if in-topic search is not available

This is growing and becoming a stylish front end. v0.3.0: [image: afM5yZ5.png]

@julian It means that I can test my plugin with nodebb actually firing hooks for it.

@baris said in Bad reply links: Yup let's test this. Excellent. /MrBurns

Submitted a pull request: https://github.com/NodeBB/NodeBB/pull/4591

Facing the same error. How does Reset Lockout Help?

@NedFodder said in Ignoring individual threads: @azeus It was added after the latest stable version (v1.0.3). It looks like it will be officially released in version 1.1.0. If you don't want to wait, you can upgrade to the latest version on the master branch. See instructions and warnings here. Thank you. I'm running on 1.0.3 and some users just asked about this feature...

Yeah, we will add an option like Only display to Admin for global mods as well. https://github.com/NodeBB/NodeBB/issues/4344

The main point here is that every time we modify the url to add the post index, it is a new resource, even though in reality, the end result is really the same. We can't fault the browser for adhering to the spec, though I honestly don't know if we can resolve this one. Here we change the url as you are scrolling, as opposed to recalculating the url when scrolling is finished, but besides that...