@bartv wrote:

Hi,

after importing, we have a large number of categories that need new colors - it’s a bit of a Christmas tree right now and people are complaining How can I easily ‘batch update’ categories? The ideal solution would be to set a category and all its children to a specified value, but as a temporary work around setting all (sub-) categories to the same color will do too.

Posts: 1

Participants: 1

Read full topic

@bartv wrote:

Hi,

after running an import with 300k users, I found that running the weekly digest is a bit of an issue: the server will queue 100k emails at once and processing them is hard on the machine - the load spikes up (about 10x), making the site very slow for a hours. I suppose this is an edge case of running an import - with organic signups these will be distributed more evenly throughout the week, making this less of an issue.

For now, I’ve flushed the email jobs and stopped generating digests, but I’d like to re-enable them.

What’s the recommended strategy for handling this - is there a way to ‘spread out’ the generation of the digests?

Posts: 1

Participants: 1

Read full topic

@nabeel wrote:

Hi,
I am in the processing of modifying the text fields in discourse using the jquery.ime plugin. I simply find the corresponding handlebar template and add the required javascript code. But I cannot find the hbs file containing the definition of search text field that appears at the top of the page. Can somebody please tell where can I find this definition?
Thanks,

Posts: 1

Participants: 1

Read full topic

@Ellibereth wrote:

Screenshot_20180506-092805.png1440x2560 220 KB

Screenshot_20180506-092758.png1440x2560 188 KB

I think these both look a tad bit funky visually. ( In the former you’re not sure if there’s stuff after build poll and in the latter “Hide Details” is cut off). Not sure about solution.

As a side note, someone thought “hide details” meant closing the options menu and was surprised when it generated a tag. Maybe there’s a better word choice?

Posts: 1

Participants: 1

Read full topic

@TechnoBear wrote:

If a topic is unlisted, topic search returns no results for any search term. Omitting unlisted topics from a general search makes sense, but if I’m actually viewing the topic, surely I should also be able to search it?

Posts: 4

Participants: 4

Read full topic

@katiesmith wrote:

I’ve just downloaded the Discourse iOS app (it is very responsive and user-friendly, I might add), and I would love to create an App like this for my existing forum. Does anyone have experience and guidance for this?

Posts: 3

Participants: 3

Read full topic

@alfabetagama wrote:

For anyone interested, i’ve put together new Vagrant Discourse development setup:

It is using Winnfsd driver for sharing so it should perform better than SMB or native VirtualBox shares.

Tested on Windows 7, feedback for other platforms would be appreciated.

Posts: 3

Participants: 3

Read full topic

@TheBestPessimist wrote:

I want to make “Categories:” page as the landing page.

From what i read i should change in the admin dashboard -> top-menu the order of the items there but at least in 2.0.0 beta9 this is no longer possible.

Any ideas?

Thanks!

Posts: 2

Participants: 2

Read full topic

@fefrei wrote:

The magic URLs for creating a pre-filled message don’t work anymore. This is a recent regression.

For example, clicking https://meta.discourse.org/new-message?group_name=team should open a message to @team (or at least show an error if that’s not possible), but for me, it currently does nothing besides redirecting to /lastest.

Posts: 2

Participants: 2

Read full topic

@Cheeser wrote:

Couldn’t get the upload system to work (it never put the backup where it needed to be), so I gave up and copied the file manually to /~discourse/public/backups/default. That got the backup to appear in the list.

Clicking Restore on my backup produces the following log output.

I am trying to restore to my local development machine in Windows 10’s Linux Subsystem so I can hack at the database (import a ton of content from a proprietary forum system) and then backup/restore to my production site. Any help would be appreciated!

I’m running Discourse v2.0.0.beta9 on both development and production.

[2018-05-06 16:12:23] EXCEPTION: Invalid argument
[2018-05-06 16:12:23] /root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/connection/hiredis.rb:19:in 'connect'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/connection/hiredis.rb:19:in 'connect'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:334:in 'establish_connection'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:99:in 'block in connect'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:291:in 'with_reconnect'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:98:in 'connect'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:363:in 'ensure_connected'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:219:in 'block in process'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:304:in 'logging'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:218:in 'process'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis/client.rb:118:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis.rb:2448:in 'block in _eval'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis.rb:45:in 'block in synchronize'
/root/.rbenv/versions/2.4.2/lib/ruby/2.4.0/monitor.rb:214:in 'mon_synchronize'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis.rb:45:in 'synchronize'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis.rb:2447:in '_eval'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/redis-4.0.1/lib/redis.rb:2499:in 'evalsha'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/message_bus-2.1.4/lib/message_bus/backends/redis.rb:381:in 'cached_eval'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/message_bus-2.1.4/lib/message_bus/backends/redis.rb:141:in 'publish'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/message_bus-2.1.4/lib/message_bus.rb:253:in 'publish'
/root/discourse/lib/backup_restore/restorer.rb:512:in 'publish_log'
/root/discourse/lib/backup_restore/restorer.rb:505:in 'log'
/root/discourse/lib/backup_restore/restorer.rb:42:in 'run'
/root/discourse/lib/backup_restore/backup_restore.rb:167:in 'block in start!'
/root/discourse/lib/backup_restore/backup_restore.rb:164:in 'fork'
/root/discourse/lib/backup_restore/backup_restore.rb:164:in 'start!'
/root/discourse/lib/backup_restore/backup_restore.rb:23:in 'restore!'
/root/discourse/app/controllers/admin/backups_controller.rb:103:in 'restore'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/basic_implicit_render.rb:4:in 'send_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:186:in 'process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rendering.rb:30:in 'process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:20:in 'block in process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:131:in 'run_callbacks'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:19:in 'process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rescue.rb:20:in 'process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:32:in 'block in process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in 'block in instrument'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in 'instrument'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:in 'instrument'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:30:in 'process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/params_wrapper.rb:252:in 'process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/activerecord-5.1.4/lib/active_record/railties/controller_runtime.rb:22:in 'process_action'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:124:in 'process'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionview-5.1.4/lib/action_view/rendering.rb:30:in 'process'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-mini-profiler-1.0.0/lib/mini_profiler/profiling_methods.rb:104:in 'block in profile_method'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:189:in 'dispatch'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:253:in 'dispatch'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:49:in 'dispatch'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:31:in 'serve'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/mapper.rb:16:in 'block in <class:Constraints>'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/mapper.rb:46:in 'serve'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:50:in 'block in serve'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in 'each'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in 'serve'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:834:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-protection-2.0.1/lib/rack/protection/frame_options.rb:31:in 'call'
/root/discourse/lib/middleware/omniauth_bypass_middleware.rb:24:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/conditional_get.rb:38:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/head.rb:12:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/session/abstract/id.rb:232:in 'context'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/session/abstract/id.rb:226:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/cookies.rb:613:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/activerecord-5.1.4/lib/active_record/migration.rb:556:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:26:in 'block in call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:97:in 'run_callbacks'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:24:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/executor.rb:12:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/better_errors-2.1.1/lib/better_errors/middleware.rb:84:in 'protected_app_call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/better_errors-2.1.1/lib/better_errors/middleware.rb:79:in 'better_errors_call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/better_errors-2.1.1/lib/better_errors/middleware.rb:57:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/debug_exceptions.rb:59:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/show_exceptions.rb:31:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/logster-1.2.9/lib/logster/middleware/reporter.rb:31:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:36:in 'call_app'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:26:in 'call'
/root/discourse/config/initializers/100-quiet_logger.rb:16:in 'call'
/root/discourse/config/initializers/100-silence_logger.rb:29:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/remote_ip.rb:79:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/request_id.rb:25:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/method_override.rb:22:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/executor.rb:12:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/static.rb:125:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/sendfile.rb:111:in 'call'
/root/discourse/lib/middleware/missing_avatars.rb:21:in 'call'
/root/discourse/lib/middleware/turbo_dev.rb:34:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-mini-profiler-1.0.0/lib/mini_profiler/profiler.rb:285:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/message_bus-2.1.4/lib/message_bus/rack/middleware.rb:63:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.1.4/lib/rails/engine.rb:522:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in 'public_send'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in 'method_missing'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/urlmap.rb:68:in 'block in call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/urlmap.rb:53:in 'each'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/rack-2.0.4/lib/rack/urlmap.rb:53:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.9.1/lib/puma/configuration.rb:224:in 'call'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.9.1/lib/puma/server.rb:602:in 'handle_request'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.9.1/lib/puma/server.rb:435:in 'process_client'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.9.1/lib/puma/server.rb:299:in 'block in run'
/root/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.9.1/lib/puma/thread_pool.rb:120:in 'block in spawn_thread'
[2018-05-06 16:12:23] Trying to rollback...
[2018-05-06 16:12:23] There was no need to rollback
[2018-05-06 16:12:23] Notifying 'magic' of the end of the restore...
[2018-05-06 16:12:27] Cleaning stuff up...
[2018-05-06 16:12:27] Removing tmp '/root/discourse/tmp/restores/default/2018-05-06-161222' directory...
[2018-05-06 16:12:27] Unpausing sidekiq...
[2018-05-06 16:12:27] Marking restore as finished...
[2018-05-06 16:12:27] Finished!

Posts: 7

Participants: 2

Read full topic

@Ellibereth wrote:

I think it would be nice if there was a way to see the set of all posts one has bookmarked from a particular topic while looking through said particular topic.

Visually doing this in a “filter” format similar to when one filters by poster may be a good way of displaying the bookmarked posts, but displaying them in a similar way to how they are displayed in activity/bookmarks can also work.

This makes it easier to find a particular set or a singular post when someone has a large amount of bookmarked posts.

Sorry if this was suggested before.

Posts: 2

Participants: 2

Read full topic

@carlokok wrote:

Earlier today I started an update of a plugin (discourse-assign) and all it pritned was the header (“this can take a while”). after 10 minutes it still said the same so I tried the reset button, which didn’t do anything. Figuring I might as well do a rebuild I did the app rebuild but it’s still on that status:

afbeelding.png1182x620 31.8 KB

And reset doesn’t work either. How can I manually reset this?

Posts: 5

Participants: 2

Read full topic

@Resurgent wrote:

Screenshot_20180507-143508.png720x1280 134 KB

In the notification list panel, The downward pointing arrow is missing. The use of this arrow is to open all the notifications.
The arrow many times dont come. Sometime it comes.
Plz Fix this bug.

Posts: 3

Participants: 2

Read full topic

@FauxTony wrote:

Hey everyone,

I’ve noticed the below behavior for plugins, any idea what might be causing this? I have tried rebuilding app and some different things, but no luck.

Appreciate any guidance!

Posts: 1

Participants: 1

Read full topic

@moebis wrote:

After completing the interactive discobot training, the certificate.svg is blank or image not found.

Screen Shot 2018-05-07 at 4.01.58 PM.png1660x1424 153 KB

Posts: 1

Participants: 1

Read full topic

@eviltrout wrote:

Did you know that Discourse has had the ability to anonymize users for quite some time? Lately we’ve improved it so the scrubbing involved is even more thorough.

How do I anonymize a user?

At the bottom of a user’s admin page, there is an “Anonymize User” button:

image.png700x302 13.8 KB

You’ll be asked to confirm. If you agree, the user will be anonymized.

How thorough is the anonymization?

• A new username will be randomly assigned to the user such as anon123456. This new username will be applied to all their posts in the system, and we will update all @mentions and quotes too.

• Their email, name, date of birth and avatar will be removed

• Their user profile will be removed

• Any api keys generated for the user will be revoked

• Any authentication mechanisms (google/facebook/etc) will be revoked

IP History

Discourse will retain the user’s IP addresses in our logs associated with the anonymous user. However, there is a new mechanism to clear those out too available to developers.

When using our UserAnonymizer class, you can pass in an :anonymize_ip option with an IP to replace, for example 0.0.0.0.

If provided, Discourse will go through several tables in our system and update the IPs associated with the anonymous user to the new value.

If you’d like to enable this feature on your Discourse, we recommend creating a plugin to handle your particular workflow.

User Deletion

It’s worth mentioning that new users can delete their own accounts. If you sign up for a forum and regret it, you can back out as long as you haven’t had too much activity.

A note about GDPR compliance

A lot of people have been talking about the new GDPR regulations coming into effect in Europe this year, specifically the Right of Erasue and how that applies to their web applications.

The anonymization tools in Discourse are available to all administrators, but we recommend you contact a legal professional if you require GDPR compliance. Said professional will be able to audit your systems and tell you if you meet the requirements.

Posts: 1

Participants: 1

Read full topic

@HappyGezim wrote:

Inside a specific topic, can I create a message that’s only visible to users that belong to a specific group?

Posts: 2

Participants: 2

Read full topic

@gabrieltonon wrote:

Are they created following a simple arithmetic pattern? Also, are they based for the entirety of an instance, or only personal accounts? I’m using the API and seeing some inconsistencies.

Posts: 4

Participants: 3

Read full topic

@Drew_Warwick wrote:

The global flag list has a “Flagged By” field, but I’m not seeing a way to filter by that. Is there any way for me to view a list of past flags a given user has submitted?

Posts: 2

Participants: 2

Read full topic

@sarahann wrote:

I am not sure if this is a feature of Discourse or it’s a bug, but maybe let’s try to have a discussion about it!

Prerequisites:

1. Discourse setup to use a blob storage for assets

Steps:

1. Upload “image.png” (either using the discourse theme cli or by clicking ‘add’ button under [your_theme]->uploads->add)
2. Notice that if you inspect the anchor href of your newly added asset (using dev tools) it’ll be “[your_blob]/user-uploads/original/1X/[hash].png”. This works great.
3. Delete [hash].png in the blob storage
4. Repest step 2 - re-upload your asset
5. Repeat step 3 - notice the url is the same ("[your_blob]/user-uploads/original/1X/[hash].png") and the asset is unable to be found.

I have gotten around this issue with images, I’d change the integrity of it (crop it very slightly, change opacity etc…).

But my main problem is with fonts that have been previously uploaded, I cannot just add spaces to them to get Discourse to re-generate a proper hash for the font. So essentially, because the font existed at one time and is now deleted I can’t seem to use that font again (unless I manage to change the integrity which causes the font to not work because it’s not in the right format).

This makes me curious about a few things:

1. Does discourse store asset URLs somewhere? How does it re-generate the same URL for each asset?

• Is the hash determined by hashing the asset (and would therefore always be the same as long as the asset is the same)?

2. Is there a better way to delete assets that have been uploaded to a blob? Possibly deleting it from the blob throughs Discourse’s tracking off

I’ve also noticed that when I change the name of the file in my /assets folder, then re-upload my theme (I use the discourse CLI tool) the asset continues to have the same name in [my_theme]->uploads->add.

Anyways, I was hoping someone could help me understand this a little better, cause I think I must be missing something

Posts: 1

Participants: 1

Read full topic