I am running DNN 7.4.1. I was having some issues with the accuracy of real-time calculations from UPS, but they were pulling from UPS. I briefly switched the Freight Charges Type in the Store Settings to use Freight Weight calculations. This did not work for my purposes, so I switched it back to the Real-time rate calculations, but it will no longer pull the rates from UPS as it did before. No other settings have changed to my knowledge. All the UPS web service settings in the store settings are the same as they were previously. The only shipping rate that it shows now is the custom shipping rate that I have set up in the Shipping Rates Module. I am new to DNN, so any help would be much appreciated. Thanks Screen shot: Shipping Calculator not showing UPS Rates
I found in the DNN Event Log that I was getting error responses from the UPS API saying that the UPS Access Key and Password were missing. I am assuming that DNN cleared those two fields from the store settings for security reasons when I switched to use the Freight Weight calculations. Once I added back the Access Key and Password it began pulling the UPS rates as normal. I incorrectly assumed that all the settings were the same since I hadn't touched them.
Related
I currently embed my Power BI report to my website by create Azure AAD and upgrade power bi user to PRO license, and follow the guideline from github. It worked well in testing environment. By this way I can do the filter, each of my customer can only see their data. But I found that if I want to implement in production environment I have to register Power BI Embedded service from Azure. It's quite expensive, the lowest option allow only 300 renders/hour, if I have 100 customers and they often refesh the embedded report, It would hit the limitation.
Is there any other way to embed power bi report to website with lower cost?
It is quite expensive. Here is the full list of Power BI embedded pricing:
https://azure.microsoft.com/en-us/pricing/details/power-bi-embedded/
The PowerBI bills on an hourly rate based on the type of nodes deployed. So if you don't keep your instance active and shut it down after 5 minutes, you'll only owe about 10 cents per month. If you need to have your embedded content loaded all the time this will definitely be a problem, but if you are okay with pausing the service that can save you some money.
I am using GAE for my product development. Now it is MVP version and in development phase. So the user traffic is still small.
But today (14:00 27th Feb 2017 UTC+7) when I saw the statistics I cannot believe my eyes. So huge numbers of requests and bandwidth. I am attaching here:
Abnormal resource usage
My request log and the App Engine Dashboard show the same traffic as usual (very small). So I think the Resource usage numbers is not correct.
Dashboard and Request log
Please explain me where the huge number of requests come from?
Here is the answer I got from Google Cloud Support. I am sharing below, in case someone get the same problem as I had:
The number of requests you see on your App Engine Dashboard is not 100% reliable as it sometimes reflect the only the projected usage not the exact usage. Your exact bill will only be reflected on your transaction history and it takes 24-48 hours for it to refresh to be able to display your usage for February 27, 2017. We can wait for 24-48 hours to validate that your transaction history will be the one to show your charges and usage.
And here is the final resource usage statistics
I'm creating a website which has a premium user feature. I'm thinking on how to design the database to store the premium user plan, and how to check it..
My main idea so far is:
Having 2 fields on the user table: premium (boolean) and expires (date)
When user does payment, it will calculate the plan duration, set premium to 1, and the expire date to the end of the duration
Every time I check if user->isPremium(), it will also check if it's expired.. if so, set it back to zero and offer a renewal
Aside from this, all payments /transactions will be recorded in a logs table for record keeping.
This is a simple design I thought, but since this is a common feature on many websites, I thought of asking you guys how do the pros do this?
This probably won't make much difference on the design, but I'll use Stripe for handling payments.
It looks good to me. It is simple and solves your problem.
Hint 1: Depending on the semantics of your premium and expires fields, you do not need both. You can just change your user->isPremium() to check if the expires date has passed. Make sure you also change how you handle offering a renew.
Hint 2: I am working in a system that handles plan subscriptions and I had to deal with the following cases:
Permit users renew/extend the subscription before expiration date.
Different prices for different durations.
Discounts.
The delay between bill generation and payment confirmation.
Users with pending payments trying to buy again.
Users asking to cancel current subscriptions.
Hope it helps.
We had an outage for our app shown on the dashboard below. There was no appengine outage notification and nothing on twitter so it looks like it was local to us. There was nothing noticeable in our logs (no increased failed requests, just silence). It lasted about 40 minutes and was noticed by our customers (we get about 1.5 requests per second). We are a paying customer but not premium (additional $500 per month) so can't email google about the issue. What's the best way to get more information / resolution of the problem?
Subscribe to the app engine mailing lists. There's usually a flurry of activity on the general one when !##$ hits the fan.
https://groups.google.com/forum/?fromgroups#!forum/google-appengine
There's usually a message posted to on the downtime-notify list too, but it usually shows up after a bunch of people complain. On the other hand, there's much less fluff to sort through.
https://groups.google.com/forum/?fromgroups#!forum/google-appengine-downtime-notify
In terms of resolution, you file a production issue (search for "production issue template" in that first mailing list), and wait.
I've chosen google-app-engine because of its scalability, and now I try to understand how much I will have to pay once I release the product.
I've looked back and forth in the google app engine documentation to find an answer for question and couldn't find. I found few details in the "Quotas" page, I found how much I can get for free and how much is the Billing Default Quota.
In Billing Page there are number for CPU, etc with Resource and Unit and how much it cost. But no where could I find how much will it cost me per channel calls/created, etc.
I can't even try to make calculations with what's in the Admin console, because the current numbers there now are 0 (since there are 2 users which are the programmers).
How can I be ready for the releasing of the product that (hopefully) will have a huge number of channels created daily?
Is there a page I missed, or is there a tool for calculating?
Thanks!
EDIT:
Moishe, thanks for the quick and readable answer. So here are some more questions:
1. Do you think - if needed - that I will be able to get even more quota for the number of channels? I saw there's a special form to ask for more quotas, but I'm not sure that includes the Channel-API feature...
2. Are there any posts you've made for "how to use channel-API efficiently"? I saw some stuff about reusing the tokens per user. Is there more?
Thanks again.
Creating a channel costs about 2.7 CPU-seconds. A CPU-hour costs $0.10. So, each channel created costs
(2.7 / 3 600) * $0.10 = $7.5 × 10^-5
So creating 1000 channels will cost $0.075, or 7.5 cents.
You'll also get charged the normal outgoing bandwidth costs for any data sent over a channel.
The CPU cost probably isn't the biggest concern; you're more likely to run into quota caps then running out of money. Paid apps are limited to 86400 channel creations/day (1/second).