Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60279 articles
Browse latest View live

Disable direct access with port (nginx)

0
0

@preDawnHunter wrote:

I am not sure if I could the problem clear but I will try my best. grin

I set up the Discourse on port 9988 and proxy it to subdomain, http://d.abc.com/, with nginx. It works. However, I can still access it from http://abc.com:9988/ and http://d.abc.com:9988/. How can I completely disable the access to the port?

I am using Digital Ocean droplet and both top and subdomain are on the same droplet.

Below is my conf for both sites (in one file).

server {
    listen 80 default_server;
    listen [::]:80 default_server ipv6only=on;

    server_name fuguo.uk; # Replace with your domain

    location / {
         root /var/www/abc.com;
         index index.html index.htm;
    }
}

server {
    listen 80;
    server_name d.abc.com # Replace with your domain

    location / {
        proxy_pass http://localhost:9988;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_buffering off;
    }
}

Many thanks.

Posts: 4

Participants: 2

Read full topic


Left clicking /raw/ links return 404 errors

Should uploading function be more obvious?

0
0

@jesselperry wrote:

Hi all -

I had a user on my Discourse ask how to upload an image. Very easy problem to solve, of course. So I go to take a screenshot and show which button to press. Then I think "what button are you supposed to press?" because normally I just drag the image to the box. Lo and behold it's a non-obvious arrow pointing upwards, easily hidden in the middle of the row of icons. The alternative of course is dragging the file onto the message box. Well the help text to do that is grey/hard to read and it's the last part of a sentence that regular users would ignore as soon as they see the "Use Markdown, BBCode, or HTML to format" text that 90% of regular people have no idea what that means.

I propose that the priority of what a user wants to do when replying/creating a topic is: 1. Write text 2. Attach image 3. Everything else

Sure enough when you look around on social media, these functions are very clear and not hidden among other formatting features:

