Jump to content

mpierre

Member
  • Posts

    7
  • Joined

  • Last visited

Everything posted by mpierre

  1. So I am guessing I should post a support request on this?
  2. It worked, except for one tiny thing: I have setup the billing on the 1st of the month with the cost of the second month on the 15th. we have an add-on, which is NOT pro-rated, and when we place an order after the 15th, it only bills one month of the add-on, not 2...
  3. But if we use prorated billing, than all clients will be charged on the same date? If a client orders his first package on the 17th, I would want him to always be billed on the 17th, even on future orders. If another client signs up on the 13th, I would want him to always be billed on the 13th, even on future orders. Do I just keep the "Enter the day of the month you want to charge on" value to 0? Do I create 30 different products each with a different day of the month so that a client will always order the same package? At worst, I can change our procedure and bill everyone on the 1st of the Month, that's what my sales crew wants anyway, but it makes the first month hard to calculate in advance.
  4. Hi, We have 1 product we offer which we bill monthly and for which we want the client to have the same day of the month for them. If their first product is ordered on the 15th, and their second is ordered on the 10th of the next month, the client would only pay for 5 days and he would be billed on it on the 15th of every month. Prorata is turned off in the settings, and both orders will come thru the API. This is how we place the orders right now: $postfields["action"] = "addorder"; $postfields["clientid"] = $customer; $postfields["pid"] = "62"; $postfields["domain"] = ""; $postfields["billingcycle"] = "monthly"; $postfields["paymentmethod"] = "[our gateway]"; $postfields["responsetype"] = "xml"; $postfields["clientip"] = $_SERVER['REMOTE_ADDR']; $whm = MakeWhmcsApiRequest($postfields); The only ways I can see to achieve out goal is to do one of these: Method A ) Manual invoice: 1 ) set noinvoice to TRUE on the order 2 ) once the order is placed, we manually create the invoice, but we do not link it to the package 3 ) We modify the package to expire on the 15th, so that it will be invoices on that date, and hopefully, on the following months, it will keep the 15th and not the 10th as the billing date. Method B) Price override 1 ) Set a priceoverride to the prorated rate, so that the invoice says the right amount, sadly, it will not have the right expiration date 2 ) Once the invoice is paid, modify the package to expire on the 15th, so that it will be invoices on that date, and hopefully, on the following months, it will keep the 15th and not the 10th as the billing date. I don't really like B because the first invoice isn't as clear. Is there another solution? Is there a way to modify the call to addorder so that I can specify it's not for a full month with an actual rate and expiration date?
  5. Hi, My WHMCS is in French and English, as I have customers in both languages. My problem, is that my products need to have both names, such: --------------------------------------- Dedicated Server / Serveur Dédié --------------------------------------- And both descriptions: ---------------------------------------------- A dedicated server with blah blah blah / Un serveur dédié avec blah blah blah 256 bytes of monthly bandwidth / 256 octets de bande passante mensuelle 2 MB of memory / 2 Mo de mémoire 1.44 mb of disk space / 1.44 mo d'espace disque $940 per support ticket / 940$ par billet de soutient --------------------------------------------------- Which just looks AWFUL on the shopping cart. So, I have 3 proposals: 1) A marker which divides the list, for example, we could problem English as language 1, and French as language 2, and || as the divider. The title would then be: Dedicated Server||Serveur Dédié. When the shopping cart displays it, it does an explode( '||', $title) on it and selects, depending on the language, which one to use. If || is not present, it always use the English one, so it's backward compatible. This would also be supported for the add-ons, modules, etc... 2 ) 2 new field in the products called "Language" and "Parent Product" which allows to specify the language of the product, and the original translation. That way, we can define 2 different product, one called "Serveur Dédié" and the other called "Dedicated Server". When the shopping cart is in English, only the English ones show up. When the shopping cart is in French, only the French show up, BUT, it also shows the products which DO NOT have a French translation, so that it is backward compatible. As for options, add-ons, etc... they can already point to only some products, so the french options would be linked to French product and the English options would point to the English products, that way, nothing to do. Of course, if clients can upgrade/downgrade themselves, it might complicate things, but we can filter on it based on their language preferences. 3 ) Allow us to put a <span class="frenchtext"> or <span class="englishtext" in any of the fields (right now, it's filtered out), and add to the body tag the class [language]body so that when it is in english, the class is englishbody, allowing us to set .englishbody .frenchtext{ display: none; } and .frenchbody .englishtext{ display: none;}. That third one is the one that requires the least amount of changes from Mondernbilling and might even be possible in the template, I will have to investigate. I am even willing to code any of the 3 options myself, if WHMCS give me access to the appropriate source code, and to give my copyright to them (in other words, that they are allowed to put what I wrote in a future version). I wouldn't mind getting a live help license for free in exchange, but I wouldn't require it ;-) In case they don't know me, I wrote several modules for ModernBilling (and internal function) before it was acquired by Plesk, and I had a special developer license with 90% of the source code. I am a senior PHP developer with over 12 years of full time experience.
  6. All of my servers will be down for a few minutes this week-end as we change the power distribution. I would like to send an e-mail using a template to all our customers with an active hosting account or dedicated server, but not those with just domain name hosting. Is there a way to do it easily?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated