@rodrigofarcas wrote:
Trying to export my 160.000 userbase, and just got a message saying "user export failed, contact staff member"
Could not find anything related to this on logs.
Any ideas?
Posts: 1
Participants: 1
@rodrigofarcas wrote:
Trying to export my 160.000 userbase, and just got a message saying "user export failed, contact staff member"
Could not find anything related to this on logs.
Any ideas?
Posts: 1
Participants: 1
@Maestra_Powers wrote:
Hey. I disabled "allow uncategorized topics" on my forum, but Uncategorized category won't go away. Is this a bug?
Posts: 4
Participants: 3
@Maestra_Powers wrote:
So I enabled "show subcategory list" feature, I like Discourse this way much better. But main category also shows topics from all subcategories - why?
Shouldn't it show topics from main category only? Like this - this makes much more sense to me. If I disable "show subcategory list" feature, I can view topics placed in main category only, like this:
But if I enable it - I can't. I see only one way to separate topics in root category now - place them in another subcategory. But that's one extra subcategory and my users doesn't used to this stricture.
My question - if "show subcategory list" enabled, why don't you guys add "Latest" view for category and all subcategories here? Like on disabled "show subcategory list" type of view.
This button should show latest for this category and all subcategories, not category itself - it should show only topics placed in this root category. Please make this kind of view possible via settings in admin panel. Till then I'll have to deal with extra subcategory structure.
Posts: 6
Participants: 3
@Maestra_Powers wrote:
I'm talking about this moderator's tool.
I need to move all topics from one category to another now, so do I need to click on each checkbox for this? Or is there a faster way? I hoped there's
Shift+click
thing, but nope. Maybe there's another hotkey for this that I don't know?
Posts: 4
Participants: 3
@Shyatic wrote:
I think the issue for myself, and many others, is that my site is relatively small; docker support isn't really there and we really just get access to FTP to upload file structure. I'm not expecting that tomorrow that this becomes a reality, but the vast majority of shared hosts (for smaller sites like my own) don't offer expanded capabilities to really support Discourse.
Just curious if there are thoughts around this (I'm not advocating for a specific way!) to accomodate the many people who have the ability to set up Wordpress, but then aren't able to expand that use to Discourse.
Look forward to your reply!
Posts: 2
Participants: 2
@tobiaseigen wrote:
I've had a request for the ability to add tags to topics when posting by email. This could work by adding a line as follows starting with
tags:
and then a comma separated list.tags: tag1, tag2, tag3
I can see potential for difficulty, e.g. because there is no autocomplete people won't know tags that are already being used and create duplicates, but I also think it can be quite powerful and help people to indicate organization they'd like without having to log in - and in my community many people just want to stay in their email.
Posts: 1
Participants: 1
@adrian2 wrote:
Thanks to Discourse support for addressing this topic previously. We have one more example of duplicate content on the home page that should probably be addressed. Maybe this belongs on the same thread, but it has since been closed.
We have duplicate content at the following URLs:
http://forum.learntomod.com/latest?no_definitions=true
and
So my guess is that we would just need a canonical href to the home page that only appears on the home page.
Posts: 11
Participants: 4
@rsaenz wrote:
I'm in the process of moving a Drupal-based forum to Discourse. In the Drupal forum images are attached to the topics and comments, and displayed at the end. I thought the simplest way to replicate this would be just add the image links to the body of the post when importing into Discourse.
The image links show up OK, but they aren't oneboxed. If I edit the post, the images show up oneboxed in the preview pane, and if I save the post with no changes the images are now oneboxed.
Any suggestions for getting those images oneboxed during the import itself?
Posts: 3
Participants: 2
@Luke wrote:
So, I've been trying to setup multisite, and the only problem I have come across is this one:
I, [2015-02-28T02:37:11.302090 #36] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' URGENT: FATAL: password authentication failed for user "discourse" FATAL: password authentication failed for user "discourse" Failed to initialize site default URGENT: FATAL: password authentication failed for user "discourse" FATAL: password authentication failed for user "discourse" Failed to initialize site secondsite URGENT: FATAL: password authentication failed for user "discourse" FATAL: password authentication failed for user "discourse" Failed to initialize site thirdsite rake aborted! PG::ConnectionBad: FATAL: password authentication failed for user "discourse" FATAL: password authentication failed for user "discourse" /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `initialize' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `new' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `connect' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:568:in `initialize' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `new' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `postgresql_connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:435:in `new_connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:445:in `checkout_new_connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in `acquire_connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:351:in `block in checkout' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:350:in `checkout' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:541:in `retrieve_connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_handling.rb:113:in `retrieve_connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/connection_handling.rb:87:in `connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:916:in `initialize' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:814:in `new' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:814:in `up' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/migration.rb:792:in `migrate' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>' Tasks: TOP => db:migrate (See full trace by running task with --trace) I, [2015-02-28T02:37:16.868844 #36] INFO -- : FAILED -------------------- RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 24367 exit 1> Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]} ef235298bb7296e50a9ca14a1a9ac850281f383b0c39b8e08eb56d888c17822b FAILED TO BOOTSTRAP
data.yml
# A container for all things Data, be sure to set a secret password for # discourse account, SOME_SECRET is just an example # templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/sshd.template.yml" - "templates/cron.template.yml" expose: - "5432:5432" - "6379:6379" - "2221:22" params: db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to 1/3 of the memory you wish to allocate to postgres ## on 1GB install set to 128MB on a 4GB instance you may raise to 1GB #db_shared_buffers: "256MB" env: # ensure locale exists in container, you may need to install it LANG: en_US.UTF-8 volumes: - volume: host: /var/discourse/shared/data guest: /shared - volume: host: /var/discourse/shared/data/log/var-log guest: /var/log # TODO: SOME_SECRET to a password for the discourse user hooks: after_postgres: - exec: stdin: | alter user discourse with password 'blahblah'; cmd: su - postgres -c 'psql discourse' raise_on_fail: false # Craftd hooks: after_postgres: - exec: sudo -u postgres createdb craftd_discourse || exit 0 - exec: stdin: | grant all privileges on database craftd_discourse to discourse; cmd: sudo -u postgres psql craftd_discourse raise_on_fail: false - exec: /bin/bash -c 'sudo -u postgres psql craftd_discourse <<< "alter schema public owner to discourse;"' - exec: /bin/bash -c 'sudo -u postgres psql craftd_discourse <<< "create extension if not exists hstore;"' - exec: /bin/bash -c 'sudo -u postgres psql craftd_discourse <<< "create extension if not exists pg_trgm;"' hooks: after_postgres: - exec: sudo -u postgres createdb persia_discourse || exit 0 - exec: stdin: | grant all privileges on database persia_discourse to discourse; cmd: sudo -u postgres psql persia_discourse raise_on_fail: false - exec: /bin/bash -c 'sudo -u postgres psql persia_discourse <<< "alter schema public owner to discourse;"' - exec: /bin/bash -c 'sudo -u postgres psql persia_discourse <<< "create extension if not exists hstore;"' - exec: /bin/bash -c 'sudo -u postgres psql persia_discourse <<< "create extension if not exists pg_trgm;"' root@discourse:/var/discourse#
web_only.yml
# IMPORTANT: SET A SECRET PASSWORD in Postgres for the Discourse User # TODO: change SOME_SECRET in this template templates: - "templates/sshd.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" expose: - "80:80" - "2222:22" params: ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed env: LANG: en_US.UTF-8 ## TODO: How many concurrent web requests are supported? ## With 2GB we recommend 3-4 workers, with 1GB only 2 UNICORN_WORKERS: 4 ## TODO: configure connectivity to the databases DISCOURSE_DB_SOCKET: '' #DISCOURSE_DB_USER: discourse DISCOURSE_DB_PASSWORD: blah DISCOURSE_DB_HOST: 172.17.42.1 DISCOURSE_REDIS_HOST: 172.17.42.1 ## ## TODO: List of comma delimited emails that will be made admin and developer ## on initial signup example 'user1@example.com,user2@example.com' DISCOURSE_DEVELOPER_EMAILS: 'miley.cyrus@instagram.com' ## ## TODO: The domain name this Discourse instance will respond to DISCOURSE_HOSTNAME: 'discourse.example.com' ## ## TODO: The mailserver this Discourse instance will use DISCOURSE_SMTP_ADDRESS: blahblahsmtp.com # (mandatory) DISCOURSE_SMTP_PORT: 587 # (optional) DISCOURSE_SMTP_USER_NAME: babydaddy@gmail.com # (optional) DISCOURSE_SMTP_PASSWORD: blahblahsecret # (optional) DISCOURSE_SMTP_AUTHENTICATION: login ## ## The CDN address for this Discourse instance (configured to pull) #DISCOURSE_CDN_URL: //discourse-cdn.example.com volumes: - volume: host: /var/discourse/shared/web-only guest: /shared - volume: host: /var/discourse/shared/web-only/log/var-log guest: /var/log #Use 'links' key to link containers together, aka use Docker --link flag. links: - link: name: data alias: data ## The docker manager plugin allows you to one-click upgrade Discouse ## http://discourse.example.com/admin/docker hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone https://github.com/discourse/docker_manager.git #multisite hooks: after_code: - file: path: /var/www/discourse/config/multisite.yml contents: | secondsite: adapter: postgresql host: 172.17.42.1 database: craftd_discourse username: discourse password: blah pool: 25 timeout: 5000 db_id: 2 host_names: - discourse.craftd.net - forums.craftd.net thirdsite: adapter: postgresql host: 172.17.42.1 database: persia_discourse username: discourse password: blah pool: 25 timeout: 5000 db_id: 3 host_names: - forums.persian-world.com - forums.persian-world.comt ## Remember, this is YAML syntax - you can only have one block with a name run: - exec: echo "Beginning of custom commands" ## If you want to configure password login for root, uncomment and change: #- exec: apt-get -y install whois # for mkpasswd ## Use only one of the following lines: #- exec: /usr/sbin/usermod -p 'PASSWORD_HASH' root #- exec: /usr/sbin/usermod -p "$(mkpasswd -m sha-256 'RAW_PASSWORD')" root ## If you want to authorized additional users, uncomment and change: #- exec: ssh-import-id username #- exec: ssh-import-id anotherusername - exec: echo "End of custom commands" - exec: awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF;}'
Please help!
At first I forgot to put the links: in, but even after that it still refuses to work.
Posts: 6
Participants: 3
@terraboss wrote:
Continuing the discussion from Treat all links as target_blank?
Hi,
I'm using some categories for discussing / viewing pdfs (scientific reviews). I'd like to prevent Discourse / my Safari desktop browser from putting each file into my download folder. The pdf should be viewable in the current tab/window. How can I set this?In case of visiting Discourse via iPad or any other kind of mobile device, it's just working fine by design. But those screen resolutions are sometimes too low. Any ideas? CSS snippets?
I found this, but I don't know how to set this globaly:
Big thanks so far and
wish you all a pleasant weekend
Posts: 1
Participants: 1
@gingerman wrote:
Subcategories which are private has problems in the UI. I tried both the bar and box style for categories. I guess we need to move the lock symbol to the end instead of the front.
Posts: 2
Participants: 2
@badevguru wrote:
I have been finding many times that I have read something early in the day that I later want to reference but cannot necessarily figure out how to get back to that topic. I often do this when scanning through top and new listings, or when weaving through search results. It would be very useful to be able to see your history of read topics which would simply show a row by row list of
Date/Time Read| Topic Name | Author| Minutes spent reading
Posts: 4
Participants: 4
@badevguru wrote:
Continuing the discussion from Forum categories as social isolation, not as information organization:
There have been tons of discussion about how to organize large forums around categories and sub categories, the use of tags for organization and the like. As I have been laying out a re-organization of my forums it occurred to me that perhaps using Categories as a first class organizational tool is the problem. As evidence I'll point out that the recommendation is to have new forums focus on showing a flow of latest topics as the landing page instead of presenting a category view. I suggest that as Discourse is attempting to revamp the concept of forums, we have taken one of the constructs from the forums and that construct is holding us back.
I propose that it would make a much more engaging reading experience if we embrace the topic as king and organize using related topic hierarchies. And yes, it does feel a little list server like, but perhaps merging the best from both concepts would be good thing.
I imagine changing the dynamic so that instead of closing topics and producing tons of similar short lived topics, that we instead embrace keeping the topic open and allowing the discussion to keep going thus reducing the number of topics that are in play. As the discussion hits a related branch, we use the reply as related topic feature to organize the discussion.
Discourse already has the tools to do this today.
Here is what I envision:
I have a forum that I am setting up to discuss future cars:
discourse.futurecars.org
When you go there you get the top topics which look something like this, and when you click on the topic you go in to the normal discourse infinite scroll of the topic. However, there is also a related topic indicator that lets you see topics that were intentionally branched as sub topics. Sub topics vs Sub Categories.
Your initial landing page to the forum might look like this, threaded topics... not threaded posts:
Autonomous Cars (1.2k posts)
The Google Car (400 posts)
- Google innovative lidar approach (20 posts)
- The Apple Car (123 posts)
- Policy Debates (600 posts)
Manufacturing Improvements (3.1k posts)
- Manufacturing Hurtles (440 posts)
- Policy Debates (12 posts)
And you can let the branching of the topic happen organically with moderators doing the pruning and shearing as needed to keep things focused.
I could then see a concept like tags working more on the post level than the topic level.
As a user, I have already setup a notification to a topic, the sub topics inherit that notification. But I can always then change that notification settings if I decide that sub topic is too fringe for my interest.
Just a thought. But something I think might have legs...
Posts: 3
Participants: 3
@meglio wrote:
Our use case: sharing is not easy with Discourse
Here is why
- Cannot locate
share
buttonLots of users do not understand where to click to share what they read while they read (not when they has finished their reading).
It is known that while a reader goes through some good content, they have that "share it now" feeling a few times in between, not just at the end. What's more, they might not even get to the end.
While the
Share
button might fit well into the design and be sufficient for some...
... it is non-functional and useless for our community.
We're building a goat farmers community where members have a very basic level of knowledge about how to use Internet, not to say they're located in Ukraine, which is below average "internet usage fluency", so our members:
- DO NOT understand what this image means
- DO NOT realize where it's possible to share
- DO NOT know where to click to get that url to share or email
Yet they keep asking me: how do we share? It's obviously counter-intuitive, at least in our case.
I have to explain in detail and make screenshots, and all I hear afterwards is "why so complicated"?
When I see a "Tweet" button it's straight - if I click it I tweet it.
If I see a "Share" button, I don't think about Twitter, I think about sharing. So one more thing to process in my head, plus one more click before I reach that Tweet button.-
Share
is not visible at all timesFor those long articles, you won't see the
Share
button until you read to the end of the article. What if it's 1800 words? I miss that opportunity to let users share as soon as they feel they want to.-
Share
button cannot be fine-tunedNot everyone would do this, but moderators would like to embed
Tweet this
button when writing 'How-tos', roundups etc - just in front of a citation that stands out.For example, Twitter allows for so many configuration parameters, like default hashtag, default text etc: https://dev.twitter.com/web/tweet-button
As a result, I'm constantly losing almost every opportunity to let good articles written by mods be spread in social networks by sharing means.
Propositions
- Make share buttons configurable (i.e. default share text, hashtag for twitter, ...).
- Allow share buttons to be generated in tools like Twitter Button Resource Page and then embedded right into the post text. For this to happen, an admin would need to embed the
<script>
part of the sharing functionality into the piece, and let authors embed the<a>
part of the sharing button. Currently it does not work as javascript does not pick up the<a>
s on the fly.- Allow for share buttons to be placed on the side, and not hidden under the
Share
button.- Add a button into the toolbar that would allow to insert a
Share button
and tweak its parameters in a dialog box.Resources
https://blog.bufferapp.com makes share buttons available on the side and in the bottom simultaneously:
An epic blog post stressing the importance of availability of share buttons:
https://blog.bufferapp.com/perfect-blog-post-research-dataA story about how sharing can be one of key engagement factors:
http://backlinko.com/content-strategy
Thanks for reading to the end.
Any thoughts on current workarounds are welcome, as well as sane criticism and examples of how you do it with Discourse.
Posts: 2
Participants: 2
@meglio wrote:
While writing a post, I'd like a button on the toolbar that would allow me to quickly insert a link to a particular category, e.g.:
[auto-inserted category name][1]. [1]: http://example.com/c/auto-inserted-category-link
Does anyone find it could be practical?
Is it more about plugin functionality or core one?
Posts: 7
Participants: 4
@JSey wrote:
Sorry about the title, feeling a little poetic today.
Here's what I came across: in a
Discourse.HeaderView.reopen({ didInsertElement: function() {
I am trying to talk to the Ruby server with an AJAX request. The very same code should also work for an iframe (a kludge I am using for a proof-of-concept). And: it doesn't.
The promise gets executed by the main frame, not the iframe. I am currently desperate enough to poke data from the main frame though to the iframe via an attribute of the iframe element - but that should not be the only solution, I hope?
Posts: 4
Participants: 2
@Grex315 wrote:
Just updated to version 0.6.4.
I made a change in settings and the discourse post type multi select box is not saving the options. It actually deselects them all so no post types have the option to post to Discourse. If i try and re-select them and save it does not save and leaves all unselected.
going back to 0.6.3 corrects this problem.
Posts: 3
Participants: 2
@AdamCapriola wrote:
YouTube videos don't auto-play, so I don't think Twitch embeds should either. Also, the display is small compared to YouTube (300x150 vs. 480x270). A consistent width for embeds would be cool.
Oh and the preview display for Twitch channels is kind of odd (it shows the channel's profile image but only the embed is shown once the post is published).
Posts: 2
Participants: 2
@LuaTenshi wrote:
I recommend adding the following code to .bash_profile as it grants easier and faster access to discourse.
function discourse { if [ "$1" = "cleanup" ]; then echo "CLEANUP INITIATED" ~/discourse_cleanup.sh echo "CLEANUP COMPLETE" elif [ "$1" = "goto" ]; then if [ "$2" = "c" ] || [ "$2" = "container" ]; then cd /var/discourse/containers/ else cd /var/discourse/ fi elif [ "$1" = "dir" ]; then if [ "$2" = "c" ] || [ "$2" = "container" ]; then echo "/var/discourse/containers/" else echo "/var/discourse/" fi else /var/discourse/launcher "$@" fi }
The contents of ~/discourse_cleanup.sh are...
docker inspect -f '{{.Id}},{{.State.Running}},{{.State.FinishedAt}}' $(docker ps -qa) | \ awk -F, 'BEGIN { TIME=strftime("%FT%T.000000000Z",systime()-60*60*24); } $2=="false" && $3 < TIME {print $1;}' | \ xargs --no-run-if-empty docker rm >/dev/null 2>/dev/null docker images --no-trunc| grep none | awk '{print $3}' | xargs -r docker rmi
Posts: 3
Participants: 2
@craft37 wrote:
Hello! Stunned with subject case.
Is there any way to import 'plain' html with topics, usernames, timestamps, years?
Old forum perl sourse code and DB lost, so I have only text.Please anybody give me some steps or tools info or even practice ideas more to parse and import html in discourse.
Thank you.
Posts: 2
Participants: 2