@Roxelle wrote:

Hi guys,
I have a problem after the team installed Discourse.
I can reach my forum only through the ip address.
How is it possible?
I have created the DNS required in my external domain.

Now to me there is a doubt.
The name servers in the domain, which must be?

Posts: 3

Participants: 2

Read full topic

@downey wrote:

Reproduce:

1. Go to a category where people can mark solutions & click the Edit button to modify category settings.
2. Notice "Allow topic owner and staff to mark a reply as the solution" is not checked.
3. Check the box for that, and click Save Category.
4. Open the edit dialog again.

Expected result:

• The box accurately represents the state of the toggle, and stays checked.

Actual result:

• The box is not checked for categories with solutions enabled, and the box never stays checked after checking it and saving settings.

Posts: 2

Participants: 1

Read full topic

@meglio wrote:

Letting admins (and optionally mods) read private messages can be useful. But most of our users don't think it is a good idea, so it is better if they don't know and there is no way for admins to accidentally let everyone suspect that such a feature exists.

One of our competitors has recently lost more than 50 active users just because there were a proof that mods can read private messaging threads! There were a real scandal - it was read by many users; it all ended up in users leaving the forum (some of them have registered with us).

We do not like the idea of our mods reading PMs, so we switched it off. However, while we, the admins, rarely read PMs to understand what's happening behind the scenes when there is a hot discussion, I noticed that I can do any of this: "like", "share" and even "invite" others to the discussion. In my view, this should be OFF - admins should be able to read in READ-ONLY mode (strict), with no way to accidentally do anything that would disclose such a feature.

Letting everyone know about such a feature will not work - partially because of our mentality, partially because Russian/Ukrainian-speaking people do not trust each other as much as people in other nations do (not sure which ones?). Thus, it is not an option nor a partial solution for our forum. It is not possible to adequately explain to our users that whatever day do, it is a normal feature that we always can read everything and anything right in the database. Most of the users strictly believe that PMs are really hidden from everyone, including admins. It is simply not the right time for our nation to think and understand that who owns the forum also has access to PMs at any time.

If not as a default feature, it would be very helpful to at least be able to SWITCH OFF any edits/actions that admins can do while reading PMs where they do not participate personally.

Posts: 15

Participants: 9

Read full topic

@Kensie wrote:

I found a topic about whether or not mods should be able to see email addresses, but I couldn't find the outcome. We have the use case that our mods are volunteers and we need to be able to restrict them from seeing personal information, or we need to make sure they've signed an NDA.

We noticed that moderators are not able to click the "Show email" button on a user's profile, but they are able to see email addresses by visiting pages like admin/users/list/active and admin/users/list/staff

Whether or not moderators are meant to see email addresses, we assume this inconsistency is a bug. Apologies if this has already been discussed somewhere, happy to be linked to existing discussion!

Posts: 1

Participants: 1

Read full topic

@downey wrote:

When I load https://discourse.example.org/admin/upgrade, the upgrade check works for all plugins but hangs indefinitely on the discourse repository itself. Any ideas?

Pasted image610x518 54.4 KB

Posts: 4

Participants: 2

Read full topic

@riking wrote:

Continuing the discussion from Clicking on user avatars of people in PMs doesn't pop up user card:

Posts: 2

Participants: 2

Read full topic

@Falco wrote:

People are asking to create some subcategories with regional access on my instance.

I have created 4 subcategories and 4 groups. One for each.

The problem is: each group is around 5000 people.

Anyone tried something like this?

The index at group_users table only helps search by group_id, but not by user_id (to list all groups like in the profile), maybe adding an index (userd_id, group_id) will solve any excess of seq_scans ?

Posts: 6

Participants: 3

Read full topic

@meglio wrote:

After 9 months of enthusiastic effort of 5+ people, our forum is now just 150 registered users (no fake ones), 500 topics, 5k messages, 14k visitors / month, ~1.2 session / visitor, 4.5m reading time per session.

I find it very hard to build a large community and readers base when it comes to a very specialized area (Ukrainian goat farmers in my case).

Just wondering, is this really too little even for a small community, or is it close to an average for many other small communities?

Posts: 5

Participants: 4

Read full topic

@Jong wrote:

I love tag plugin. Thanks.

Topic suggestion which based on exist topic is very useful.
But when I type in Korean, topic suggestion filter doesn't work properly.

Check thease screenshots.

English

tagsuggestion2.png898x330 10.5 KB

Korean

tagsuggestion.png888x424 15.7 KB

Posts: 3

Participants: 2

Read full topic

@jesselperry wrote:

I'm on beta 10. When a specific user tries to create a topic in any category - it gives a Internal Error 500. It happens just for this user, and in any category they try to post. Very strange.

Below is the backtrace. Any clues?

/var/www/discourse/app/models/topic_user.rb:102:in `>='
/var/www/discourse/app/models/topic_user.rb:102:in `block in change'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:199:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/transactions.rb:208:in `transaction'
/var/www/discourse/app/models/topic_user.rb:85:in `change'
/var/www/discourse/app/models/topic_notifier.rb:40:in `change_level'
/var/www/discourse/app/models/topic_notifier.rb:18:in `watch_topic!'
/var/www/discourse/lib/topic_creator.rb:64:in `watch_topic'
/var/www/discourse/lib/topic_creator.rb:42:in `create'
/var/www/discourse/lib/post_creator.rb:266:in `create_topic'
/var/www/discourse/lib/post_creator.rb:123:in `block in create'
/var/www/discourse/lib/post_creator.rb:215:in `call'
/var/www/discourse/lib/post_creator.rb:215:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/transactions.rb:208:in `transaction'
/var/www/discourse/lib/post_creator.rb:213:in `transaction'
/var/www/discourse/lib/post_creator.rb:121:in `create'
/var/www/discourse/lib/new_post_manager.rb:150:in `perform_create_post'
/var/www/discourse/lib/new_post_manager.rb:123:in `perform'
/var/www/discourse/app/controllers/posts_controller.rb:114:in `create'
/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:77: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/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-1.0.0.3.pre/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:170:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:72: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>'

