Jump to content

Pipe permissions changes after upgrade

Recommended Posts

For the past few upgrades my piping has failed on me, instead of me receiving notifications of a new support ticket being raised, a delivery failure is sent to my client.

It turns out that at each upgrade, the permissions for pipe are changed from 755. It would seem that this has long been known about, yet continues to happen.

Does anyone have any knowledge as to when this will be fixed?


Share this post

Link to post
Share on other sites

I have the crons directory outside of public_html and the permissions is not changed when I use the automatic updater.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.


Important Information

By using this site, you agree to our Terms of Use & Guidelines