-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
z-push-admin broken in v60 #2178
Comments
z-push-admin doesn't work. |
Seems like you found the solution yourself: https://discourse.mailinabox.email/t/version-60-for-ubuntu-22-04-is-released/9558/42 |
Just adding the summary from the MIAB forum into this specific issue to help it get resolved. The link @hija has provided above only provides part of the solution. cinergi summarises here: https://discourse.mailinabox.email/t/version-60-for-ubuntu-22-04-is-released/9558/53 I managed to get Z-Push to work with a few changes to the PHP files, without resorting to installing PHP 7.4: Edit /usr/local/lib/z-push/backend/ipcsharedmemory/ipcsharedmemoryprovider.php as per this post. Edit /usr/local/lib/z-push/policies.ini as per the above post. Add the symbolic links as per this post. Edit /usr/local/lib/z-push/backend/caldav/caldav.php as per bob4os's instructions at the end of this thread. |
Good points, @beemach. Do you know why changing the policies.ini is required? I don't see how this fixes any issues caused by using PHP8 instead of PHP7. |
Will this fix be pushed to the master branch any time soon? I don't want to be messing with the filesystem on my MITB box incase these changes break an official fix that get's released. |
I ran a script based on the above links and comments. It fixed z-push for some basic usage by a Microsoft Mail client... Your mileage may vary. |
#2236 |
Now that Z-Push is updated to 2.7.0 for v62, I've opened a PR to fix the rest of this issue #2263 You can create the below bash script and run as sudo to achieve the same.
Feedback welcome. (Edit: spelling) |
z-push-admin broken in v60
The text was updated successfully, but these errors were encountered: