I would like to have a plugin which is able to sort the posts with the most likes at the top. I've listed several reasons why I would love this functionality at this post.
I would like to find out if there are more people interested in this functionality, however, unfortunately I am not a programmer. But I might be able to come up with a bitcoin/litecoin bounty for someone which could create this hack for me, and for everyone who wishes to use it.
Hi, just wanted to say that I really really get this - I was reading the about page and was like, hey! this is my life right now!
So I got a fab job as a community manager for phpList, but I was shocked to find that nearly all the tools had no "how to make this awesome" manual. I have seen tools with user level how toos and developer level how too's but no "community manager" level documentation at all. I hope to spend some time this year documenting my experiences with some of these tools from this perspective
Keep up the amazing work with this, the forum is looking amazing, I love how it works! I have put this down as something for us to look into over the year and see about switching Any guides about the process of this would be great
Right now I have a Discourse installed at community.mydomain.com, while I'm waiting on the domain name I want (which may take several weeks).
In the meantime, I'd like to get users on the forum but community.mydomain.com isn't appropriate.
As a temporary solution, I set up a .TK domain name, which IS appropriate, but my question is - will I run into trouble down the road when I switch the .TK to the .COM I'm waiting on?
I.e., will users still be able to log in with their Facebook, Twitter, Gmail credentials, or will, for example, FB think something funny is up? I know normal registrations will still work, but I'm not sure about FB apps and APIs and I'm concerned about creating hassle for users later on.
Also, app.yml has community.mydomain.com set as the domain name. Can this create issues if people register through the .TK?
I just had this error while upgrading to 0.9.9. I am using a multisite setup and from the logs it looks like the first site migrates as expected but the second crashes.
for more fun and laughter within your community, I created a little Easter present for you (and them): a plugin to browse and select Reaction-Gifs of the amazing replygif.net Library in the composer window:
The installation as the usual. From your discourse installation directory, do
cd plugins
git clone https://github.com/ligthyear/discourse-plugin-replygif.git # clone the repo here
cd ..
RAILS_ENV=production rake assets:precompile
Hi guys, we're having some issues getting our reskin/customisation plugin working. @sam asked us to post here so that we can get some help over the weekend because he's heading away. Thanks.
My front end guy has the plugin partially working.
If you have a look at https://github.com/sitepoint/discourse-theme/you can see that we have a plugin.rb file in which we load additional SCSS files. At the end of the file is a comment that includes the content of the Site Customization form field as we use it (with "Do not include standard style sheet" checked). What we'd like to achieve is to be able to call the SiteCustomization API from the plugin and inject the variables from there, rather than having to use the form in the Admin section. Could you please provide guidance on how to do that?
Also, the generated stylesheet file in public/uploads/stylesheet-cache currently combines the styles in a strange order. Most of the styles are applied correctly (i.e. default styles come first, and our override styles are lower in the file), but in the case of e.g. header.scss, the default style come after our override (search for the ".d-header {" rule), which is not desirable, because for example our definition of the header background color is overwritten back to default. How can we ensure that our plugin styles are always loaded after the default styles? It looks like the order is somewhat random now. This issue was already present before we started using the SiteCustomization feature: in the browser's dev tools' Network tab, the our header.css would come up earlier than discourse's default header.css.
I'd like to know if it possible to write a plugin, that would treat specific attachment extensions and present an image for them instead of text link? For example it could be a preview image for PDF file, similar to what Gmail is doing. I'm asking as a developer, but I'm not sure that Discourse API allows that. Are there any examples that can be used as a reference?
I've got discourse running on an internal server at our company but can't for the life of me get email working. In the sidekiq output I get the below error messages.
We've got an Exchange Server so after some googling I installed the ruby-ntlm gem, changed the authentication type to ntlm but I still got the same errors.
Has anyone else got it up and running with exchange/ntlm?
On another note, editing the production.rb file and restarting discourse/sidekiq every time is pretty painful. It would be great if the email setting could be configurable in the app itself.
Got Discourse setup on DigitalOcean with the guidelines on here (great guide btw). However, I never received a confirmation messages, other users also not.
Funny thing is that I can go to the Admin and any test email from Discourse gets sent. So, it is definitely not something with the email settings.
We created an account with the wrong e-mail address, and I clicked the first option after clicking delete user, which was something to the effect of ban username and ip address.
Is there a way to undo this so that the username can be reused, and accounts can be created from our ip address?
Also, from a design perspective, it would be more useful if this was not the first option, but was 2nd or 3rd option to prevent hurried clicks, as in this case.
rake aborted!
fe_sendauth: no password supplied
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:831:in `initialize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:831:in `new'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:831:in `connect'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.2/lib/active_record/connection_adapters/postgresql_adapter.rb:548:in `initialize'
...
What have I done wrong?
I've set up my instance of discourse to use SSO with my own external site for authentication purposes. This is working as expected and I have no issues with it. Getting it set up was easy. Great work!
My goal with using SSO is to always have the users of my discourse forum (1) create their discourse user accounts via SSO'ing via my external site and (2) only use SSO to log on. I also want my external site to be the only place where users can change their email and user name, so I have also set "sso_overrides_email" to true, "sso_overrides_username" to true, and "email_editable" to false. This is all working as expected.
My issue:
The whole notion of invites in discourse (at least as they are currently implemented) doesn't play nicely with discourse as I have set it up. As an admin, moderator, or user with a trust level greater than two, a user can send invites out to any email address. When the link in these invites is used, a user account is then auto-generated for that email on my discourse instance, but this is bad since no corresponding user with that email address is guaranteed to be already created on my external site (that is used SSO).
Solutions?
There are most likely multiple solutions for this, but what would likely be easiest to implement (and totally A-OK for my needs) would be a simple "Disable Invites" checkbox in the admin User settings.
Thoughts?
Thanks!
One last note:
I read on semi-related thread that one could disable invites by enabling "must_approve_users", but that doesn't work in my case for two reasons. (1) When "must_approve_users" is enabled, if a user tries to login via sso for the first time, they are just dropped back on the discourse page and are not logged in. They is no notification that they just had their account created and an admin now must activate there account. (2) For our situation, we don't want to have to activate each and every user. Anyone with an account on our external site should be allowed to have an account on our discourse instance.
A few times now, I've read a topic only to realise a few posts in that it's from match '13 and probably completely irrelevant to the state the engine is now. More so in this forum that since we are in beta, everything changes fast.
I don't know how, but IMO dates should be more visible on "old topics" (perhaps how old could be configured somehow, adding an ageing visual cue, putting the created date near the title only on those topics, or something like that)
Maybe everything is OK, but it's not acting the way I would've expected.
A week ago, someone on my team converted an old WordPress forum into a Discourse forum, and then I got the data from his Discourse install via admin > backup > download, followed by admin > upload > restore on my Discourse install. That seemed to work great. The archive was 600 MB, and took 6 hours to restore.
But now this weekend, we did that process again, to capture more recent posts from the WordPress forum, with the plan to probably go live if the migration went well. But several things have happened differently:
Restore seems to work in minutes, instead of 6 hours. Which means either you guys are really smart and somehow are able to just restore the deltas, or something is wrong.
No logs – just "No logs yet..." with a spinner, or nothing.
Inconsistently logging me out – I wasn't an admin on my teammate's Discourse forum at the time when he backed up, so it sort of would make sense that upon restore, my Discourse install would suddenly stop recognizing me. This would happen, but then... unhappen and I would regain access.
Inconsistent archive sizes – To test if it had really imported all the data, I tried creating a backup and seeing if it was the same size as the archive I had just restored from. But the new backup was 1.1 GB, about twice the size.
Questions:
Is it normal for a 600 MB restore to take just a couple minutes under the above conditions?
Why am I not seeing logs during restores?
What's with the login/admin behavior during restores?
Why might you upload a 600 MB archive, restore from it, backup from it, and see the archive balloon to 1.1 GB?
This file is 891 MB. And after Vagrant works its magic, it goes to 3GB.
This is basically a Linux Ubuntu image, with the necessary dependencies pre-installed for Discourse development:
Ruby
Rails
Postgres
Redis
.. and so forth.
Is there any way we can compact, resize, or otherwise make this VM image smaller so it is quicker and easier to download for folks that want to get started with Discourse development?
891 MB is a lot of downloading before you can get going on Discourse. Would love to make this VM smaller if possible!
On the main topic screen, the Create Topic button (and the "tab" buttons, for that matter) scrolls off with the topics. It would be better if it remained in the band that stays on screen (like the notification, search, etc., toolbar).
Also, the Create Topic button doesn't appear on the thread-reading screen at all.
I'm not sure whether the other buttons should stay on screen. The top band could easily get cluttered. Most (but not all?) appear in the "go to" menu anyway.