Anton wrote:
Please could you explain what this mean and where it is used, need it to make correct translation.
Translation key:
js.raw_email.title
Original English text:
Raw Email
Posts: 4
Participants: 2
Anton wrote:
Please could you explain what this mean and where it is used, need it to make correct translation.
Translation key:
js.raw_email.title
Original English text:
Raw Email
Posts: 4
Participants: 2
Anton wrote:
Could you please explain the meaning of User Card Badge concept so I can make a correct translation and add it to the Transifex glossary.
Related translation keys:
js.user.change_card_background.title
User Card Backgroundjs.user.card_badge.title
User Card Badge
Posts: 6
Participants: 4
Anton wrote:
Please explain what do these keys mean so that I can translate them to Russian and add corresponding instructions to Transifex.
Translation keys in question and their original English text versions are:
i18n.transliterate.rule.ț
ti18n.transliterate.rule.Ț
ti18n.transliterate.rule.ș
si18n.transliterate.rule.Ș
s
Posts: 1
Participants: 1
KajMagnus wrote:
Hi,
Discourse generates the cooked HTML in the browser, right? And sends it together with the raw markdown to the server and saves it server side? (Without re-rendering the HTML from the markdown server side)
Do you sanitize the HTML server side, with some Ruby tool then I suppose?
Best regards, KajMagnus
Posts: 2
Participants: 2
Anton wrote:
It seems as if currently this translation key is not pluralized:
js.composer.min_length.need_more_for_reply
{{n}} to goPlease could you pluralize it as Russian translation needs pluralization. Many thanks!
Posts: 1
Participants: 1
Jason Wojo wrote:
Apologies if this exists or I'm in the wrong category. Does the $99 one-time install include configuration for email as well, or does the admin need to go into the code to set these values after the install? Overall, how much configuration is included?
Posts: 2
Participants: 2
Jeff Atwood wrote:
I am also getting double profile background with error:
[bs_BA.user.change_expansion_background.title]
Posts: 7
Participants: 3
Briancguy wrote:
Guys,
I just upgraded from beta 1 to beta 6 and suddenly users are complaining that they are seeing real names (I've had real names hidden because we're a medical site).
Please FIx ASAP!!!
Posts: 3
Participants: 2
Alex Okafor wrote:
Continuing the discussion from Official color plugin not working:
Having done a clean docker install and added this plugin it still doesn't appear be working. I get the stripped
<span>
elements as in the original bug report.
Posts: 1
Participants: 1
Andrew Kraut wrote:
I added the web ssl template, then issued
./launcher rebuild app
and now it fails to bootstrap:FAILED -------------------- RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 362 exit 1> Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "chown -R discourse $home", "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'"]} 0ffcf6cbc3b36241997d17f99638c61fb8405441417adcb75aade0305c1acf9b FAILED TO BOOTSTRAP
Further up, I also see this:
I, [2014-10-25T07:58:38.004253 #45] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' rake aborted! NoMethodError: undefined method `after_after_initialize' for #<Plugin::Instance:0x007f161e6b0ab8> /var/www/discourse/plugins/discourse-plugin-permalink/plugin.rb:12:in `activate!' /var/www/discourse/lib/plugin/instance.rb:171:in `instance_eval' /var/www/discourse/lib/plugin/instance.rb:171:in `activate!' /var/www/discourse/lib/discourse.rb:84:in `block in activate_plugins!' /var/www/discourse/lib/discourse.rb:84:in `each' /var/www/discourse/lib/discourse.rb:84:in `activate_plugins!' /var/www/discourse/config/application.rb:149:in `<class:Application>' /var/www/discourse/config/application.rb:19:in `<module:Discourse>' /var/www/discourse/config/application.rb:18:in `<top (required)>' /var/www/discourse/Rakefile:5:in `require' /var/www/discourse/Rakefile:5:in `<top (required)>' (See full trace by running task with --trace)
Any ideas what's going wrong?
Posts: 4
Participants: 2
Marco wrote:
I'm trying to add a site to the onebox whitelist, I enter ebay.it in the text field:
and a soon as i click elsewhere (the field looses focus) the entire field is cleared:
I can't save the setting.
Posts: 6
Participants: 5
Dean Taylor wrote:
The admin section for reviewing trust levels appears to have incorrect links.
Whilst viewing the trust level 3 requirements for a user
/admin/users/{username}/tl3_requirements
You see this:
Note the button/link toTrust Level 2 Users
Should this be
Trust Level 3 Users
?And then you click the
Trust Level 2 Users
button/link and it takes you to:
URL:/admin/users/list/regular
But isn't
regular
Trust Level 3?Should this just be
/admin/users/list/tl3
to make the url consistant withtl3_requirements
?
Especially if these can be renamed fromRegular
at somepoint?
Posts: 1
Participants: 1
Bohuslav Svancara wrote:
Hello,
I am trying to migrate our proprietal forums data to Discourse.
I am able to convert users, categories and topics.
But trying to convert posts I ended with this SQL exception when Discourse performs the command:
topic = Topic.find_by(id: @opts[:topic_id])
in the PostCreator.setup_topic function.
(The Input argument is:
puts @opts[:topic_id]
{"topic_id"=>63, "post_number"=>1, "url"=>"/t/matrix-mania-dead-on-arrival/63/1"}
)Can some good soul help me please?
Thank you,
BobException while creating post 27775416. Skipping. PG::Error: ERROR: missing FROM-clause entry for table "id" LINE 1: ...opics" WHERE ("topics"."deleted_at" IS NULL) AND "id"."topi... ^ : SELECT "topics".* FROM "topics" WHERE ("topics"."deleted_at" IS NULL) AND "id"."topic_id" = 63 AND "id"."post_number" = 1 AND "id"."url" = '/t/matrix-mania-dead-on-arrival/63/1' LIMIT 1 /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `exec' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `block in exec_no_cache' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract_adapter.rb:373:in `block in log' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activesupport-4.1.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract_adapter.rb:367:in `log' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `exec_no_cache' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/postgresql/database_statements.rb:137:in `exec_query' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/postgresql_adapter.rb:954:in `select' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/database_statements.rb:24:in `select_all' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/query_cache.rb:70:in `select_all' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/querying.rb:39:in `find_by_sql' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/relation.rb:611:in `exec_queries' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/relation.rb:493:in `load' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/relation.rb:238:in `to_a' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/relation/finder_methods.rb:460:in `find_take' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/relation/finder_methods.rb:98:in `take' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/relation/finder_methods.rb:81:in `find_by' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/querying.rb:7:in `find_by' /home/vagrant/vagrant/lib/post_creator.rb:197:in `setup_topic' /home/vagrant/vagrant/lib/post_creator.rb:70:in `block in create' /home/vagrant/vagrant/lib/distributed_mutex.rb:21:in `synchronize' /home/vagrant/vagrant/lib/distributed_mutex.rb:5:in `synchronize' /home/vagrant/vagrant/lib/post_creator.rb:137:in `block in transaction' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction' /usr/local/rvm/gems/ruby-2.0.0-p0-turbo/gems/activerecord-4.1.6/lib/active_record/transactions.rb:208:in `transaction' /home/vagrant/vagrant/lib/post_creator.rb:131:in `transaction' /home/vagrant/vagrant/lib/post_creator.rb:69:in `create' /home/vagrant/vagrant/script/import_scripts/base.rb:454:in `create_post' /home/vagrant/vagrant/script/import_scripts/base.rb:401:in `block in create_posts' /home/vagrant/vagrant/script/import_scripts/base.rb:381:in `each' /home/vagrant/vagrant/script/import_scripts/base.rb:381:in `create_posts' script/import_scripts/collective2.rb:79:in `execute' /home/vagrant/vagrant/script/import_scripts/base.rb:71:in `perform' script/import_scripts/collective2.rb:259:in `<main>'
Posts: 2
Participants: 1
Thomas Wilson wrote:
I'm trying to embed discourse comments in my ghost blog but am running into issues.
My Discourse install is setup with SSL, so I'm not sure if that could be causing odd behaviour.
When attempting to embed comments, I follow the instructions on @eviltrout's blog. I set the discourse URL to http:// (rather than http s, which maybe I should be doing?).
Nothing loads, so I check the dev console and see that my discourse install has X-Frame-Options=SAMEORIGIN set in its headers (rather than ALLOWALL). I follow the instructions here and restart my container, but STILL get the SAMEORIGIN error.
Would the fact that my site runs over http s be a problem here? If so, is there anything I can do to get around this?
Posts: 1
Participants: 1
Joe Seyfried wrote:
Maybe I'm missing something, but here's a thought that occurred to me while fiddling with my import scripts: wouldn't it be nice if we had a backup feature that deals only with the site's settings, but not the contents (posts, categories, uploads etc. should be left out)?
This would be a) somewhat reassuring if you had a staff of more than one who are allowed in the admin section. Plus b) it would ease my (admittedly somehow unstructured ) import efforts, since I run an import (lengthy operation), leave it online for a while for my team to explore, change some things in the admin settings while it's there, and then before my next importer run, when I want to revert to my pre-flight backup with only the basic settings, I'm pulling my hair trying to figure out which settings to write down in order not to lose them...
Posts: 2
Participants: 2
TheLoneCuber wrote:
I noted a problem with user profile pop-ups on 1.1.0.beta7 here, and since the same problem exists on How To Geek's Discourse I'm guessing it will effect most users running 1.1.0.beta7 with a custom header.
Adding height to the header (by way of image or other: on standard header only, not mobile) offsets the user profile pop-ups by the new height amount. In my case the header image is 400px high, so the user profile pop-ups pop up 400px below the user profile, which means it actually appear off-screen on smaller viewports.
I've only added the header image to my Discourse after upgrading to 1.1.0.beta7, so I'm not sure if this is a known problem, though I've not found any other posts on it. And I hadn't noticed it on How To Geek's Discourse instance previously either.
You can see the problem live by clicking any user profile thumbnail at http://discuss.howtogeek.com/.
Posts: 2
Participants: 2
Mikkel Høgh wrote:
I have been trying to wrap my head around how to run those import scripts that come with Discourse, but without insight into the world of Ruby on Rails, it's proving difficult. I'm trying to import data from a Drupal site, using
script/import_scripts/drupal.rb
. I've edited it with the right connection info for my MySQL database, and I've tried to run it in different ways. I think something like this ought to work?bundle exec ruby script/import_scripts/drupal.rb
However, that gives me this error:
script/import_scripts/drupal.rb:3:in `require': cannot load such file -- mysql2 (LoadError) from script/import_scripts/drupal.rb:3:in `<main>'
I've tried working around that with a
bundle exec gem install mysql2
, but that seems to make no difference at all, even though it insists that the gem is now installed.What am I doing wrong?
Posts: 1
Participants: 1
TheLoneCuber wrote:
On a brand new Discourse instance, with no users yet, I want to use Twitter login only, and I want to force the Discourse username to match the Twitter username. Discourse already automatically populates the new usernames as their logged-in Twitter username. So is there any way to remove the users' ability to edit their Discourse username when creating a new account?
Or is their any other way I can achieve this?
Posts: 4
Participants: 2
Allen - Watchman Monitoring wrote:
I just upgraded and now I'm looking at a logo link which takes me to the page I'm on...
Any thoughts on a button to bring us back to the admin page in general?
Posts: 2
Participants: 1
Justin Gordon wrote:
I've got discourse integrated into my octopress blog. It works great on the individual article pages.
However, on the homepage, I see this. Any advice? You can see this at http://www.railsonmaui.com. Just scroll down.
Besides incorrectly listing many links, the links go to the wrong pages. For individual article pages, I get the correct display of comments.
Posts: 1
Participants: 1