If you're paying me to learn angular too, sure I have really limited experience, just for messing about no real-world experience.

This is already found and reported.

agreed, please @administrators make it happen

Maybe you should add a vagrant section to the docs A lot of people use vagrant, potentially they just don't know this solution exists yet

This has been available in core for a while now. You can set it on the category page.

Woops. Experimental paginator that I should have removed. The new mobile menu isn't really compatible with it at all #4 this has been raised recently, my suggestion was to remove read notifs from the mobile menu, or add a new badge like the chat section does #5 might be a different bug. Notifs don't load if you slide to open the menu

@apilorusso Thanks, Actually just got things how I wanted not to long ago. Basically, I made the category cards a hover and made them swap out the title/description with the latest post/preview. Let me know what you think .. Humm.. seems I can't include a link it thinks it's spam.. Check out my profile for my forum

Cool @drew look forward to it, let me know if I can be of any help.

Quite Worth It Very Nice

I think Leagues a bit ropey, but I live in Leeds now, so I'm surrounded by Leeds Rhinos supporters. I went to work once wearing my Leicester Tigers hoody, that was a long day...

Yeah its on my todo for tjs 1.0

This would be nice, for Facebook, Google and Twitter. Something like adding the Current URL to a variable and then loading that variable after you have logged in. I don't know how all that works but, would be nice. Or would it have to be in a cookie or something.. bla beyond me

The nbbpm checks new packages that get added to npm, so if you unpublish your package, we won't know. Best bet would be to keep the package there so users on old NodeBB versions can still install it, but put an nbbpm.indexed = false in package.json, so when it comes through from npm, nbbpm will know to remove it from the index.

@henrywright said: this idea wouldn't work if > 1 line change I was referring to my idea of making a manual 1-line change to the theme core at the point of each upgrade. That would avoid you having to use Git to merge in new commits each upgrade. Again, although not a clean way of working, it sounds like it'll be easier than what you're currently doing.

@psychobunny said: This is how you upgrade? This looks like how I design XD Explains how you forget to push fixes to this place.

@baris thanks. I realised there's some issues with redactor munging the data. When code is insered inside a <pre/> block, switching between HTML and WYSIWYG views will munge the content to HTML entitites. You can recreate this issue on this page: http://imperavi.com/redactor/examples/typography/ Switch to code view and add some HTML inside the <pre/> block. I entered: <p>test</p> Switch to WYSIWYG and back to code and it has been replaced by: &lt;p&gt;test&lt;/p&gt; This breaks the ability to parse that code later with syntax highlighters. I've raised it with Imperavi.

I use a slightly modified version of lavender for my site, and up until now that's been quite a headache. I've had to maintain an entire theme which is just a fork of lavender and constantly merge in changes just so I can have one template file be slightly different. I was wondering if this is now something I can resolve with the baseTheme parameter? If MyTheme has a baseTheme of nodebb-theme-lavender, which in turn has a baseTheme of nodebb-theme-vanilla does that mean that I can change my repo to just be the one altered file? I remember in the past I tried inheritance and found it didn't work.

It was fixed, but the forum was not updated. Now is. Over and out.

@psychobunny issues raised: https://github.com/NodeBB/NodeBB/issues/3468