My proposition:

  • In the least, make the help text in the box be more obvious and highlight how to drag an attachment in
  • Change upload icon to be a camera (I know it also allows uploading any attachment, but again we're thinking about what the majority of users want to do) and highlight the icon and also separate it from the row of formatting icons. Maybe move icon to the empty space under the right side of the box where "saving"/"saved" currently lives?

Posts: 12

Participants: 4

Read full topic

Global Discourse Site Directory - mockups

0
0

@codinghorror wrote:

Here are some mockups from the amazing @rewphus on basic design ideas for a public, global Discourse site directory.

  • The goal is to publicize Discourse sites and get people going to your instance and increasing traffic.

  • The idea is that you would automatically be pulled into the directory (based on us crawling you) unless you specifically opted out in your site settings.

Posts: 4

Participants: 4

Read full topic

Restore failed at 'Validating metadata'

0
0

@AstonJ wrote:

With this message:

[2015-07-23 00:29:37] [STARTED]
[2015-07-23 00:29:37] 'AstonJ' has started the restore!
[2015-07-23 00:29:37] Marking restore as running...
[2015-07-23 00:29:37] Making sure /var/www/discourse/tmp/restores/default/2015-07-23-002937 exists...
[2015-07-23 00:29:37] Copying archive to tmp directory...
[2015-07-23 00:29:37] Unzipping archive...
[2015-07-23 00:29:37] Extracting metadata file...
[2015-07-23 00:29:37] Validating metadata...
[2015-07-23 00:29:37]   Current version: 20150713203955
[2015-07-23 00:29:37] EXCEPTION: undefined method `[]' for nil:NilClass
[2015-07-23 00:29:37] /var/www/discourse/lib/backup_restore/restorer.rb:176:in `validate_metadata'
/var/www/discourse/lib/backup_restore/restorer.rb:35:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:17:in `restore!'
/var/www/discourse/app/controllers/admin/backups_controller.rb:74:in `restore'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:552:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.10/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.6/lib/mini_profiler/profiling_methods.rb:106:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/mapper.rb:45:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:73:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:692:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/conditionalget.rb:35:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/head.rb:11:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:124:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/cookies.rb:562:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.8.3/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/methodoverride.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/runtime.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/sendfile.rb:112:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.6/lib/mini_profiler/profiler.rb:279:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/builder.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:65:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.5/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'
[2015-07-23 00:29:37] Trying to rollback...
[2015-07-23 00:29:37] There was no need to rollback
[2015-07-23 00:29:37] Notifying 'AstonJ' of the end of the restore...

Any ideas what going on here?

I've still got access to shared/standalone/backups/default on the old server if I need to use one of those backups instead...

Posts: 12

Participants: 4

Read full topic

Low bounce rate in Google Analytics?

0
0

@smartwatchme wrote:

Anyone ever have an issue with extremely low bounce rate being reported in GA? As in below 5%...?

Posts: 3

Participants: 3

Read full topic

Digests fire very quickly in a slow forum

0
0

@watchmanmonitor wrote:

On of the forms I manage is a slow moving on, mostly for dissemination of information. Many people are on digest, and if there isn't a post for one week, I'm seeing discourse JUMP on the first post as if it was the most important thing.

What this results in is people on a digest of 3 or 7+ days getting just the first post, then getting the rest of the follow ups 3-7+ days later, depending on their digest settings.

I think the following is what I'm after, but don't know what else it would effect:

Repro:

  1. Run a forum with sporadic activity.
  2. Have users on a 3 day digest
  3. Wait as 3+ days go by.
  4. As a topic is created/updated, watch as the first post triggers the digest email
  5. Digest users may login right away, but there's nothing more.
  6. Notice that people active on the site, or in mailing list mode reply & interact with the site.
  7. digest users won't get another email for 3+ days (depending on their settings)

What I'm wishing was that there was a bit more of a buffer between the one post triggering a digest that essentially mutes the forum for days, after just one post comes by. Maybe an admin setting of digest delay?

In our specific case, the forum is moderated, so I may go and release 3-4 posts at a time, but only the first one is emailed out, while the others are stale. In that case, knowing I could put a 1 hour delay would allow me to approve a number of posts, knowing at they will all go out in a single digest.

Thoughts?

Posts: 1

Participants: 1

Read full topic

Why are threaded replies echoed in the main topic stream?

0
0

@wpd wrote:

I understand Discourse places an emphasis on forum members reading as much as possible, but I can't quite understand why threaded replies show up again in the flat conversation stream. I just think the current design invites user frustration - I myself am fond of following sub-threads, but when I see the same thing I just read show up further down the stream I'm kind of feeling "why did I even bother?"

So instead of this:

I really prefer SBNation's indented view of sub-topics, as it solves the issue of denoting a sub-thread while keeping it completely visible in the mainstream (without echoing the same content twice):

Hiding a sub-thread is as easy as clicking once on the sub-thread's title:

Posts: 7

Participants: 4

Read full topic


Possible to change joined date?

0
0

@natedalliard wrote:

Hello everyone,

this is my first post here, I hope I am doing everything right.

Is it possible to change the joined date for any given user?

I ask, because I want to bootstrap my forum and make it ready for launch day, but I want the first user (admin and system) to be joined on launch day and not before. Any idea how I could achieve that if I can not change the joined date?

I could delete my admin account on launch day an register a new one. Is that possible with the user @system ?

Thanks guys, the software is really easy and fast to install. I love it so far!

Greetings from switzerland!

Posts: 8

Participants: 3

Read full topic

Who would prefer a standard wysiwyg to markdown?

0
0

@etewiah wrote:

I just saw an interview with Michael Pryor of trello:

http://startupxplore.com/blog/qa-michael-pryor-trello-interview-spain-launch/

At one point he says:

We added markdown in Trello which in retrospect, was a mistake because it’s a developer centric feature in a non developer focused product. We overcame it by adding guidance on how to use markdown within the app, but users sometimes still get confused.

I'm curious to know what the feeling out there is about the use of markdown in Discourse. Am I the only one who thinks discourse would appeal to many more people if it just used a standard wysiwyg editor?

Posts: 6

Participants: 6

Read full topic

Possible to use some features in django project?

0
0

@lin2280778 wrote:

Our company use Reviewboard fot code review, Reviewboard is a django app based on python.

I really love the pull-down menu at right of subject when we create a new Topic on Discourse.

I am think to use this feature in my reviewboard app,

Or add review code feature into Discourse ?

is that possible ?

/

Posts: 2

Participants: 2

Read full topic

HTTPS on my discourse

0
0

@Zonork wrote:

Hi, i want to enable the HTTPS in ma Discourse, how i can do that?, i need do something in my container? or are only a configuration?

Posts: 3

Participants: 3

Read full topic

How to move discourse urls from one domain to another? How to do page redirects

Deleting posts doesn't reset last activity date

0
0

@davemaxwell wrote:

We were having an issue with the auto-close feature where threads which have been dormant for a while weren't being closed automatically (we have it set to close 30 days after the last activity). Doing some moderating, I have found that deleting the last post in a thread doesn't reset the last activity date on the thread. So if a spammer wannabe comes in and lays down a crap post two months after the last post, we lose those two months for the auto-close functionality to work.

Edit: It seems to be the "Category" level dates/activity periods which are incorrect (see screenshots in post #3)

Example thread: http://community.sitepoint.com/t/javascript-add-css-to-style-wont-work/190090/18

Notice how the last post is actually May 20 (deleted post was made and deleted July 21)

This is the category page which shows the last activity period after the post was deleted. It still shows the relative time to the deleted post.

To recreate:

  1. Find an older post (say two months old) and add a post to the thread.
  2. Delete the post (I was using the delete spammer functionality but just deleting the post does it as well)
  3. Notice that the last activity date will still have the date/time of the deleted post, not the "old" last post.

Posts: 7

Participants: 4

Read full topic

Container docker persistent

0
0

@Zonork wrote:

Hi, how i can make a container like Discourse container, i dont know how run my container and let them running if my server is shut down

Posts: 4

Participants: 2

Read full topic


Search help doesn't work

0
0

@natedalliard wrote:

Continuing the discussion from Search help doesn't work in RU locale:

The same happens to me when I use DE locale, then the help button from the search doesn't work. When I switch over to EN locale it works flawless. Any ideas how to fix that? Do I have to translate something?

Posts: 1

Participants: 1

Read full topic

Uncategorised tag not showing on posts or in lists of posts

0
0

@gingerling wrote:

Hi

I am having some odd issues at discuss.phpList.org

First of all, we allowed uncategorised posts, however, they had no coloured category tag on the post or lists of posts, as if they just "had no category", with white space where the category infromation would normally be. I assumed this was normal, but when I go the the categories page you can see there is a category for them with a mustard coloured tag.

Also these posts would often not get read or any attention, I can't work out if there is some bug or if people just don't notice them because of the missing tag making them less visible in some way.

I then disallowed posting with no category for a while, because of them mostly being support requests and not being read, however, we actually do want uncategorised for legitimate uses.

I am really confused as to why the uncategorised coloured tag does not show on posts with this category.

I would also like to make it so uncategorised is not the default, to stop lazy people just not using the category function.

Posts: 2

Participants: 2

Read full topic

Are TL3 and TL2 requirements too different?

0
0

@alefattorini wrote:

Take a look at this:

Regular: 32
Member: 827 :-\
Guess that read 25% of topics created in the last 100 days in a very active forum it's really hard.
For example in meta are 300 topics.. no bad smile
Am I wrong? Do you think an intermediate level could be useful?

Posts: 2

Participants: 2

Read full topic

Issues with embedding from RSS

0
0

@laurakalbag wrote:

I’m having a few issues with embedding from RSS. I’m going to enable comments for each original post, but I want to ensure that the comments end up in the right location in Discourse with the correct attributed author and publishing date.

Issue 1: embed username key from feed

I need each topic to be correctly attributed to the right author. I’m set up as the default. My RSS has a format of <discourseUsername>jo</discourseUsername>, so I entered discourseUsername as the value for embed username key from feed. It just attributes all topics to the default user. Have I done something wrong here?

Issue 2: pubdates

I need each topic’s timestamp to be the same as the original post publishing time. Otherwise adding our RSS feed of ~70 posts floods the forum with outdated topics that have recent timestamps. (Pushing newer manually-created topics down.) Is there a way to set the timestamp for topics pulled from RSS to the same time as the RSS <pubdate>?

Issue 3: chronology

Maybe related to Issue 3, the topics imported via RSS are not in the same chronological order as the original posts.

I hope none of these are stupid questions! Any help, suggestions, or workarounds would be much appreciated! smile

Posts: 1

Participants: 1

Read full topic

Big troubles with site customizations and embedding after update

0
0

@probus wrote:

I updated my Discourse instance to latest (tests-passed) and I believe something broke with site customizations.

1) Code highlighting is gone from site customizations except for css and save is greyed out. I think I remember a bug like this but I believe it got fixed. This is with Firefox, with Chrome it still works..

2) Embedding is completely busted. My discourse header customizations show up in the embedded iframe. It makes the embedded comments completely unusable. I was just about to release this blog..

I updated a test server with identical site customizations to the same commit and everything works well with that. I have a feeling something went wrong when updating. How can I redo the update/install to the production server? Destroy the docker container and build a new one?

Posts: 1

Participants: 1

Read full topic

Viewing all 60279 articles
Browse latest View live




Latest Images