@rwahmao wrote:
at the admin->login panel,i enabled signup cta. and it will display a content box at the end of each post to promote sign up.
and i personally really donot like the emoji in it,and want modify the content.
i try to find the content text at admin panel but failed.
anybody know where&how to modify the text?
Posts: 10
Participants: 3
@jd2066 wrote:
From what I have found, these are the available storage drivers:
Union File Systems - aufs and overlayfs
I'm currently using overlayfs and it seems to work ok but I'm not sure about it as I've read that it can use too many inodes which can cause problems.
Snapshot Enabled File System - btrfs
This looks like an interesting option but it isn't recommended for production use.
Device Mapper Loopback
This uses Device Mapper over Loopback Mounted Image Files. From what I've read, this is a slow and unrecommend option.
Device Mapper using raw block devices
This option uses Device Mapper, usually with LVM on raw block devices. It seems to be better then the loopback option but how much I don't know. Also on a Virtual Private Server (VPS), the raw block device is actually a virtual image file so I don't know for sure if this helps here as the raw block device is still not really a hard disk but in a VPS, no hard disks are real so it may not matter.
Posts: 9
Participants: 3
@jd2066 wrote:
When I run the launcher script, it always shows the following message before running the specified command:
which: no docker.io in (/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin)I looked the launcher's code and found the line causing this:
docker_path=`which docker.io || which docker`It seems while the line of code will set docker_path to the path of docker.io or docker, one of the which commands will fail causing an error to be printed to the console.
I'm not quite sure how this can be fixed as the
whichcommand doesn't seem to have an option to suppress errors.The launcher script still functions despite showing this error but it certainly confused me when I first attempted my Discourse install as I thought my Docker install might be broken.
Post Note: I left this uncategorized because the bug category says it's for bugs that prevent Discourse from working normally and this bug doesn't stop Discourse from working normally, it's just makes setup a bit confusing/annoying.
Posts: 2
Participants: 2
@mikehunterson wrote:
I can't wrap my head around this. I'm trying to view a topic next to latest topics on the main page. I modified the main application route map so topic routes are inside the discovery route. Like this:
It loads the topic view correctly into the discovery view but how do I get the navigation bar and topic list there too? Any advice is appreciated.
Posts: 1
Participants: 1
@KazWolfe wrote:
Recently, I noticed the Suppress this category from the homepage option on my Discourse install.
This sounds like a perfect precursor to something like an "event category," or a category only visible while certain events are happening.
Basically, an "event category" will have a switch on it that, when enabled, will completely hide the category -- allowing no access except by a direct link. This would hide the category from the Categories page, from the category selection menus, and hide any category posts from the "New/Latest/Unread/Top" sections.
Event Mode can be enabled by either using a checkmark, or by selecting a date range in which it's enabled.
Posts: 1
Participants: 1
@Magnetidog wrote:
Hello,
I have successfully configured Discourse on a Digitalocean droplet and then setup the importer for vBulletin using the various topics on the the forum. The importer is now connecting correctly to the database (installed on the same server and coming from a vBulletin 4 installation). Anyhow, a few seconds after the process has started, I get this error:
discourse@discourse:/var/www/discourse/script/import_scripts$ RAILS_ENV=production ruby vbulletin.rb loading existing groups... loading existing users... loading existing categories... loading existing posts... loading existing topics... importing groups... 6 / 25 ( 24.0%) Failed to create group id 7 Moderators: ["Name has already been taken"] 25 / 25 (100.0%) importing users /var/www/discourse/script/import_scripts/base.rb:202:in `escape_string': wrong argument type Fixnum (expected String) (TypeError) importing groups... 6 / 25 ( 24.0%) Failed to create group id 7 Moderators: ["Name has already been taken"] 25 / 25 (100.0%) importing users /var/www/discourse/script/import_scripts/base.rb:202:in `escape_string': wrong argument type Fixnum (expected String) (TypeError) from /var/www/discourse/script/import_scripts/base.rb:202:in `block in all_records_exist?' from /var/www/discourse/script/import_scripts/base.rb:202:in `map' from /var/www/discourse/script/import_scripts/base.rb:202:in `all_records_exist?' from vbulletin.rb:75:in `block in import_users' from /var/www/discourse/script/import_scripts/base.rb:675:in `block in batches' from /var/www/discourse/script/import_scripts/base.rb:674:in `loop' from /var/www/discourse/script/import_scripts/base.rb:674:in `batches' from vbulletin.rb:64:in `import_users' from vbulletin.rb:32:in `execute' from /var/www/discourse/script/import_scripts/base.rb:45:in `perform' from vbulletin.rb:564:in `<main>'Is there anything I could do to figure out what is going on here?
Thanks!
Posts: 2
Participants: 2
@Hector wrote:
When viewing a category here on meta it seems that sorting by replies, views or activity has stopped working.
Posts: 2
Participants: 2
@Mooash wrote:
I think it would be beneficial if the value for
them-coloris a separate setting fromheader_background.At the moment its set like this:
<meta name="theme-color" content="#<%= ColorScheme.hex_for_name('header_background') %>"I tried overwriting it as a customization however setting it twice doesn't change anything, when on a Nexus 5 using Google Chrome it just uses the first
<meta>tag it sees and doesn't take into account the secondary one.For example, I'd like to set the
theme-colorto red but keep the background of the header as white still since red matches my favicon.
Posts: 3
Participants: 2
@mikedyang wrote:
Hello everyone!
There has been some discussion about how to manage a multi-language community. Like this, this and this.
From what I've gathered there are 3 options for running a multi-language community:
1. Separate sites for every language.
Pros
- Categories are preserved in every language.
- Users see only their native language.Cons
- Communities are separated with little to zero interaction.2. Make a category for every language
Pros
- Language communities interact.
- Multi-language speaking users can add more value and volunteer translating.
- Users see only their native language inside categoryCons
- Categories are preserved only in the main language. Other languages get 1 category where everything is posted.3. Make a tag for every language
Pros
- Language communities interact.
- Multi-language speaking users can add more value and volunteer translating.
- Categories are preserved in every language.Cons
- Users see posts in languages that they don't speak.What's been your experience? Which approach did you choose? Are there any other ways to manage multi-language communities?
All feedback is appreciated.
Thank you.
Posts: 2
Participants: 2
@boopathi_s wrote:
curl -X POST --data "name=dave&username=dave&email=dave@example.com&password=P@ssword&active=true" http://localhost:3000/users/list/active?api_key=**&api_username=** i posted th is curl in ubuntu when i posted this url ...i will get a lengthy doctype html page as a response
i am new to this could anyone help me this out.
Posts: 2
Participants: 2
@Ricardo_Viteri wrote:
Hello, is there a way to setup discourse to force newly registered users to read the top and faq before posting?
Posts: 5
Participants: 3
@fefrei wrote:
I'm using Discourse for a yearly event (a preparatory course at a university), both for internal use for the organizers and for discussion among participants. This year's event has finished, and once usage has dropped below significance, I'd be okay with shutting the installation down.
Next year, however, I want to have another installation ready, and the old topics available as an archive to the organizers. This leaves multiple options, and I'm not sure what is best:
Archive HTML, New Installation
I could simply drop the current installation and bootstrap a new install. After copying over a few site settings, it would be mostly ready! However, I need an archive of the old posts. I could try to download the HTML view of all old posts, and offer them as an archive to the new team of organizers.
This should be relatively easy, but the archive is hard to search, and you cannot link to old posts.
Move Installation, New Installation
I could also try to move my current installation somewhere else (a different subdomain), and leave it up and running! This would serve as a nice searchable archive where I can link to old topics, but this needs server resources and updates. I'd also need to create accounts for next year's organizers in the old installation so they have the right permissions.
I don't think this approach really scales over multiple years.
Category Permissions
I could also put this year's participants into a large group, and use category permissions to restrict access to old topics to the corresponding participants.
Since I don't want this year's participants to see next year's posts, I would also need to put next year's participants into their own group – which can't simply be done in the SSO payload.
I also cannot move all current categories under a new category
2015since Discourse doesn't support sub-subcategories.Deleting all Topics
Another idea would be to leave the forum as-is, but clean it up:
- delete all topics
- prevent SSO for this year's participants
- disable all user accounts (so no-one gets mail notifications until he signs in again)
The resulting Discourse installation would look mostly empty, and could be used by next year's organizers and participants without the old users noticing. However, using the
?status=deletedquery string, the organizers (all with moderator permissions) could browse the archive.I don't see a way to allow searching these deletes posts.
Hiding all Topics
Similarly, I could proceed as before, but hide all topics instead of deleting them. For the organizers, this would mean that old topics are still easily available and searchable, only distinguished by the "hidden" icon.
Category Archiving
There's a discussion on how category archiving should work. This might work once it is implemented, but I think it is not really tailored towards this situation.
I'm interested in opinions on how to proceed. Which method is the best in this case? Did I overlook a better way?
Posts: 6
Participants: 4
@Killian_Hermann wrote:
Confirmed behavior in production 1.5.0 beta 2
Continuing the discussion from Can't make wiki topics if post_menu was modified:
I had to reset the filters I had on my hidden post menu and menu items in order to get the elipsis -> admin wrench to set wiki posts (and other functions on that menu)
The thread that figured this out for me was closed last year, not sure where this ended up but seems like a legit bug.
Posts: 2
Participants: 2
@lisajill wrote:
I have been asked by one of my peers if there is a way to make the thumbnail for StackOverflow oneboxing smaller. I suspect that this will come up with others.
Are there any configurations we can do? Or would we need to modify Onebox? Can someone guide me on this?
Thanks!
Posts: 2
Participants: 2
@Krischan wrote:
Hi all,
I'm using this code (thanks again, @tgxworld!) to present different calls to action for users who are logged in/not logged in.
Now I want to educate myself about other conditions that can be used like this. For example: I want to target certain groups the same way as above. Is there something like
if currentUser is part of group "Group name" then?
And where can I find more information on other variables that can be used here?
Thanks so much!
Posts: 1
Participants: 1
@eviltrout wrote:
We've been using pagedown as our rich composer for years. Unfortunately, we'd outgrown it in a few ways:
It's very hard to extend to add features.
It hasn't been updated in years.
It had implementations of features we didn't like or found buggy like undo/redo. We forked the editor and removed them but that just left us with a lot of dead code.
It had zero tests. Modifying it meant we could be taking a detour to regression town U.S.A.
We made the decision to rewrite our composer using Ember.js so it was more in line with the rest of our codebase and so that we could allow people to extend it more easily.
In our master branch, we have the first attempt at this re-write and we'd love your help to test it out. We've deployed it to Discourse Meta already, however it has not replaced the main posting composer yet. This is a major code change and we want to make sure it works well before replacing the main functionality of Discourse. Instead we've replaced the rich markdown editor everywhere except posting:
The user preferences page, for editing your About Me
The admin page for editing text content
Editing queued posts before approving them
Editing category templates
If you have admin access on your own Discourse on the master branch you can test #2-4 but if you're just trying here on Meta, the best place is #1.
Please post any issues or feedback on the new composer. If we find it works well we'll replace the main composer shortly.
Fun Developer Stats
The new editor has 118 integration tests, covering all of its functionality.
The new editor is less than 350 lines of code (including the handlebars markup). Pagedown is over 2,300 lines! We're going to be deleting a lot of code.
Posts: 12
Participants: 8
@Trash wrote:
In admin > settings > user preference I set a list of categories that are watched by default.
After a few days I change settings and I moved the list in "default categories tracking".In User Profile I can see the list of categories is still under "watched" and not "tracking".
The change is not real-time?
Posts: 3
Participants: 2
@Mike_Nielsen wrote:
Hey!
We are currently testing migration from vBulletin to Discourse and we're moving our site which has over a decade of posts.
All users and groups have been migrated, but when the script hits "import_topics", this error fires:
importing topics... vbulletin.rb:213:in `block (2 levels) in import_topics': undefined local variable or method `topic' for #<ImportScripts::VBulletin:0x007f6b33cc1e88> (NameError) from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.7/lib/patches/db/mysql2.rb:6:in `each' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.7/lib/patches/db/mysql2.rb:6:in `each' from vbulletin.rb:213:in `map' from vbulletin.rb:213:in `block in import_topics' from /var/www/discourse/script/import_scripts/base.rb:676:in `block in batches' from /var/www/discourse/script/import_scripts/base.rb:675:in `loop' from /var/www/discourse/script/import_scripts/base.rb:675:in `batches' from vbulletin.rb:201:in `import_topics' from vbulletin.rb:33:in `execute' from /var/www/discourse/script/import_scripts/base.rb:45:in `perform' from vbulletin.rb:563:in `<main>'I'm not super familiar with Ruby, so I'm not even sure where it gets the 'topic' variable from as it does not seem to be defined anywhere but referenced in several places.
Thanks for your help
Posts: 2
Participants: 2
@lisajill wrote:
It registers the 'right' time in the topic but on the list of posts on the front page (category view as primary) it says the old timestamp:
Wrong:
Right:
Posts: 3
Participants: 3
@ATPJD wrote:
Is there a secret configuration option to allow me to limit how long a user remains signed-in?
I would like users to be signed-out automatically after 30 minutes of inactivity.
Thanks for any pointers.
Posts: 13
Participants: 6
