You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2022. It is now read-only.
Using events would allow user to easily add custom functionalities.
Simple example: when an article is displayed, increment a counter and use this value to select the X most popular articles. They can also be used to notify an admin that an author has published an article, etc.
Back-end events:
ArticleIsCreated
ArticleIsDeleted
ArticleIsModified
ArticleIsPublished
CategoryIsCreated
CategoryIsDeleted
CategoryIsModified
Front-end events:
ArticleIsDisplayed
CategoryIsDisplayed
IndexIsDisplayed
I think that only the Request is required to access time, query parameters, IP, etc.
As for my previous suggestions, I can work on this feature and provide a PR.
The text was updated successfully, but these errors were encountered:
Great suggestions I really like the idea
I'll try to work on this today
Regarding the ArticleIsDisplayed event, I found this package to calculate the number of views for the models based on the IP but it has Redis as dep. https://github.com/awssat/laravel-visits
I think ArticleIsDisplayed will be postponed after I recreate the internal architecture of this package to allow external custom packages, then we can add this idea as an optional package like what I did with LaRecipe package
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using events would allow user to easily add custom functionalities.
Simple example: when an article is displayed, increment a counter and use this value to select the X most popular articles. They can also be used to notify an admin that an author has published an article, etc.
Back-end events:
Front-end events:
I think that only the Request is required to access time, query parameters, IP, etc.
As for my previous suggestions, I can work on this feature and provide a PR.
The text was updated successfully, but these errors were encountered: