AkkomaGang/akkoma
AkkomaGang/akkoma
17
68
Fork 110
Code Issues 145 Pull requests 16 Projects 2 Releases 21 Packages Wiki Activity

update nsfwCensorImage suggestion in config/description.exs #837

Merged
floatingghost merged 1 commit from norm/akkoma:update-nsfwCensorImage into develop 2025-01-05 15:37:09 +00:00
Conversation 3 Commits 1 Files changed 1 +2 -2
norm commented 2024-10-17 06:45:20 +00:00
Contributor
Copy link

Turns out this is also used to set the default values in adminfe, so
update this to the correct URL for the NSFW banner so that it doesn't
break if you reset this value.

Turns out this is also used to set the default values in adminfe, so update this to the correct URL for the NSFW banner so that it doesn't break if you reset this value.
update nsfwCensorImage suggestion in config/description.exs
Some checks are pending
ci/woodpecker/pr/build-amd64 Pipeline is pending
Details
ci/woodpecker/pr/build-arm64 Pipeline is pending
Details
ci/woodpecker/pr/docs Pipeline is pending
Details
ci/woodpecker/pr/lint Pipeline is pending
Details
ci/woodpecker/pr/test Pipeline is pending
Details
be692e3a59 
Turns out this is also used to set the default values in adminfe, so
update this to the correct URL for the NSFW banner so that it doesn't
break if you reset this value.
Oneric commented 2024-10-17 21:33:32 +00:00
Owner
Copy link

It seems like the hex id bit gets generated at frontend build time. Not sure what caused it to change, but it might be more future proof to leave suggestions empty just letting the frontend’s default fallback select the currently correct path

The base file in the frontend repo is src/assets/nsfw.png and it’s included as import nsfwImage from '../../assets/nsfw.png' in src/components/attachment/attachment.js for use as the default fallback

It seems like the hex id bit gets generated at frontend build time. Not sure what caused it to change, but it might be more future proof to leave suggestions empty just letting the frontend’s default fallback select the currently correct path The base file in the frontend repo is `src/assets/nsfw.png` and it’s included as `import nsfwImage from '../../assets/nsfw.png'` in `src/components/attachment/attachment.js` for use as the default fallback
norm force-pushed update-nsfwCensorImage from be692e3a59
Some checks are pending
ci/woodpecker/pr/build-amd64 Pipeline is pending
Details
ci/woodpecker/pr/build-arm64 Pipeline is pending
Details
ci/woodpecker/pr/docs Pipeline is pending
Details
ci/woodpecker/pr/lint Pipeline is pending
Details
ci/woodpecker/pr/test Pipeline is pending
Details
to e4332d06b5
Some checks are pending
ci/woodpecker/pr/build-amd64 Pipeline is pending
Details
ci/woodpecker/pr/build-arm64 Pipeline is pending
Details
ci/woodpecker/pr/docs Pipeline is pending
Details
ci/woodpecker/pr/lint Pipeline is pending
Details
ci/woodpecker/pr/test Pipeline is pending
Details
ci/woodpecker/pull_request_closed/build-amd64 Pipeline is pending approval
Details
ci/woodpecker/pull_request_closed/docs Pipeline is pending approval
Details
ci/woodpecker/pull_request_closed/build-arm64 Pipeline is pending approval
Details
ci/woodpecker/pull_request_closed/lint Pipeline is pending approval
Details
ci/woodpecker/pull_request_closed/test Pipeline is pending approval
Details
2024-10-20 05:01:47 +00:00 Compare
norm commented 2024-10-20 05:02:37 +00:00
Author
Contributor
Copy link

Setting the default URL to a blank string instead so it will indeed use the fallback set in the FE

Setting the default URL to a blank string instead so it will indeed use the fallback set in the FE
Oneric approved these changes 2024-10-26 21:55:56 +00:00
floatingghost deleted branch update-nsfwCensorImage 2025-01-05 15:37:09 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Oneric
Labels
Clear labels   
approved, awaiting change

   
broken setup

Issue arose from a misconfiguration by the admin, custom patches, manual db edits or similar

  
bug

Something is not working

  
cannot reproduce

   
configuration

This requires config changes

  
documentation

This is about human-readable docs

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
extremely low priority

   
feature request

Something new?

  
Fix it yourself

Support has been attempted

  
help wanted

Need some help

  
invalid

Something is wrong

  
mastodon_api

   
needs change/feedback

Issue or PR is stalled on response from the author or a third party

  
needs docs

   
needs tests

   
not a bug

   
not our bug

Bug in a dependency of ours (meaning we can't just fix it), or in another AP implementation or client interfacing with Akkoma (which needs to be fixed on their end)

  
planned

   
pleroma_api

   
privacy

   
question

More information is needed

  
static_fe

   
triage

   
wontfix

This won't be fixed

No labels
approved, awaiting change
broken setup
bug
cannot reproduce
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs change/feedback
needs docs
needs tests
not a bug
not our bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AkkomaGang/akkoma!837
No description provided.