@watchmanmonitor wrote:

So many times, the person who opens a topic in a category like #support doesn't know to click the ellipsis and mark a post as the "solution".

It would be nice if anyone could use the "solved" checkbox as a way to easily let the OP know they should consider marking a post as the solution.

Posts: 5

Participants: 3

Read full topic

@tobiaseigen wrote:

Continuing the discussion from Did onebox change? They're not showing for my main site any longer:

Not sure what's going on here or if it's related to this topic, but my site used to onebox beautifully in discourse - it no longer does as of a week or so, even here on meta. I just updated my discourse to tests passed.. no dice. No changes recently on the wordpress site until we updated some plugins today.

Example URL that should onebox:

https://namati.org/resources/childhood-statelessness-in-south-africa/

Posts: 3

Participants: 2

Read full topic

@Ham wrote:

Hi, so Im working with the custom layouts plugin. I have both sidebars up.

On the main page (Latest) it looks fine. On categories is fine. But when I click on Top the topics (

) It runs over into the right sidebar.

Only certain pages are working ok, and others in the list are all running over. I cant seem to adjust it on those pages. When I adjust the css for topic-list.emberview it changes the pages that are ok and does nothing to other ones.

Appreciate any help. Thanks.

table.JPG1204x266 36 KB

Edit: Fixed with

.topic-list {
table-layout: fixed !important;
}

Posts: 1

Participants: 1

Read full topic

@jomaxro wrote:

At some point in the last 2 days internal URLs stopped oneboxing on my instance. I'm up to date with tests-passed as of 1:15 AM EST 6/9/17.

There are the errors I'm seeing in the console when a post with an internal URL is loaded. There do not appear to be any related errors in /logs.

Posts: 22

Participants: 6

Read full topic

@cat24max wrote:

Hey guys,

I was trying to change the hostname of my installation, so I followed this tutorial.
Discourse was installed to the default /var/discourse directory.

After using the "./launcher enter app" command I was switched from /var/discourse to /var/www/discourse and followed the next steps.
Now as that still didn't fix my broken CSS and pictures, I tried to go back to the /var/discourse folder, but it just isn't there anymore. How can this happen? I cannot find a file called "app.yml" ANYWHERE on the hard drive.

Posts: 14

Participants: 3

Read full topic

@Trash wrote:

For obvious reasons I can not repro the bug here on Meta.

I asked my team to test discobot after seeing that in the certificate I was assigned with the name of a group that was deleted months ago (SupportTeam)

Another member (he was a member of Support Team too) has been assigned the old username (Xtkale) that he changed years ago in Alex

And here another one, his username is murra, murray was the old username (he has never been a member of the Support Team)

It seems that discobot assigns the old username if you changed it. And if you never changed it he assigns the name of a deleted group if you belonged to that group.

EDIT: another recent member of our team has completed the tutorial for new user. He changed username before entering the team and discobot has given him to correct username.
The other members mentioned above have changed username after entering in some group, so probably discobot has problems with obsolete informations relative to groups.

EDIT2 : find some errors in the log

info:

Discourse::InvalidParameters (user_id must be present)
/var/www/discourse/plugins/discourse-narrative-bot/plugin.rb:80:in `generate'

backtrace

/var/www/discourse/plugins/discourse-narrative-bot/plugin.rb:80:in generate'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/implicit_render.rb:4:insend_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:198:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/rendering.rb:10:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/callbacks.rb:20:in block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:117:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:555:in block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:505:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in __run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:inrunprocess_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:in run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/callbacks.rb:19:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/rescue.rb:29:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/instrumentation.rb:32:inblock in process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:in block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications/instrumenter.rb:20:ininstrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:164:in instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/instrumentation.rb:30:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/params_wrapper.rb:250:in process_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/railties/controller_runtime.rb:18:inprocess_action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/abstract_controller/base.rb:137:in process'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionview-4.2.8/lib/action_view/rendering.rb:30:inprocess'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.4/lib/mini_profiler/profiling_methods.rb:76:in block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal.rb:196:indispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal/rack_delegation.rb:13:in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_controller/metal.rb:237:inblock in action'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:74:in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:43:inserve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:43:in block in serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:ineach'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:in serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:817:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/engine.rb:518:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:inpublic_send'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:in method_missing'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/mapper.rb:51:inserve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:43:in block in serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:ineach'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/journey/router.rb:30:in serve'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/routing/route_set.rb:817:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:incall!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:incall!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:incall!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:incall!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:incall!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:incall!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:incall!'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/conditionalget.rb:25:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/head.rb:13:incall'
/var/www/discourse/lib/middleware/anonymous_cache.rb:138:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/params_parser.rb:27:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/flash.rb:260:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:225:incontext'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:220:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/cookies.rb:560:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/query_cache.rb:36:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:29:in block in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:88:inrun_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in _run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:81:inrun_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/callbacks.rb:27:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/remote_ip.rb:78:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/debug_exceptions.rb:17:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/show_exceptions.rb:30:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/rack/logger.rb:38:incall_app'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/rack/logger.rb:22:in call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:17:incall_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:29:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-4.2.8/lib/action_dispatch/middleware/request_id.rb:21:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/runtime.rb:18:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.4/lib/mini_profiler/profiler.rb:171:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/message_bus-2.0.2/lib/message_bus/rack/middleware.rb:62:in call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/engine.rb:518:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/application.rb:165:incall'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:in public_send'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-4.2.8/lib/rails/railtie.rb:194:inmethod_missing'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/urlmap.rb:66:in block in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:ineach'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in call'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:606:inprocess_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in process_client'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:702:inworker_loop'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:549:in spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:142:instart'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.3.0/bin/unicorn:126:in <top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:22:inload'
/var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:22:in `'

