Jump to content

yggdrasil

Member
  • Content Count

    1007
  • Joined

  • Last visited

  • Days Won

    9

yggdrasil last won the day on August 22

yggdrasil had the most liked content!

Community Reputation

72 Excellent

3 Followers

About yggdrasil

  • Rank
    Level 2 Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I purchased the pro version of font awesome for my site, and I was not able to integrate it properly with WHMCS as they had some classes hard coded. So there is that and ended with different versions for jQuery, Bootstrap and font awesome, one for WHMCS, one for the main site. That creates more work. I get what you say about SEO but its not just SEO but easy to remember URL's. I'm a keyboard person, I prefer to type things, including commands vs copy and paste. Having easy URL's for articles and others parts is helpful and I expect some of my customers are the same. I never cared about the SEO part but the URL structure. I would like to have my own since its the sitemap of my navigation. I never asked for a new admin template. If someone reads my posts I never ever complained about the admin part. That is something I can suffer, but the front end the customers see not. I don't mind as much customizing the admin site and I'm ok with one single theme that works vs having a new one. I care about simplicity when it comes to staff and admin tasks, I would actually make it as simple as possible so it takes as less clicks and go from one part to the other vs making it fancy. I agree with your points, the themes should rarely change because they are the basis on which others build their design. I agree with WHMCS philosophy here. Just ship one admin and one client theme, bare bones, simple but still nice and let others build what ever design they want on top or buy a theme from another company.
  2. This is a custom hook in your site. Sadly, hooks do not fail gracefully when they have an error, they just crash the whole system, yet hooks is the only way to modify some stuff. I consider them dangerous for this reason as they also now reveal internal information about your files and server to everyone... Be careful with the hooks you place in your installation and make sure to triples test them.
  3. The bigger question is until how long will v4 be officially be supported (security...)? It's not the best scenario to have outdated code running on public websites.
  4. If you check every other major release in the past 2 years the story was the same. They are quick to release new versions that hardly passed Beta. That should explain some of your questions. The trick is not to upgrade WHMCS when they release a new major version but wait for the smaller releases that keep fixing stuff.
  5. I'm aware of that. It's actually ironic that we need to wait WHMCS to update a software that is open source and free. This shows the current sad state of WHMCS when it comes to locking files and user end front code. They should not be encoding and putting open source code under their proprietary ioncube files. Other web softwares that use open source libraries don't do this. The ship them as they are and the customer is free to modify them as they see fit, that is the whole idea of why people use something like bootstrap (customization). If WHMCS was properly built the bootstrap version would be irrelevant. Someone could be using version 3, or 4 or 5, or not even use bootstrap at all for their theme. Every other softwares does not lock you into what you have to use for the website design. But I gave up on this a long time. We need to accept that Bootstrap 4 will be with us for years to come until they again decide to upgrade it. Having 4 after people asked for years is already a welcome feature.
  6. Because they are not a hosting company? You know how the phrase goes, jack of all trades master of none. It Its a very different business than software developing. They can potentially lose customers if the service is not top-notch (SLA uptime), support (replied instantly...). That sort of customer expects something very differently, even support that WHMCS does not have today. You don't try to cover all things that shine under the sun if you want to be successful. The big example is how WHMCS also offers custom development yet Modules Garden is far more successful not only making modules but taking all the work away from WHMCS when it comes to custom software because they only focus on development and nothing else while WHMCS tries to focus on other stuff as well. The second argument is maybe because WHMCS is a b2b business that sells to hosting companies and service providers? Imagine the following situation. A hosting company offering a reseller plan but then competing directly with its own customers or trying to sell directly to their customers. How many people do you think would actually want that service? When you do B2B you usually try your users and customers to trust you, not alienate them. This is why the marketplace was not very well-received either. Imagine if you are a company selling something like Weebly or SSL and you are a WHMCS customer, now suddenly they add your competitor in your control panel and to all other WHMCS users which would mean management would probably say "We should drop WHMCS" as they are promoting our competitors right in our the interface. This is no different from putting up a shoe store with Shopify, and they then add banners in your store to Amazon Shoes trying to divert your customers to their own affiliate program. There are some things you usually don't cross when you do B2B, that means you are selling to other business or people that sell to end customers. WHMCS never sold to end users. They sell to people that usually provide a services or products to others. Even if you are a developer or web designer.
  7. The reason a BETA is tagged that way is to install it on a test environment or not a live system. Beta will have bugs and issues. Never use Beta on your real website or production systems. Expect issues, problems and bugs, I don't think WHMCS support even covers Beta issues for that reason since it's just for testing and developing. Beta should be installed on a new installation, not upgrading from a previous version.
  8. No, they are 2 years minimum. I'm not sure why people would be willing to lose money by offering 1 year for domains that require 2 years length many people will not renew the second year, and they would have to cover the financial loss. It makes it look great and cheaper, but its a fact that if you offer 1 year, plenty of people will register a domain but never used it, as such they will not renew either.
  9. I'm not sure why they didn't just partner with some hosting companies to offer that model. It does feel a bit awkward that WHMCS sells hosting for software companies and now they also host services directly as well.
  10. Well, the new 8.1 Beta has bootstrap 4 support (finally). That could be a reason if you want to keep up with modern standard designs. They also introduced a child theme, not sure what is yet but maybe it makes it easier to integrate your design, or maybe it has the opposite effect, I guess we will have to wait and see. As for the 8.0.x, the only important feature I can think for upgrading is IDN support which is important if you are selling domains to people that speak different languages. The reason I don't upgrade is that while you get something new you probably lose older stuff that you are using right now. Upgrades or new software are only nice when they don't affect the other things you are using.
  11. Another option you could use, is set the billing for that product as 0 or free for that customer. And bill that customers using the Billable Items instead. That will create an invoice every month not related to the product. Then just change the product to the termination date (in 3 months). The product will not bill the user monthly anymore, he will receive a separate invoice created by your Billable Recurring Item instead. Take into account that WHMCS with products tries to bill the product. The sort of agreement you have is a bit more complex and probably is customized or enterprise type which probably is better off not using a product but a customized way to bill that person based on the agreement.
  12. I understand what you are trying to achieve and you probably are like me a number freak. It does bother me for example when I closed fraud accounts that now I have a useless ID I wil never use again. But this is not only true for WHMCS. For example, lets say a bug tracker like Mantis, also creates a unique ID per each bug, even if they are on different projects. Since one bug is just one more record in a table and the ID is created by the database system not the software. The thing is that most developers use this setting (auto increment) because it creates a unique ID on the database automatically and you need this for data consistency as everything can and will change (like username, or name), in the end the number that never changes (and should) it what identifies a unique item. And while you might use this customer identification purposes or product (I do) you need to stop worrying about the number and consider like a trow away setting. Don't completely rely on them and instead try to query the number for each customer in case it has changed (from other systems...) If you really need to match this to the old system, the only solution I can give you is to create dummy accounts in between the users that don't match an ID. Then if you someday register an account manually use one of those positions that hold temp data. Or the other solution is not to use the ID's from WHMCS and like someone else suggested create your own custom field, you can then have a hook that calls this automatically on each new customer registered but now you are replicating what WHMCS does and you need to babysit a parallel number systems that does the same. It all depends on how many customers you have. The logic thing I would do in your case, is just to import the customers in order and then change the ID on my other system to match this. You need to think which one is the most important one and the master. If your new ID's will be assigned from now on forward's by WHMCS (like registering new customers) then the logic here tells you that it's your other system that should take the ID from WHMCS and not the other way around. It would be easier just to change the ID's in the other system and then start with the new numbering system on WHMCS. This is the cheap easy way instead of creating a hook or a new number format. It all of course depends on how many customers you have, but if you need to start hacking around WHMCS then why not just create a script that does the same in the other system? Just create a script or some other task that gets the new ID for each old customers in WHMCS and then updates it automatically in your other platform/software. It's a one time job, and once finished just start using the new ID's created by WHMCS. Do not change or try to tamper with the ID's in WHMCS because they are used in several queries and tables to get data, you will end up with many troubles and your installation will always have troubles afterwards. The unique ID is the primary key in the database and as such has to match with other tables for data consistency.
×
×
  • 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