pleroma/pleroma
4
6
Fork 12
Code Issues 720 Pull requests 83 Projects Releases 1 Packages Wiki Activity

Allow using schedule_at to post with a past date #7869

Open
mkljczk wants to merge 3 commits from mkljczk/pleroma:backwards-schedule-at into develop
pull from: mkljczk/pleroma:backwards-schedule-at
merge into: pleroma:develop
Conversation 2 Commits 3 Files changed 8 +212 -9
mkljczk commented 2026-04-06 22:15:55 +00:00
Owner
Copy link

i think i had a MR for this but i think that was shortly before the data loss? anyway this one's more complete by not allowing backdated posts to reply/quote others' posts and removing mentions from them

Checklist

  • Adding a changelog: In the changelog.d directory, create a file named <code>.<type>.
i think i had a MR for this but i think that was shortly before the data loss? anyway this one's more complete by not allowing backdated posts to reply/quote others' posts and removing mentions from them ### Checklist - [x] Adding a changelog: In the `changelog.d` directory, create a file named `<code>.<type>`. <!-- `<code>` can be anything, but we recommend using a more or less unique identifier to avoid collisions, such as the branch name. `<type>` can be `add`, `change`, `remove`, `fix`, `security` or `skip`. `skip` is only used if there is no user-visible change in the PR (for example, only editing comments in the code). Otherwise, choose a type that corresponds to your change. In the file, write the changelog entry. For example, if a PR adds group functionality, we can create a file named `group.add` and write `Add group functionality` in it. If one changelog entry is not enough, you may add more. But that might mean you can split it into two PRs. Only use more than one changelog entry if you really need to (for example, when one change in the code fix two different bugs, or when refactoring). -->
mkljczk force-pushed backwards-schedule-at from 2c543176df
Some checks are pending
ci/woodpecker/pr/changelog Pipeline is pending approval
Details
ci/woodpecker/pr/lint Pipeline is pending approval
Details
ci/woodpecker/pr/unit-testing-elixir-1.15 Pipeline is pending approval
Details
ci/woodpecker/pr/unit-testing-elixir-1.18 Pipeline is pending approval
Details
to 7a4571a762
All checks were successful
ci/woodpecker/pr/changelog Pipeline was successful
Details
2026-04-07 12:03:43 +00:00 Compare
Merge branch 'develop' into backwards-schedule-at
Some checks failed
ci/woodpecker/pr/changelog Pipeline was successful
Details
ci/woodpecker/pr/lint Pipeline was successful
Details
ci/woodpecker/pr/unit-testing-elixir-1.15 Pipeline was successful
Details
ci/woodpecker/pr/unit-testing-elixir-1.18 Pipeline failed
Details
bf03a47336
Merge branch 'develop' into backwards-schedule-at
Some checks failed
ci/woodpecker/pr/changelog Pipeline was successful
Details
ci/woodpecker/pr/lint Pipeline was successful
Details
ci/woodpecker/pr/unit-testing-elixir-1.15 Pipeline failed
Details
ci/woodpecker/pr/unit-testing-elixir-1.18 Pipeline failed
Details
d5e18bdf93
lambadalambda commented 2026-05-25 12:53:24 +00:00
Owner
Copy link

Can we rather add a specific endpoint / mix task for this? This is very unintuitive behavior...

Can we rather add a specific endpoint / mix task for this? This is very unintuitive behavior...
phnt commented 2026-07-16 22:12:27 +00:00
Owner
Copy link

Implementing user data restoration from backups would probably be a better UX. Especially since backups are already implemented.

Implementing user data restoration from backups would probably be a better UX. Especially since backups are already implemented.
Some checks failed
ci/woodpecker/pr/changelog Pipeline was successful
Details
ci/woodpecker/pr/lint Pipeline was successful
Details
ci/woodpecker/pr/unit-testing-elixir-1.15 Pipeline failed
Details
ci/woodpecker/pr/unit-testing-elixir-1.18 Pipeline failed
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u backwards-schedule-at:mkljczk-backwards-schedule-at
git switch mkljczk-backwards-schedule-at

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch develop
git merge --no-ff mkljczk-backwards-schedule-at
git switch mkljczk-backwards-schedule-at
git rebase develop
git switch develop
git merge --ff-only mkljczk-backwards-schedule-at
git switch mkljczk-backwards-schedule-at
git rebase develop
git switch develop
git merge --no-ff mkljczk-backwards-schedule-at
git switch develop
git merge --squash mkljczk-backwards-schedule-at
git switch develop
git merge --ff-only mkljczk-backwards-schedule-at
git switch develop
git merge mkljczk-backwards-schedule-at
git push origin develop
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
AP C2S

   
AdminAPI

   
Breaking API
Affects clients

  
Breaks existing config

   
Check if still valid

   
Data Protection

   
Do not merge

   
Document in the changelog

   
Doing

   
Feature Request / Enhancement

   
MastoAPI

   
NL2
Improved Mobile Experience

  
NL4
Improved instance customization and QoL options

  
OStatus

   
OTP Releases

   
Refactor

   
Security

   
To Do

   
TwitterAPI

   
bug

   
complicated

   
confirmed

   
deps

   
discussion

   
documentation

   
easy

   
feature: to be merged in stable

   
fix: to be merged in stable

   
incident
Denotes a disruption to IT services and the associated issues require immediate attention

  
needs to be backported to maint

   
needs-changes

   
needs-info

   
needs-review

   
performance

   
regression

   
unclear
No labels
AP C2S
AdminAPI
Breaking API
Breaks existing config
Check if still valid
Data Protection
Do not merge
Document in the changelog
Doing
Feature Request / Enhancement
MastoAPI
NL2
NL4
OStatus
OTP Releases
Refactor
Security
To Do
TwitterAPI
bug
complicated
confirmed
deps
discussion
documentation
easy
feature: to be merged in stable
fix: to be merged in stable
incident
needs to be backported to maint
needs-changes
needs-info
needs-review
performance
regression
unclear
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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
pleroma/pleroma!7869
No description provided.