env

hostname adu1-app
process_id 178
application_version d326784ecfe66adb16eab9800550ad7c4864464e
HTTP_HOST forum.adunanza.net
REQUEST_URI /discobot/certificate.svg
REQUEST_METHOD HEAD
HTTP_USER_AGENT Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
HTTP_ACCEPT text/html
HTTP_X_FORWARDED_FOR 51.15.41.81, unix:
HTTP_X_REAL_IP unix:

Posts: 1

Participants: 1

Read full topic

@huynhthai824 wrote:

Hello everyone, i wanna delete column users in front page
examlple photo:
Help me!

image.png1207x604 85.4 KB

Posts: 14

Participants: 3

Read full topic

@elfeffe wrote:

I have version v1.7.0.beta2, and I tried to upgrade it but it doesn't work.
How can I upgrade it?

Or at least, upgrade to a specific commit, so I go step by step.
Is that possible?

Posts: 7

Participants: 3

Read full topic

@sam wrote:

I have commenced our migration to markdown-it , all rejoice

markdown-it is a compliant CommonMark JavaScript library that is super fast, well maintained and straight forward to extend.

I already have it working on a branch, but so many of our extensions are broken that I do not want to subject everyone on meta to it quite yet.

The plan

Phase 1 - get this running on meta (underway)

The first phase of the migration to the new engine is getting us ready to turn markdown-it on at meta.

To make this feasible and minimize branching I designed it so we can merge in my changes early. Turning on markdown-it requires a hidden site setting and the actual work I am doing is totally segregated from current support.

This means I should be able to merge in my changes next week into the latest branch.

I plan to enable markdown-it at meta once I ported all our extensions and plugins running at meta to the new engine. This is a slow process as a lot of code needs to be re-written to support the new engine.

Expected time frame: 4-8 weeks

Phase 2 (stabalization)

The second phase of the project will be me submitting pull requests to various plugins and stabalizing the new engine. I anticipate running on meta for at least 2-4 weeks before "flicking the switch" and making the new engine default on.

During this phase I will make sure to close all the #markdown-it-review bugs. Not touching these bugs till this is live on meta.

Expected time frame: 2-4 weeks

Phase 3 (gutting out old engine)

The third phase of this process will be removing the old engine from core and adding "deprecation" so plugins that we did not catch can be notified of the change.

Expected time frame: 1-2 weeks

Phase 4 (removing deprecations)

Finally, in the release after next we will remove all the deprecation so we don't have to carry around dead code.

BUT I WANT TO PLAY WITH THIS NOW!

No need to be so loud, just click on this link:

markdown-it.discourse.org

You have to be logged in to meta.discourse.org for that to work....

I am providing some transient updates on my progress there.

Posts: 3

Participants: 2

Read full topic

@rohmann wrote:

I've added a poll, and it looks nice in the Composer preview. After saving, all I see is the poll code in the topic

[poll type=multiple min=1 max=5 public=true]
* Option 1
* Option 2
* Option 3
* Option 4
* Option 5
[/poll]

Any ideas what would cause this to happen?

Posts: 2

Participants: 2

Read full topic

@hnaseri wrote:

I have an educational android application. In this application, I gather some user activity data, day by day, and show them in some charts to the user. So that they could know their daily progress and effort.

I thought that these charts would be interesting and motivational for other users. So I am thinking of showing these charts publicly in the forum user profile page. I want a developer to do this job for me.

I just need two kind of charts:

