-
Welcome to the Chevereto User Community!
Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.
Please keep in mind:
- This community is user-driven. Always be polite and respectful to others.
- Support development by purchasing a Chevereto license, which also gives you priority support.
- Go further by joining the Community Subscription for even faster response times and to help sustain this space
-
Chevereto Support CLST
Support response
- Extra Support is delivered within 24-hours.
- Pro Subscription ticket response time is within 7 days on Software Support, Bug Tracking and RFC.
- Bug Tracking requires an active Chevereto self-hosted subscription.
- Community Help is user driven. Be polite with other users and do not expect official support.
Support checklist
- Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
- Confirm that the server meets the System Requirements
- Check for any available Hotfix - your issue could be already reported/fixed
- Read documentation - It will be required to Debug and understand Errors for a faster support response
Getting 3 notification email for update available.
- Thread starter mkerala
- Start date
- Status
Actually... I think that the problem here is the same as the stats stuff. Websites with heavy traffic trends to overlap this functions. To put it simple: The ping update is included after 24 hrs of the last ping update, it is rendered by a random user and then it reverts to the 24hr span. If your website has several hits per second the thing that will happen is that when one client process the ping update, maybe another user (or users) also process the ping update and the thing fires the notification more than once. We are talking about request that happens almost at the very same time.
Stuff like this is hard to debug and I haven't been able to reproduce it so I have to work blind here. It is harder when you consider that I can't rely in the database because you have too much requests per second and the database is lagged (or delayed, whatever is the right word for it).
To be honest, I don't know if there is a way to stop this concurrent process without rely in a file locker or something like that. A file operation happens extremely fast compared to a MySQL statement so I believe that I will have to put a file locker here. I mean, I can do it using memory but a file based system is more reliable and universal for this purpose.
Stuff like this is hard to debug and I haven't been able to reproduce it so I have to work blind here. It is harder when you consider that I can't rely in the database because you have too much requests per second and the database is lagged (or delayed, whatever is the right word for it).
To be honest, I don't know if there is a way to stop this concurrent process without rely in a file locker or something like that. A file operation happens extremely fast compared to a MySQL statement so I believe that I will have to put a file locker here. I mean, I can do it using memory but a file based system is more reliable and universal for this purpose.
- Status