I'm running a dedicated server and i like that my customers receive these updates from plesk 12,
But they receive an email every day.
Is there any way to make it so that they only get updates once a month?
I know i can disable/enable them via "Tools & Settings - Notifications" but i want to change the regularity of them.
APS updates notifications are sent as a part of Daily Maintenance task so it is not possible to modify the period.
Related
In a few weeks, I'd like to track subscription status etc. for my app.
I know about the server notifications that you can set up on App Store Connect - however, I haven't found a way to request a data set for all transactions that would have fired server notifications if they were already set up at a time.
Does Apple expect you to set up the receiving end for these notifications in advance, even if you don't need the data right now, or is there a way to request the past few years worth of notifications (or transaction information or whatever you want to call it) that you have "missed"?
What is "Subject to frequency limit" tag in Firebase Cloud Messaging? When I try to schedule the message there is on tag called "Subject to frequency limit", which further has two option
Subject to frequency limit
Custom
Once per user for this message
What does it actually mean, can anyone please explain? How will this option make difference to my scheduled Cloud messages.
Once per user for this message:
Every user will get this notification only once. If there are new users the next day, they will get the notification at the scheduled time. Users that already received that notification e.g. yesterday won't get it again.
Custom:
Then you can set Send no more than one message every x days. That means that every user will get that notification only once in x days.
E.g. if you set it to 1: Every user gets that notification daily at the scheduled time.
My app should get push notification on user defined time duration (like on each Monday 11 AM).
So for that App have to check for new updates on server (on background) on user defined date and time, App might not be running at this time, but it still has to check for new updates on server. If any update found, server will send push notification for the same.
How can I implement time based background process?
Thanks!
Why don't let the server do all that? I mean, you will have to do a post with the selected date by the user from the app, and the server at the selected time will send a push notification to that particular user (you know what user it is by his token id). Amazon Web Services works like that for example.
In the event management app I am building I require user notification functionality. Having never implemented something like this before, I am after some advice on how you would go about doing this.
Here are a couple of scenarios that will require notifications.
Scenario 1:
Each event in the system has a start date associated with it. If the event also has delegates assigned to it that have a status of 'Provisional', I would like to send a notification 3 days before the event start date to any users with the role 'Admin', informing them that there are still provisional delegates assigned to this event.
Scenario 2:
There are accounts in the system, and each account has an account manager assigned to them. Accounts can also have multiple contacts associated with them. An account manager is able to assign a note to the account which is tied to a contact. So they can, for example, create a note of the type 'Scheduled Call'. The scheduled call has a date and time associated with it, so if around 1 day before I would like to send a notification to the account manager, informing them that they have a scheduled call due for this contact at the specified date and time. I'd like to keep sending or showing this notification until it is dismissed or deleted.
Summary:
There are several other scenarios but these 2 cover the basic functionality. I guess my question is this, has anyone implemented this or can anyone tell me how you would go about implementing such functionality in Laravel 4?
Specific questions are:
Method of Implementation
How to Automatically Check for these Specific Scenarios. Cron or via IronMQ or similar?
Where to store the code. In a helper function or it's own controller?
Are there any other considerations I have missed? Thanks.
I think you would need some sort of scheduled task / CRON job. Using the scheduled task, you can then run php artisan YOUR_CUSTOM_COMMAND. Obviously you would need to develop your own commands to use. See: http://laravel.com/docs/commands
I am working on an iPhone app and I want to implement the new model of auto-renewal for in-app purchases. I am able to successfully implement transactions and can even get subscribed to the app, but what if the user cancels the auto renewal subscription?
How will I be able to know that it has been cancelled, and so not continue to allow access (once expired)?
You can find the expiration date of a user's subscription by sending a receipt verification to Apple's servers. Check out figure 1-3 on the In-App Purchase Programming Guide.
Basically the steps are:
On the device, get a transaction receipt for an in-app-purchase. Either one you've saved during a transaction or by calling [SKPaymentQueue restoreCompletedTransactions].
Send that receipt to your server. (This is preferred over trying to do a receipt verification with Apple's servers directly from the app, since that would require you to store your shared secret on the device.)
Send the receipt to Apple's servers from your server, and in the response look for a key named expires_date (expressed in milli seconds since Jan 1, 1970 GMT).
I used this guide to help me on the server side: Verifying Apple App Store Receipts For In App Purchases With PHP and cURL.
There is no way to determine if the user has auto-renewal turned on or off. Apple doesn't give you access to this information. The only way is to wait until the expiration date passes without a renewal.
if the receipt status is 21006 and there is a key named cancellation_date, then it's a cancellation, you can find the new expiration date in that key but it's a formatted date, if you need a better value to parse check for receipt['latest_expired_receipt_info']['cancellation_date_ms'] same as expires_date