forked from asmecher/pln
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Plugin is unable to cleanup after journal is removed #68
Comments
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
…nabling the plugin
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
…nabling the plugin
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
jonasraoni
added a commit
to jonasraoni/pln
that referenced
this issue
Feb 23, 2023
This was
linked to
pull requests
Feb 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's some code to cleanup data here:
pln/PLNPlugin.inc.php
Line 92 in 49f2b90
But it depends on a non-existent hook, and at the administrative part (
/admin/contexts
) where the journal is supposed to be removed, standard plugins are not loaded, so there's no way to listen for the right hook (Context::delete
).The cleanup might be done inside the scheduled task.
Another possibility would be to investigate the behavior of enabling the "site-wide" setting, which would be the only way to get the plugin loaded at the right time.
The text was updated successfully, but these errors were encountered: