Jump to content

aegisdesign

Level 2 Member
  • Content count

    52
  • Joined

  • Last visited

Community Reputation

10 Good

About aegisdesign

  • Rank
    Level 2 Member
  1. integration to sell .se and .nu domains

    One of the things I noticed today on .se domains is that the Additional Domain Fields only seem to be available to edit at ordering for the client or in WHMCS admin. A client can't go in to their domain whois settings and edit the additional fields afterwards. For me, this manifested as a domain we'd transferred in probably back in WHMCS 5.x, which had details at the registrar (we use NetIM) but that weren't showing in WHMCS v7.3 Admin (blank). When the client wanted to transfer out, it failed because of a missing id/vat no and they had no way of editing their details. Or did I miss a client area template change somewhere along the way?
  2. v7.2.1 Errors

    Check that your error_reporting really is set to 0. I was getting an Oops error so I explicitly set error_reporting to 0 in configuration.php. However, I was running PHP in php-fpm mode (FastCGI probably has the same problem) and if you look at the phpinfo() output it was ignoring what I had set in configuration.php and also in a local php.ini and using the servers master value of E_ALL! For me, it caused the cart to throw an exception (it passes a null to a foreach) and a couple of 3rd party modules barfed out too. I'm deftly sidestepping the debate as to why WHMCS now throws so many exceptions into the Whoops handler and why their developers haven't spotted their coding errors by running with E_ALL on in development/beta testing to weed out these.
  3. Version 7.2 Breaks 3rd Party Support Module Usage

    I had a similar issue on testing the beta. It wasn't until I noticed you had to click the small recycle icon next to the dropdown selecting the rewrite method that it worked. In the beta at least it wasn't writing the .htaccess file when you saved the settings, only when you clicked the icon. I don't know if they fixed this as the .htaccess was already in place when I upgraded my test environment to 7.2.1.
  4. Market Connect Prices

    No, it's not just you. I'm UK based also. With potential exchange rate fluctuations it's just not viable for Weebly and SpamExperts. The margins are too tight and in the case of Weebly, you'd be mad as a client not to go direct to them. SSL certs are potentially ok but you can get them cheaper elsewhere and you can sell non-Symantec SSLs which might be a definite requirement if Google pull support for them.
  5. Updated to 7.2.1

    Looks like you have the wrong templates. Check you've updated your 'six' theme. If you're using your own theme then you need to modify it to match the changes (quite extensive changes) in 7.2's 'six' theme.
  6. Themes for v6 also working for v7?

    To be fair, Github is a relatively recent event if you've been using WHMCS prior to v6. I speak from experience of diff'ing and merging templates from v3 onwards and trying to glean from the release notes what has changed and how it relates to your custom theme branch. When I started, my theme was quite different to the one provided by WHMCS but over the years, having to merge changes into your design, you end up not diverging too much or you're spending days doing an update. IMHO, it'd be much easier if there was a base parent theme for the release and custom themes were merely overrides like Wordpress does child themes or Prestashop does it's themes. ie. you have a support/templates/base/ folder and a support/templates/my_custom_theme folder WHMCS then looks for say header.tpl in my_custom_theme and if there is none, gets it from base. That way, if the auto-updater updates templates, you get the new template updates in base but your custom changes are still used. For a long time WHMCS was stuck on a really old version of bootstrap which meant the themes were using old bootstrap syntax. Merging it in with a site design based on an up to date version was a nightmare.
  7. VATMOSS & EU VAT changes

    Thanks brian! I'm not sure that thread answers it but yes, WHMCS Ltd are in the same situation whereby they're selling digital goods into other EU states and will have to change their accounting to comply. I'm VAT registered so I'm just going to have to suck up the extra admin for MOSS but this just seems to be likely to kill off small hosting companies, enforce VAT registration or at least stop them selling intra-EU.
  8. VATMOSS & EU VAT changes

    I'm wondering how WHMCS or anyone else is dealing with the changes in intra-EU sales coming in to force in January 2015? The change is that instead of charging VAT at the rate of the seller's country, it's at the buyer's country. There is no threshold so if a UK company selling hosting to someone in the EU is not VAT registered they will have to charge VAT to other EU states, account for it and submit accounts to every country in the EU they make a sale into. Or, in the UK at least you have to register for VAT, sign up with MOSS (Mini One Stop Shop) and submit EU VAT returns to MOSS and they sort out paying each country. You can read a very good summary about it from a UK perspective at http://rachelandrew.co.uk/archives/2014/11/25/how-small-companies-and-freelancers-can-deal-with-the-vatmoss-eu-vat-changes/ Presumably this requires quite a change in WHMCS in how VAT rates are applied at checkout, how sales tax reports are generated and in retaining data on the purchaser for the 10 years mandated by the change in law. And yes, before someone says it, it's utterly ridiculous for small businesses and freelancers.
  9. Admin summary ajax not working

    We had this also. In order to get the System Overview widget to appear we had to also enable the Orders Overview widget. I didn't dig much further but I would guess the javascript isn't getting loaded unless the Orders graph is loaded first. For us it's ok but I imagine other companies might not want their pure support staff looking at the orders stats.
  10. I use the Bootstrap based default theme mixed in with the older Portal theme and my own custom bits. Most of the files other than the header/footer work just fine copied into Portal so you get much nicer Bootstrap style forms, the Portal style client area and not the awful default theme client area and navbar. I am however about to entirely switch to a custom theme based on the Bootstrap 3 based code that Shaun Reitan is maintaining at https://github.com/ShaunR/template-bootstrap & https://github.com/ShaunR/orderform-bootstrap and would encourage others to do so. For that matter it would be great if WHMCS Ltd also switched to use ShaunR's work since there Bootstrap Default is years out of date.
  11. Linode Integration

    I found this today while looking to see if anyone has integrated Linode with WHMCS https://github.com/eksoverzero/whmcs-linode It needs a bit of work still but might help someone out.
  12. Upgrade from 5.0.3 to 5.2.2

    Changes in the templates are rarely documented fully in my experience and if they are often miss some of the files changed. I always do a diff (with FileMerge on a Mac) of the templates folder between versions to see what I have to change in my own customised templates.
  13. adeska, you should ALWAYS presume that an upgrade can go wrong. That is why you take a backup before you do the upgrade, so you can revert to your working system.
  14. YES! You need two licenses. You get a FREE dev licence if you bought through WHMCS direct, otherwise it's $45 one off. Apart from that, going live on day 1 of a new release is completely nuts. Everyone knows there's going to be wrinkles to iron out. You sit. You wait. You watch the forum. In a week or so's time when there's a consensus on problems, the 3rd party devs have updated their addons and there's possibly a bugfix release, you TAKE A BACKUP OF YOUR WORKING SITE, and install the update in the knowledge that it's safe to do so and you know what you're likely to hit.
  15. I'll be using PHPSelector from CloudLinux and letting my customers choose PHP 5.2/3/4/5 http://docs.cloudlinux.com/index.html?php_selector.html
×

Important Information

By using this site, you agree to our Terms of Use & Guidelines