Jump to content

WHMCS JimmyW

WHMCS Technical Analyst
  • Content Count

    6
  • Joined

  • Last visited

  • Days Won

    1

WHMCS JimmyW last won the day on June 17

WHMCS JimmyW had the most liked content!

Community Reputation

3 Neutral

About WHMCS JimmyW

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. In past occurrences, this error has been caused by a custom gateway leaving a hook behind for this particular payment method. I would recommend removing any related hooks you have within your /includes/hooks/ directory and any remnants of the payment gateway form your /modules/gateways/ directory and try to access the invoice again with the error. If this doesn't help to resolve the issue, you may wish to open a support ticket and we can have a closer look.
  2. Often, when creating helpful articles within the knowledgebase, it can be difficult to provide a large amount of information in such a small form and still ensure it is readable. In past experience, there has been occasions when a certain article needed multiple outcomes based on a clients decision. When i have been faced with this scenario, i have added a Bootstrap accordian style element into the knowledgebase article, allowing me to add styling that hides the unneeded information untill it is called by the user. WHMCS its self uses mutiple elements from the Bootstrap library. Using the Bootstrap 4 library, it is possible to add cetain styles and elements into the knowledgebase textfield. The best way to implement this would be click the “Enable/disable Rich Text Editor” button. From this point you can add your HTML and call most of the Bootstap tools. In this particular scenario, i called the accordion class as seen below. <div class="accordion" id="accordionExample"> <div class="card"> <div class="card-header" id="headingOne"> <h2 class="mb-0"> <button class="btn btn-link btn-block text-left" type="button" data-toggle="collapse" data-target="#collapseOne" aria-expanded="true" aria-controls="collapseOne"> Collapsible Group Item #1 </button> </h2> </div> <div id="collapseOne" class="collapse show" aria-labelledby="headingOne" data-parent="#accordionExample"> <div class="card-body"> Some placeholder content for the first accordion panel. This panel is shown by default, thanks to the <code>.show</code> class. </div> </div> </div> <div class="card"> <div class="card-header" id="headingTwo"> <h2 class="mb-0"> <button class="btn btn-link btn-block text-left collapsed" type="button" data-toggle="collapse" data-target="#collapseTwo" aria-expanded="false" aria-controls="collapseTwo"> Collapsible Group Item #2 </button> </h2> </div> <div id="collapseTwo" class="collapse" aria-labelledby="headingTwo" data-parent="#accordionExample"> <div class="card-body"> Some placeholder content for the second accordion panel. This panel is hidden by default. </div> </div> </div> <div class="card"> <div class="card-header" id="headingThree"> <h2 class="mb-0"> <button class="btn btn-link btn-block text-left collapsed" type="button" data-toggle="collapse" data-target="#collapseThree" aria-expanded="false" aria-controls="collapseThree"> Collapsible Group Item #3 </button> </h2> </div> <div id="collapseThree" class="collapse" aria-labelledby="headingThree" data-parent="#accordionExample"> <div class="card-body"> And lastly, the placeholder content for the third and final accordion panel. This panel is hidden by default. </div> </div> </div> </div> After all of this is added to the KB article, saving would then result in the article contents being dislayed within an accordian whenever a client views the article, allowing the client to select the information that is needed.
  3. Having clients organized into groups offers some great benefits ranging from being able to identify certain level of clients, to offering automatic group discounts. If you ever need to manage or remove a large number of clients in order to delete a particular group, WHMCS doesn't currently provide a mass deletion option in the UI. There are alternative options that may save you time to bulk update. As an example, this action could be performed directly within the database. Firstly, you would need to identify the ID of the client group that you are wanting to empty. This can be identified by checking within the tblclientgroups table. The entry in the `ID` column is the value we need to retrieve. An easy way to do this would be to identify the `group name` and use the `id` from the same row. Finally, using the SQL query below, it is possible to remove all clients from a specific client group using the ID you have just located. UPDATE `tblclients` SET groupid="0" WHERE groupid="X"; In this scenario, you would simply need to update the “X” with the group ID from tblclientgroups. Using the above command and updating the “0” to another group ID, you would also be able to move all clients from one group into another. Please note: performing queries directly to the database is not something that is typically recommended. This is provided only as an example. We are unable to offer any guarantee this query will work with future versions of WHMCS. As with any change made to a WHMCS installation, we do recommend ensuring you have a full database backup prior to starting. This backup would allow for a swift resolution should any errors occur.
  4. HI masoodsajedi, Cron Tasks that hang at this step are typically caused by a large database backups. I would recommend checking your backup process and changing to an alternative backup method. Once you have changed the backup method, re-attempting the same terminal command, should hopefully allow this to complete successfully. Regards
  5. Hi Daniweb, The most likely reason you are seeing inconsistencies within the client are is likely due to the way WHMCS makes many of its API queries. Typically the return information looks to be returned to the System URL rather than any alias. As a result this information may not be passed back to your alias or may be rejected at the registrar due to inconsistencies with the URL in compared to what is expected. This is even more likely to be the case when retrieving domain information as this is called from the registrar upon almost every required page load rather than cached locally. As an investigatory measure, you may be able to see entires within your module log that would give you an idea of what is or is not occurring when you access your installation using your alias. I hope this helps.
  6. Hi sol2010, Could you please confirm what version of WHMCS you are using? The docs page you have referred to relates to WHMCS Version 7.10 and lower, however the invite feature was added within version 8.0. More information relating to Users and accounts within version 8.0 and above can be found here; https://docs.whmcs.com/Users_and_Accounts I hope this helps .
×
×
  • 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