I want to escape by default, to prevent accidental XSS. If you intentionally want to allow scripts then you should use double curly brackets
I think its something I would rather break today than worry about it in future
v0.3.0 Final Round of Testing
-
Just a heads-up that any non-essential issues have been bumped to v0.3.1, and we've begun "live fire" testing of v0.3.0 on this community.
Barring anything catastrophic, you should see v0.3.0 released sometime
tomorrowSunday/Monday.For those of you here running edge builds of NodeBB (which I imagine is almost all of you), feel free to upgrade (
git pull && ./nodebb upgrade) and test. NodeBB should not crash. If it does, send us the error log/stack trace.Note: At first, you may see stuff like this being logged:
warn: [socket.io] Unrecognized message: event:enter_room warn: [socket.io] Unrecognized message: reconnected warn: [socket.io] Unrecognized message: api:updateHeader warn: [socket.io] Unrecognized message: event:enter_room warn: [socket.io] Unrecognized message: reconnected warn: [socket.io] Unrecognized message: api:updateHeader warn: [socket.io] Unrecognized message: api:meta.rooms.enter warn: [socket.io] Unrecognized message: api:meta.reconnected warn: [socket.io] Unrecognized message: api:meta.updateHeaderThis is normal -- some of your users are still running old client-side scripts. They just need to refresh.
Hopefully, nobody will have to clear their cache. NodeBB should be smart enough to trick your browser into downloading the new client-side scripts (fingers crossed).
-
Great. Only 1 little problem: nothing loads
On chrome console getting 2 errors:Uncaught ReferenceError: require is not defined
Uncaught ReferenceError: templates is not definedP.S. cache is cleared
-
@julian Is there a full change list somewhere?
-
@Chris https://github.com/designcreateplay/NodeBB/issues?milestone=13&page=1&state=closed is probably your best bet
-
Great job, all you devs.
The new composer box looks much better, though it could still use some styling.
Also, when I click on the Preview button, it doesn't show any content. And it would be good to move the Discard and Submit buttons closer to the middle of the box. But this is a good start.
-
So it looks like I am the only one who has problems
Well, as always, d'oh -
Hahaha... even a day before the next version lands, we're pushing new features (ninja)
That's just how we roll here.
-
That's the way it should be.
Talking about new features, how about custom pages, like a plugin that makes it possible to add a blog page, so I can ditch WP.
-
Ah well, the cool thing about blogs is that you could theoretically make yourself your own forum, and give yourself write access (which will automatically not allow anybody else to create topics). Then blog to your heart's content
Other than that... perhaps look at plugin-42 or plugin-static-page?
-
This post is deleted! -
Just updating the original post -- the landing of 0.3.0 has been delayed until Sunday or Monday. Not to worry, nothing catastrophic happened, we just don't want to release software that we're not 100% about
-
To add to @julian we made some fixes and changes today Commits of 18th January. Would like to test them out a bit before releasing 0.3.0.
-
I've never been a fan of Release early, release often just for the heck of it. That's another way of saying, take your time. Give us something that's ready for production.
-
So many changes
-
-
nah, we got you @julian, keep the QQ coming
-
When should we expect 0.3 to be out out? Wanting to update but if the "final" 0.3 is due soon I may hold off.
-
Just hold off for another day. We're wrapping up some last minute changes
As always, before you update, make sure you have a recent backup!!
