thebluehydrangea comments on Unable to purge deleted posts

Unable to purge deleted posts (thebluehydrangea.org)

submitted 9 months ago by thebluehydrangea@thebluehydrangea.org to c/piefed_help@piefed.social

9 comments fedilink hide all child comments

With the help of other users here I have finally been able to get a PieFed instance up and running! I am running 1.5.3 (Docker install) and I've run into one small problem...trying to manually purge deleted posts always redirects to a page indicating that an error has occurred, the post is not purged. I am not sure how I would go about debugging this, but I will certainly provide any additional information that one might need. I appreciate all the help, the best part about the fediverse for me has to be the community! 👍

Edit: included screenshot of error page.

[–] thebluehydrangea@thebluehydrangea.org [S] 2 points 9 months ago (3 children)

Very sorry, I briefly took my instance down thinking that I could somehow fix the problem on my own, unfortunately I am not seeing the replies to this post unless I view it on the original server...that's my bad. I did get the replies from rimu and others regarding the problem though, I appreciate very much that a fix for this issue is already in the works! May I ask how one would go about applying it, or would it just be a regular update?

permalink

fedilink

source

hideshow 3 child comments

[–] wjs018@piefed.wjs018.xyz 4 points 9 months ago (2 children)

If rimu is fixing it the way I suspect he is, then it will just be a regular update. Since you are running docker, here is how to make sure you are updating where you want. No need to run any of this until he pops back in here and lets you know that he pushed a fix to the 1.5 branch.

# Prerequisite - navigate to the pyfedi folder

# Bring down the docker containers
docker compose down

# Wait for all the containers to stop

# Check to make sure you are on the 'v1.5.x' branch
git status

# You should see near the top of this output 'On branch v1.5.x'
# If it says a different branch name, then probably stop here and ask for help
# Feel free to hit up the matrix room or chat.piefed.social for more realtime support as well

# Pull the updates and start docker back up
./deploy-docker2.sh

👍 1

permalink

fedilink

source

parent

hideshow 2 child comments

[–] thebluehydrangea@thebluehydrangea.org [S] 2 points 9 months ago (1 child)

Goodness, well that's certainly easy enough to handle, I'm glad that I did the Docker install after all 😁 Very impressive that a fix is on the way already as well, I will look forward to it as I've made a bunch of test posts that I've deleted on my instance and they are currently cluttering things up 👍

I will keep an eye on the thread for further developments, much appreciated once again!

permalink

fedilink

source

parent

hideshow 1 child comment

[–] rimu@piefed.social 4 points 9 months ago

Sorry, looks like the fix will have to come out in v1.6, available in a week or so.

In the meantime you can fix it manually by running this: (change postgres_container to your DB container)

docker exec -i postgres_container psql -U piefed piefed <<'SQL'
ALTER TABLE post_vote
    DROP CONSTRAINT IF EXISTS post_vote_post_id_fkey,
    ADD CONSTRAINT post_vote_post_id_fkey
        FOREIGN KEY (post_id)
        REFERENCES post(id)
        ON DELETE CASCADE;

ALTER TABLE post_reply_vote
    DROP CONSTRAINT IF EXISTS post_reply_vote_post_reply_id_fkey,
    ADD CONSTRAINT post_reply_vote_post_reply_id_fkey
        FOREIGN KEY (post_reply_id)
        REFERENCES post_reply(id)
        ON DELETE CASCADE;
SQL

permalink

fedilink

source

parent