1- A line chart which I think discourse already has implemented it in Admin panel for views, etc.
2- A punchcard chart. Somthing like what github shows in user profile page. (I found this repository which might be usefull)

Most of the data are provided with the application. We just need some user custom variables in discourse to store them. However we might also need some user data from discourse too. For example the daily contribution (post, topics, replies) to show them as a contribution punchcard graph in their profile.

I don't know if its possible, but we would like to be able to feature the best users, by showing their charts in topics. So for example something like a shortcode or oneboxing it to show a user chart in a topic would be really great (if possible).

Please let me know if you can do this work or if you have any question about this.

Posts: 1

Participants: 1

Read full topic

@slspencer wrote:

Can someone provide help with embedded video settings?
Obviously something changed, but I can't locate the setting that fixes this problem:
Our videos are now only downloadable links, they previously were playable within the post.

Current behavior:

forumvideoproblem1.PNG976x398 21.9 KB

Previous behavior:

forumvideoproblem2.PNG832x818 85.6 KB

Posts: 8

Participants: 3

Read full topic

@lkramer wrote:

Hello. We have Discourse 1.8.0. I just noticed that users no longer can choose to receive "daily summary" emails in the Mailing List mode area of their Preferences. The only options seem to be to receive "every email." Has this daily summary feature been eliminated?

(We host our forum at discoursehosting.com. Not sure exactly if they just upgraded 1.8.0.)

Posts: 3

Participants: 2

Read full topic

@brunoedigital wrote:

Hi,

I have an idea which seems simple but I'm not sure how easy it would be to implement.

Basically I would like a plugin where the user can connect his discourse profile on my community to an app on his Facebook.

What that app would do is that it would show notifications from Discourse inside Facebook notifications, just like any regular notification from facebook (like, reply, mention, etc).

Then when the person clicks on any of those notifications inside his facebook, it would redirect to the specific topic on my discourse install… and if he's logged in, would open as normal just as if he has clicked on a notification inside Discourse itself.

BTW, I don't use Facebook sing in/logon for my community. So it would have to be something as an app that I'd say:

“Click here to connect to your Facebook account.”… then that would open a Facebook window asking for those standard authorizations. After the ok, the app starts to push notifications from Discourse into Facebook.

That's the overall idea.

So, for that:

• Is it possible to work like that?
• What would the best way to go about it?
• If you are interested in this project, what would the budget be and how long you believe would take to create it?

After we can add here to the plugin section if other people want to use it

That's it.

Thanks!

Posts: 1

Participants: 1

Read full topic

@Kripesh_Das wrote:

Hi,

Can anyone help me to generate API key?

discourse api key.JPG1920x1040 73.1 KB

After following the instructions I am getting error

Posts: 3

Participants: 3

Read full topic

@yanokwa wrote:

Manual backups (local and to S3) work great, but automated backups don't seem to work. Any ideas why?

Settings

backup.png1546x1342 267 KB

Errors ~ 6 minutes after trigger

Job exception: Cannot allocate memory - fork(2)

/var/www/discourse/lib/backup_restore/backup_restore.rb:160:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:160:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:15:in `backup!'
/var/www/discourse/app/jobs/regular/create_backup.rb:8:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

Ram

root@discourse-app:/var/www/discourse# free -mh
              total        used        free      shared  buff/cache   available
Mem:           992M        664M         72M        137M        255M         50M
Swap:          2.0G        1.0G        1.0G

Posts: 6

Participants: 3

Read full topic

@sam wrote:

• Add a onebox eg: https://discuss.samsaffron.com

• Preview shows onebox

• Keep typing, preview hides onebox (yet onebox class is still there)

Assigning to @eviltrout for next week.

Posts: 1

Participants: 1

Read full topic

@Puranjay_Rajpal wrote:

For some reason when i post on twitter or other websites the favicon i uploaded is not pulled ? any ideas why ?

Posts: 3

Participants: 2

Read full topic

@Aussie_Wombat wrote:

Hey there! I was wondering would there be a possibility of adding an “unlimited reply” for private messages?

Because over in the Infinite Flight Community (which runs through discourse) all us Aussies have a private chat and it will keep ending so we have to invite everyone in again - that can get pretty annoying

So just as a little feature it would be great to have this as a feature

-Wombat

Posts: 6

Participants: 3

Read full topic

@SidV wrote:

This a strange behavior

Screenshot from my test:

image.png610x586 29.4 KB

Screenshots from TRY.discourse.org:

image.png630x623 37.2 KB

Minor bug (?)

image.png796x454 38.6 KB

I tried to test other languages but I couldn't.
When I changed to pr_BR for example, the discobot only replayed to me in English.

Posts: 5

Participants: 2

Read full topic