Posts: 13

Participants: 2

Read full topic

@OnceWas wrote:

I just rebuilt my development Discourse instance from 1.4b10 to v1.4.0.beta12, and the Discourse-generated letter avatars are now getting pulled from https://avatars.discourse.org. For example, the URL for my letter avatar for administrator is now https://avatars.discourse.org/letter/a/f9ae1b/32.png.

On my production server, which is on 1.4b9, the avatar URL is /letter_avatar/administrator/32/5_fcf819f9b3791cb8c87edf29c8984f83.png

My API calls to my 1.4b12 server also show the discrepancy in the avatar URLs:

...
["users"]=>
  array(2) {
    [0]=>
    object(stdClass)#630 (3) {
      ["id"]=>
      int(19)
      ["username"]=>
      string(13) "administrator"
      ["avatar_template"]=>
      string(56) "https://avatars.discourse.org/letter/a/f9ae1b/{size}.png"
    }
    [1]=>
    object(stdClass)#629 (3) {
      ["id"]=>
      int(-1)
      ["username"]=>
      string(6) "system"
      ["avatar_template"]=>
      string(52) "/user_avatar/ask.twobydev.com/system/{size}/17_1.png"
    }
  }
  ["user"]=>
  object(stdClass)#659 (29) {
    ["id"]=>
    int(19)
    ["username"]=>
    string(13) "administrator"
    ["avatar_template"]=>
    string(56) "https://avatars.discourse.org/letter/a/f9ae1b/{size}.png"
    ["name"]=>
    string(17) "Two by Fore Admin"
    ["last_posted_at"]=>
    string(24) "2015-08-20T16:57:57.794Z"
    ["last_seen_at"]=>
...

Seems odd - and definitely not ideal for all involved - if all my letter avatars are getting pulled from Discourse's CDN.

1.4b12:

1.4b12.png1331x549 98.6 KB

1.4b9:

1.4b9.png1376x386 87.5 KB

Posts: 8

Participants: 4

Read full topic

@wethil wrote:

Hello dear developers and users. I want to make discourse location based like craigslist. But not with gps. just users chose their country manually. How can I do it simply ?. I want to add a country choosing page after sign up page but routes.rb is very confusing.

Posts: 1

Participants: 1

Read full topic

@Knagis wrote:

If I use "Accept emails from anonymous users with no accounts" for a category that only staff has access to it can correctly receive e-mails from anonymous users (they are submitted via the "system" user and a quote tag).

I expected that this accepts e-mails from existing users since it does not reduce the security in any way. Unfortunately it does not - instead a rejection e-mail is sent back to the user.

My use case - as many others I am trying to use Discourse to replace our ticketing system. I have a small script that uses API to retrieve the received e-mails, create new users and change the owner of the posts.

I would actually prefer a setting "Accept any e-mail" - that would set "skip_validations" option both for replies and topic creation - a moderator would then process the posts. The reason is that when a user writes the e-mail he does not get the feedback about unique titles, minimum lengths, permissions etc.

Posts: 2

Participants: 2

Read full topic

@axp wrote:

Not sure that this is a bug, but when I dismiss posts (too much posts, I mean there is more than one page) in /new I have just big white screen waiting for something May be it would be better to bring position to header?

after-dismis.jpg1218x685 51.6 KB

Posts: 7

Participants: 4

Read full topic

@substance_D wrote:

I wish to have a similar drop-down menu from header logo.
How do i achieve it?

Thanks

Posts: 4

Participants: 2

Read full topic

@Krischan wrote:

I'm sure this question has been asked before, but I can't find any answers: Can users create their own subcategories? If not, what is the best practice to have something similar to a user generated "sub-reddit"? Thanks for your help!

Posts: 2

Participants: 2

Read full topic

@terraboss wrote:

Is anyone running Discourse on AWS's new EC2 Container Service? Is it recommendable? Are there any known issues with managing them?

Thanks

And a little bit longer... ;oP

Posts: 1

Participants: 1

Read full topic

@randaalex wrote:

Hello,

I try to implement availability to setup topic image (this is primary image and it will displayed in topics list, show, etc)
I write plugin, and add file-type field (similarly to https://github.com/discourse/discourse-tagging)

But I have problem: when I add file via input, file caught by composer file uploader:

Discourse.png2030x984 321 KB

Perhaps exists some ability to change this workflow via plugin?

Posts: 3

Participants: 2

Read full topic

@gzoritchak wrote:

The demo below. The same image is uploaded twice.

The first time the name of the file is "écran.png". At the end of the upload the link is not updated. The file was uploaded (you can check in the original directory).

Uploading écran.png...

After changing the name from "écran.png" to "ecran.png". The upload is working.

It's a problem for many countries. By default a screen copy file name on a french mac is "Capture d'écran 2015-mm-DD à HH:MM:SS.png".

ecran.png1556x720 66 KB

Posts: 2

Participants: 2

Read full topic

@sam wrote:

image.jpeg2048x1332 268 KB

I think there is a lot of wasted area. The search field could be in the same line with the results value and dropdown menu for filtering. And at the left side to the current results is also too much white space. A little bit on both sides will be okay, but not as much and static as it now is.

Posts: 3

Participants: 2

Read full topic