WHMCS John

Hi @xyzulu, Your case is logged with the development team following your ticket, and this is still the case now. I'm pleased to hear that the CSS changes allowed you to complete the approval process, that us helpful for us to know. It was interesting that Google required approval for the apps, as we do not use any sensitive scopes. But it appears it may be related to the use of a logo on the consent screen. So another potential workaround in the meantime might be to leave the logo blank when creating the OAuth Credentials consent screen.

Hi @ju5t, CURLINFO_CERTINFO is used to obtain the certificate information for display. If this is empty, you're correct that WHMCS will also be unable to retrieve certificate data. Thanks for your feedback regarding the help article on that point, I have passed that on to the documentation team. The Help > System Health Check status page has a version check to advise on the appropriate version of cURL to return this data. We are also tracking the specific environments with this flaw. As yet we've been unable to reproduce on stock CentOS7 repos we set up for testing this. But please do keep that info coming: PHP version OS OS Version CURL Version Output from Test Script In 7.7.0 we added PHP path detection logic to the cron command on the Setup > Automation Page, to help users in EasyApache Multi-PHP environments specify the same PHP binary for web and the CLI. In 7.7.1 we fixed an illegal mix of collations error which was reported. This specifically applied to older installations of WHMCS made where the server's default database charset/collation was not utf8. The Collation error now being discussed is unrelated to certificate validation; it would not prevent the SSL check on page load or cause false positives/negatives. But does stop the checks being performed in the background by the daily automation tasks. The `mysql_charset =utf8` line is standard on all installations since v5.3 (released in 2013) so most people should have it. It's presence is recommended. Case CORE-13267 has been opened to investigate how this error could be negated for installations with an latin1 charset.

Hi @xyzulu, In order to use the Google Sign-in feature, it is not necessary for Google to review the integration. In my tests, creating a credential set does not require approval: https://docs.whmcs.com/Configuring_Sign-In_using_Google Therefore I'd be interested to hear the details of your project which necessitates this? Were you able to gain approval with the CSS changes suggested in this thread? These are the kind of changes we were be considering, so it will be good to have confirmation.

Hi @DennyS and @Vox WHMCS is looking for a "51" error code from cURL to determine that no SSL certificate exists. Provided a success response is returned, then cURL evaluates the certificate is valid, and WHMCS will report the same. What response code do you get when performing a cURL connection test from the WHMCS server to the domain in question please?

Hi there, I'm pleased to confirm that the iOS app can be used to accept orders, place new orders and look up client details. It can also be used to manage services, answer support tickets and create invoices, announcements and much more!

Hi @mytamhuyet, This is not an official feature of WHMCS, however there are a number of after-market customisations which may be of interest: https://marketplace.whmcs.com/product/2966 https://marketplace.whmcs.com/product/3158 https://marketplace.whmcs.com/product/4833

Hi there, If you are still experiencing this issue, can you please provide some information about your email server to help troubleshoot: Server OS and Kernel version: Mailserver and version (eg. Dovecot) Control Panel and version (if applicable eg. cPanel, Plesk etc) POP Port (as entered into WHMCS Setup > Support > support Departments > Edit)

Hi @happydog5954, The Invoice Selected Items button is used in two locations in the WHMCS admin area, it will override any invoice generation settings and force the next invoice to be generated immediately: https://docs.whmcs.com/Clients:Billable_Items_Tab#Invoice_Selected_Items https://docs.whmcs.com/Clients:Summary_Tab#Invoice_Selected_Items If you'd like the invoice to be generated as normal for the due date and don't wish to wait for the daily automation tasks, click the "Generate Due Invoices" link on the client's Summary tab or Admin Dashboard.

Hi @HarryAdney, After changing the assigned product manually, please click the "Change Package" Module Command button to send the command to the server.

Hi @anandarup, This is probably because a one-time payment is being made for the domains, but a subscription is being created for the products. It sounds like your PayPal account needs upgrading to accept PayPal subscriptions.

Hi @comauHOST, Here is the technical documentation regarding this requirement: https://www.enom.com/api/Domains Topics/AU_ES_PE.htm If your registrar does not yet require them, please refer to the following documentation to remove the fields: https://docs.whmcs.com/Additional_Domain_Fields#How_do_I_customise_the_fields_that_are_displayed.3F

Hi @rjsorto, I can certainly see how implementing two systems for users to choose from is appealing. From an implementation PoV it's more nuanced. It would essentially double the amount of work we would be committing to for the life of the feature; double the work creating the two distinct logics, double the testing for every release, double the ongoing maintenance, and there is an after-sales support cost in the added complexity too. Therefore before implementing any feature we carefully weigh up the cost to benefit ratio when making decisions about how new features operate. That said, we like to be responsive to user feedback, so if there is a demonstrable demand for change which tips the equation in favour of the benefit side (via the feature request system, here on the community, or from our in-person conversions with users) then we can certainly consider it for the future. I hope that provides a little more insight into the decision making process we follow 🙂

Hi @rjsorto, Namespinning engines do not check actual availability in real-time so as to provide fast suggestions. This is true of tools from eNom, ResellerClub, Verisign etc. We therefore added the check upon adding to cart to prevent users from adding unavailable domains to their cart. The feedback we received from users is that faster loading results are more important than accuracy.

Thanks for providing this example, it's most helpful. It's interesting to hear that "ubuntu18" is a value you would have accepted in the hostname field, because it sounds more like a server name than a hostname to me. In this event what was your typical procedure? For example would your staff need to contact the customer to determine the full hostname they want to use and then manually adjust it before provisioning the service?

Hi all, I'm interested to hear what kind of values you are using in the Hostname field that are not accepted by the validation introduced in v7.6? What is the use-case for that particular value?