@Richie wrote:

Hi everyone,

I’m struggling to get a large-size top logo to display properly and I’m wondering if someone could help me out.

I’ve taken some code from both @Simon_Cossar and @Nick_Putman from this thread (which is a couple of years old now, unsure if still valid on current versions?): Big header, scroll down, make header small (Like default size)

When viewing on a desktop sized browser the large logo is displayed correctly. Then when you scroll down in a topic it disappears from view and gets replaced with the small logo. All correct, as expected, works fine.

On mobile (an old iPhone 5S) the small logo is displayed instead - again all working fine.

On an iPad Mini 2 there is NO logo/banner displayed at all - until you scroll down in a thread, then the small logo appears correctly. But until then, no logo is shown. And this is my issue, no logo on tablet sized devices.

I tried removing this section:

.discourse-touch .brand-header {
    display: none;
}

At which point the big logo then appears on the iPad - but the big logo then also appears on mobile and it’s way too wide so it allows or forces the page to scroll left and right (horrendous!). But, the logo does appear.

So my dilemma here is how do I get my large logo to appear on the iPad Mini 2 size screens?

Or, how do I make the large logo responsive, so when viewed on Mobile it scales down to fit the width of the mobile?

If you’d like to see this issue in action, my discourse (running v1.9.0.beta14) is at https://greyarro.ws

This is the large logo I wish to use: https://greyarro.ws/uploads/default/original/1X/e4b1b51b1c15174d8eba003302eaab349a94985c.jpg

Changes I’ve made thus far:

Admin > Settings > logo url > (I’ve placed a 1x1px transparent gif in here)

Admin > Customise > Themes > Default > Edit CSS/HTML > CSS

.title .logo-big {
    display: none;
}
.brand-header {
    margin-bottom:-63px;
}
.brand-header .brand-logo {
    z-index:5000;
    position: relative;
}

// Force the Discourse header to remain fixed, even with iOS 'elastic scrolling'
.discourse-touch .d-header {
    position: fixed;
}

// This displays the small logo on iPhone but then no logo is visible at all on iPad Mini 2
.discourse-touch .brand-header {
    display: none;
}

// Always display the site logo - without this is will disappear during the iOS elastic scrolling
.discourse-touch .d-header #site-logo {
    display: inline;
}

Admin > Customise > Themes > Default > Edit CSS/HTML > Header

<div class="wrap brand-header">
    <a href="https://greyarro.ws/">
        <img class="brand-logo" src="/uploads/default/original/1X/e4b1b51b1c15174d8eba003302eaab349a94985c.jpg">
    </a>
</div>

Hopefully I’ve supplied enough information - please let me know if you need any more details??

Thanks in advance

Posts: 5

Participants: 2

Read full topic

@mattbr wrote:

Hello,

I am in the process of moving from phpBB to Discourse and managed to get everything up and running except for the avatars. Any user uploaded avatars from phpBB are not displaying and I am getting the letter avatar, however if a user has setup Gravatar on phpBB it is able to fetch and grab the images from there and set them properly.

When I navigate to /var/discourse/shared/standalone/import/data/avatars/upload I can see that there are images of users avatars in there, however when I view my forums they are not being associated to the user.

I have read this thread: Letter avatars still displayed after importing phpbb3 avatars the only plugins we are using are:

• Docker Manager
• Discourse MigratePassword

Since I’m a new user I cannot link to both of those, but are easy to find on GitHub. I do not believe are causing any issues. I have my avatars settings.yml file as:

import:
    avatars:
        uploaded: true
        gallery: true
        remote: true

Does anyone have any other suggestions as to what might be the issue? I would like to not have to force our users to re-upload their avatars once we go live with Discourse. I have verified that once on Discourse you can re-upload your avatar and it works perfectly fine.

Thanks!

Posts: 1

Participants: 1

Read full topic

@Vespura wrote:

I’m not sure if this has been an issue just on one discourse forum I moderate on, or if this is happening to more sites. Anyway the issue is that I can’t remove/deny/disagree a flagged topic. I can ignore/defer or accept/agree it no problem, just the disagree button doesn’t seem to work. The flag looks like it disappears but if you reload the page it’s back.
Flagged posts don’t cause the same issue. They can be agreed/disagreed/ignored all fine. It’s only on flagged topics (/the OP of a topic) which has this weird bug.

This doesn’t seem to happen on my own site (I’m an admin on there so maybe that overrides it), but trying this out on a forum where I’m a moderator gives me this problem.

Posts: 2

Participants: 2

Read full topic

@supermathie wrote:

As per the following screenshot, the ‘currently selected post’ red bar should disappear when selecting posts for mod operations:

image.jpg809x1012 244 KB

Otherwise it looks as though the post on which the bar sat was selected for deletion/moving/etc.

(also, not a big deal but the number of selected posts doesn’t change on the right when more posts are selected)

Posts: 1

Participants: 1

Read full topic

@Quintin_Par wrote:

Trying to do a disqus comments import

root@ss-app:/var/www/discourse/script/import_scripts# RAILS_ENV=production ruby disqus.rb --file=/tmp/disqus-export.xml --dry_run

and I am hit with this error

image.png1409x213 63.2 KB

root@ss-app:/var/www/discourse/script/import_scripts# RAILS_ENV=production ruby disqus.rb --file=/tmp/disqus-export1.xml --dry_run
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::LIBXML_VERSION
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::LIBXML_PARSER_VERSION
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::NOKOGIRI_USE_PACKAGED_LIBRARIES
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::NOKOGIRI_LIBXML2_PATH
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::NOKOGIRI_LIBXSLT_PATH
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::NOKOGIRI_LIBXML2_PATCHES
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::NOKOGIRI_LIBXSLT_PATCHES
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::LIBXML_ICONV_ENABLED
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::XML::EntityDecl::INTERNAL_GENERAL
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::XML::EntityDecl::EXTERNAL_GENERAL_PARSED
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::XML::EntityDecl::EXTERNAL_GENERAL_UNPARSED
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::XML::EntityDecl::INTERNAL_PARAMETER
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::XML::EntityDecl::EXTERNAL_PARAMETER
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/nokogiri.so: warning: already initialized constant Nokogiri::XML::EntityDecl::INTERNAL_PREDEFINED
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/version.rb:3: warning: already initialized constant Nokogiri::VERSION
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/version.rb:3: warning: previous definition of VERSION was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/version.rb:100: warning: already initialized constant Nokogiri::VERSION_INFO
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/version.rb:100: warning: previous definition of VERSION_INFO was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:29: warning: already initialized constant Nokogiri::XML::ParseOptions::STRICT
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:29: warning: previous definition of STRICT was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:31: warning: already initialized constant Nokogiri::XML::ParseOptions::RECOVER
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:31: warning: previous definition of RECOVER was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:33: warning: already initialized constant Nokogiri::XML::ParseOptions::NOENT
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:33: warning: previous definition of NOENT was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:35: warning: already initialized constant Nokogiri::XML::ParseOptions::DTDLOAD
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:35: warning: previous definition of DTDLOAD was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:37: warning: already initialized constant Nokogiri::XML::ParseOptions::DTDATTR
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:37: warning: previous definition of DTDATTR was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:39: warning: already initialized constant Nokogiri::XML::ParseOptions::DTDVALID
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:39: warning: previous definition of DTDVALID was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:41: warning: already initialized constant Nokogiri::XML::ParseOptions::NOERROR
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:41: warning: previous definition of NOERROR was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:43: warning: already initialized constant Nokogiri::XML::ParseOptions::NOWARNING
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:43: warning: previous definition of NOWARNING was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:45: warning: already initialized constant Nokogiri::XML::ParseOptions::PEDANTIC
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:45: warning: previous definition of PEDANTIC was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:47: warning: already initialized constant Nokogiri::XML::ParseOptions::NOBLANKS
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:47: warning: previous definition of NOBLANKS was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:49: warning: already initialized constant Nokogiri::XML::ParseOptions::SAX1
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:49: warning: previous definition of SAX1 was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:51: warning: already initialized constant Nokogiri::XML::ParseOptions::XINCLUDE
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:51: warning: previous definition of XINCLUDE was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:53: warning: already initialized constant Nokogiri::XML::ParseOptions::NONET
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:53: warning: previous definition of NONET was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:55: warning: already initialized constant Nokogiri::XML::ParseOptions::NODICT
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:55: warning: previous definition of NODICT was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:57: warning: already initialized constant Nokogiri::XML::ParseOptions::NSCLEAN
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:57: warning: previous definition of NSCLEAN was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:59: warning: already initialized constant Nokogiri::XML::ParseOptions::NOCDATA
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:59: warning: previous definition of NOCDATA was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:61: warning: already initialized constant Nokogiri::XML::ParseOptions::NOXINCNODE
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:61: warning: previous definition of NOXINCNODE was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:63: warning: already initialized constant Nokogiri::XML::ParseOptions::COMPACT
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:63: warning: previous definition of COMPACT was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:65: warning: already initialized constant Nokogiri::XML::ParseOptions::OLD10
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:65: warning: previous definition of OLD10 was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:67: warning: already initialized constant Nokogiri::XML::ParseOptions::NOBASEFIX
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:67: warning: previous definition of NOBASEFIX was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:69: warning: already initialized constant Nokogiri::XML::ParseOptions::HUGE
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:69: warning: previous definition of HUGE was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:72: warning: already initialized constant Nokogiri::XML::ParseOptions::DEFAULT_XML
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:72: warning: previous definition of DEFAULT_XML was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:74: warning: already initialized constant Nokogiri::XML::ParseOptions::DEFAULT_HTML
/usr/local/lib/ruby/gems/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/parse_options.rb:74: warning: previous definition of DEFAULT_HTML was here
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax/parser.rb:33:in `<class:Parser>': superclass mismatch for class Attribute (TypeError)
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax/parser.rb:32:in `<module:SAX>'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax/parser.rb:3:in `<module:XML>'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax/parser.rb:2:in `<module:Nokogiri>'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax/parser.rb:1:in `<top (required)>'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax.rb:3:in `require'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax.rb:3:in `<top (required)>'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml.rb:3:in `require'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri/xml.rb:3:in `<top (required)>'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri.rb:36:in `require'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/nokogiri-1.8.1/lib/nokogiri.rb:36:in `<top (required)>'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/loofah-2.1.1/lib/loofah.rb:3:in `require'
	from /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/loofah-2.1.1/lib/loofah.rb:3:in `<top (required)>'

what could be the issue?

Posts: 1

Participants: 1

Read full topic

@Steven wrote:

Sorry for my english, it’s a bit technical for me.

When I use the wrench then the following options : Select Posts... > delete selected after selecting 5+ posts, it’s buggy, sometimes

The first time I tried this : I selected 200+ posts, deleted it, but when I refreshed the page, they weren’t deleted.

After upgrading to the latest version, I didn’t try to delete 100+ posts again, I try a few at a time

• If I select 10 or less posts, it usually works fine
• if I select between 10 and 30 posts the selected posts have the deleted background (red in my case) for a few seconds then change to their usual background (white background)… But after a refresh they are in fact deleted.
• If I select 30+ posts, the posts can stay undeleted. (EDIT : in fact, after a refresh one minute later, they are deleted. It makes sense, must be sidekiq who needs time)

It’s not an exact science, sometimes it works fine, sometimes not, it’s a bit weird.

Tested on Firefox and Chrome on latest Discourse version.

Posts: 1

Participants: 1

Read full topic

@ShadowPauler wrote:

Let me tell you why I think Discourse is the best, forum software out there now, please know this is my personal opinion and is now a general fact, but could be one sooner or later…

Discourse is forum software in development, with many features that forums don’t have today, nor would they come to a point where they will have these amazing features that are still in development, such as the live previewer with the editor, makes creating content, a lot more easier, and you know that you won’t screw up because it’s on the right of your screen! What forum software has that? None that’s Implanted, and it’s even able to use Grammarly, which I am currently using, so it’s compatible! You can even go do something in the editor as your thinking about what you’re going to type. Come on, isn’t that just awesome or what?

The next feature I think that is great is the less loading and more reading. I mean, don’t you hate the entire website reloading again just to get to the next page? If you have a bad internet connection, it would be awful and terrible. But wait, Discourse gots you fam! See Discourse doesn’t have to reload because it’s awesome! Okay, not just that, but it uses something called, “Ajax” which is the future of technology. Loading a websites components without reloading or refreshing, saving a lot of time, and bandwidth, Discourse highly makes use of this and makes everyone happy creating the concept of never refreshing.

Another thing that makes Discourse so amazing is it’s anti-spam system! Huh, don’t you love that? I mean who likes spam just overloading their community and members with awful, or terrible, or just massive messages? Nobody, I can tell you that for sure. And the way Discourse loads the messages, just makes it so smooth, like make a sandbox of Discourse, now copy and paste a massive amount of spam and let it load. Now if you check it out on another computer or phone, it loads smoother than sandstone! And that’s pretty smooth!

The last thing about Discourse that I love is not simply a feature that can be created, or a plugin that can easily go into Discourse, it’s the great developers of Discourse, Now I know I have made a first bad impression, but seeing how helpful and kind they really are towards others made my soul go to heaven. They get money only from sponsors and server renters for Discourse, and they have made their project open-source by choice, as they help others getting nothing back except for feedback from them. The Discourse developers are those guys who would dedicate their lives to a project, just to make everyone happy.

I think they should deserve major thanks from the community, so PM or Mention them, and tell them how thankful you are for them creating the future of forums, the future of technology, the future, of Discourse. Thank you for reading.

Posts: 5

Participants: 3

Read full topic

@nsuchy wrote:

So I have two questions about the Discourse App.

1. At some point will the app work like an app and not just a web browser list?
2. Currently only Discourse hosted forums get notifications, I run a community that’s very privacy sensitive and my users don’t want big hosts / business having access to user data - we use a small host Frantech and don’t use Cloudflare / any big providers to handle user information. Any way that could change? Maybe offer it as a small service at low rate?

Posts: 1

Participants: 1

Read full topic

@jordan1909 wrote:

I needed to determine if it was possible to:

1. Detect when a new post is submitted via client side
   Reason: We do a lot of support here. We do not want “stale” cases to go unanswered or slip through the cracks.
   
   ==> If specific poster != x set topic timer on a specific topic based on this change and set it to a specific user

It a long shot and I have a feeling this functionality will require a full plugin however I wanted to determine if this was the case.

I guess I am more directly trying to find out if I can even detect a post submission and if I can update the timer via an api call to the topic. I can figure out the rest myself if I can confirm this is possible and where this is documented.

Posts: 3

Participants: 2

Read full topic

@Andy_White1 wrote:

We would like to create a link from some text in the Category Description. which opens Create Topic dialogue page (Just as the Create new Topic text link does.)

Here is the page on our site where the question is posed

Many thanks for your help on this. I have searched and I get the feeling it is a wish list, but maybe wrong

Posts: 2

Participants: 2

Read full topic

@xiasummer wrote:

Hi,

I use my discourse to write long stories, some times it is so long that the Discourse reacts quite slow, especially when I write some mathjax formulas with the math plugin.

I’m wondering if this is normal? And also, should I change some parameters to have a better performing system?

Yours.

Posts: 2

Participants: 2

Read full topic

@huynhthai824 wrote:

My website is https://batdongsan.host
And it’s die
We only ping successfull
I git pull and lauch rebuild command finish normal, but website die still.
I don’t know how check error?
Can you help me?
Thank you!

Posts: 4

Participants: 4

Read full topic

@NickB wrote:

When I click Make Public Topic on a Private Message, the message is converted to a topic - but I can’t work out which category it will end up in. How do I set the category for the ex-message?

Thanks, Nick

Posts: 4

Participants: 2

Read full topic

@Slowhand wrote:

This is only happening in Windows 10/Edge, works correctly in Firefox & Chrome.

When using one-box, getting a stretched box.

Example, first one is how it used to look and next post is how it looks now. Seems to have started on November 8.

image.png809x785 116 KB

Posts: 3

Participants: 2

Read full topic

@kuyashi wrote:

Is there a reason why some domains/subdomains don’t appear as a onebox ?
I have added the domain in the whitelist - makes no difference:

Sample URL:
https://medium.freecodecamp.org/chart-the-stock-market-with-react-redux-react-vis-and-socket-io-18caf312693c

Posts: 1

Participants: 1

Read full topic

@vinothkannans wrote:

If Onebox URL had & symbol in query string it is automatically converting as & in onebox html.

For example https://meta.discourse.org/new-topic?title=topic%20title&body=topic%20body&category=support/wordpress&tags=wordpress

It makes trouble to pre-filled topic via URL feature as it reported here.

Posts: 4

Participants: 2

Read full topic

@gerhard wrote:

When you edit a category it’s not possible to scroll on the settings tab anymore. Looks like it’s caused by select-box-kit which adds overflow: hidden to the .modal-body element.

cc @joffreyjaffeux

Posts: 1

Participants: 1

Read full topic

@Andreas_Dorfer wrote:

Issue: Fix not compatible with latest discourse · Issue #4 · nunof07/discourse-mumble · GitHub
in order to run
GitHub - nunof07/discourse-mumble: Mumble Viewer plugin for Discourse
with current discourse (and mumble-server off course)

Goal: Working fix on Github plus PR on the original repository.

Timeframe: until end of 2017.

Budget: 100USD via paypal

Posts: 1

Participants: 1

Read full topic

@nixie wrote:

Is there a way to disable local backup and enable just Amazon S3 online backup?

Posts: 7

Participants: 3

Read full topic

@nsuchy wrote:

Screen Shot 2017-11-11 at 2.16.24 PM.png1546x324 34.5 KB

The message I sent says 7 hours ago when it was sent one minute ago. The admin panel shows the user was on one minute ago. So confused is this bug or something I did

Posts: 22

Participants: 6

Read full topic