Jump to content

disgruntled

Member
  • Posts

    617
  • Joined

  • Last visited

About disgruntled

disgruntled's Achievements

Senior Member

Senior Member (3/3)

0

Reputation

  1. That is because any modification within a function is done in the local scope. Unless the variable is passed into the function by reference rather than the standard manner of creating a copy then the internal modification is not available outside of the function. This means the second hook, no matter what its priority is does not have access to the changed "copy" of the variable. To pass by reference &$variablename, Bear in mind this does have implications, It alters the original which may not be the desired effect later in the program. you should choose the method that works correctly. Also, If you have two hooks for the same point that work on the same variable, you may be able to combine them both into one hook and thus any internal changes would be accessible in the second part you needed. If you cant, then passing reference is what you need but as i say, be careful with it.
  2. Why are you adding it to the language files? the configuration file is called up on every single page within whmcs. Add your foreach to that file just once and its added? unless whmcs will suddenly fall down because if it.
  3. Why you would require proof of concept for a feature request i cant think. But in any case, you have none. http://forum.whmcs.com/showthread.php?61614-WHMCS-module-to-connect-to-another-WHMCS-s-API this is just one example, there are hundreds just search API on the forum they date back years. I suggested this myself in the post as you will see. I don't claim proof of concept because reseller API's have been around pretty much as long as there have been resellers wanting them and I'm not silly enough to think i am the first person to ever have thought of it. Take a look at how whmcs works, it is an API, that interfaces with other API's. reverse it and you have what you need in place already.
  4. It is generated from the "setup > general > support" tab, you will notice there are options available. For instance you can use something like these as the ticket mask [companynamehere]: %n%n%n%i and you would get something like this [company]: 1238764 [companynamehere]: %a%a%a%i and you would get something like this [company]: abc8764 [companynamehere]: %A%A%A%i and you would get something like this [company]: ABC8764 This should give you your company name, plus three numbers followed by the ticket id. you have other options they will be apparent when you take a look.
  5. I have looked at 2CO, but they are US based being UK based i would have to convert all payments to USD, From what i can see they dont they dont support GBP, whether this means they dont support UK payments at all i will have to look into further. I should have stated im in the UK, sorry for the misunderstanding.
  6. I fear the writer may soon be redundant!, to be fair, they did state they added redundancy just not at the documentation level
  7. Stick. Unless your modules are updated by the authors before hand to allow you to commit to an upgrade (or yourself if made by you). because you will have an absolute nightmare with any modules that rely on the global smarty, and thats just the start with all the rewriting going on i would just hold on, at least for a couple of months, in the mean time you will be able to contact your module suppliers and find out if and when they will be updating them. For those that are not or will not you might be able to get the source if they are cubed because they are no longer supported, in this case, you could probably get whmcs to take a look at it and fix what you cant.
  8. In part i agree, IF and thats the only cause for me to agree, they have done some intensive re-factoring of the source code and made it function better than the original then yes charge for it, but if this is simply a case of, lets take some free code and charge for its usage, then remove it from the code and we can all stick to the free source code thanks. Further more, whats with this upgrades fees, if your going to keep on charging me for upgrades what was the point in having me pay for an owned license. The point in me buying it was to have no more outlay for the product. If i wanted to keep paying for the software time and time and again i would have just gone with the monthly licensing and not had an upgrade fee to pay! Just ran some calculations and actually the deal may not be so bad after all. on an unbranded owned license with annual upgrade fees it would take about 30 years to match the cost of monthly for 10 years. I guess that in itself is reason enough to buy an owned license
  9. Does anybody know of a card payment gateway other than paypal/google that will process a low volume of card transactions without the client needing to sign up? Im asking because some of my clients don't want an account with these gateways they just want to make the payments with their debit card and have done with it. Obviously i could look into a merchant account but to be fair i dont think the volume it would be cost effective,
  10. The only thing i can suggest is that you write up a script in your favoured language to export the data to a CSV file. Start by working out the data your accounting system wants and the order it should be in. Then match up this information with the data in the whmcs database. From here you can decide on the best way to get the data, account by account or as a list of accounts. which ever way you go, the brief outline is this: Gather accounting information Gather database information Put script together Choose the account(s), Pull the data and order to requirements Write it out to CSV file. Import into accounting software. your accounting documentation would be a good place to start Good Luck
  11. I have voted modern, but in actual fact i think the whole order form process needs a good overhaul. Basically, the modern look, with comparison features and slider optionals. and an extra list option I think all this ?carttpl=etc is outdated and bad for SEO, the form template should be set at product group level. that way any link to the products within that group would automagically be using the correct templates. My specs i would have Basic hosting, resellers, ssl all using a modern x comparison view Domains using modern x list view vps/dedicated using modern x sliders, lots and lots of sliders. As you can see, i have a preference for the modern template, but it needs lots of bells and whistles I have a slider template that ive been working on that does all the adjusting / pricing etc i just have not yet gotten it to work with the cart. Although, to be absolutely honest, i think its time that whmcs came as a stand alone api as well as a full blown system, or at least came with a more modular system where you can say, ok, i need the provisioning, the billing and the admin area but i dont need the front end. that would be cool i think for those that wanted it.
  12. I find myself commenting on whmcs upgrade process again. If whmcs are going to be making a major change such as removing the global $smarty then surely there should be plenty of notice about this ahead of any release so that the community devs can prepare a release of their addons to coincide with the new release. Failing that simple step how about a notice looking like this on the upgrade page. This Upgrade will break existing addons
  13. I just had this error message else where. It means that smarty hasnt been initialised in the script. could mean that the livehelp module will need an update also. in my hook i got around the notice easily enough right before my assign i added this. $smarty = new Smarty(); But looking a the location of your fatal error that wont help you as the file is cubed Edit, having gotten through the whole thread now, i see that there are fundamental changes, i guess there is a valid reason for it but none the less its a pain.
  14. Im not going to be bailing, i like whmcs, besides i own my license so im not throwing away good money. RE: update beta phases I have to agree, The phases need to be lengthened. beta phase a - major bug finding and reporting beta phase b - major/minor bug finding and reporting beta phase c - cosmetic bug reporting beta phase d - select group for final evaluation. only release when no bugs have been found for x consecutive days update release - Only a proven stable release. That might seem like overkill, but as somebody on this thread pointed out, this is a billing/business software there has to be extra checking going on.
  15. Thank you for your reply. I guess i am going to have to fall back onto some good old php/mysql grunt work.. and here was me thinking with whmcs using smarty those days were numbered. Never mind. I will take a look at that post and thanks again. EDIT: I just updated the first post with the version info, it seems the post your refering to isnt affecting mine, im not on 5.2 yet and until they fix the problems i wont be.
×
×
  • 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