WHMCS John

Hi all, We've been able to reproduce this behaviour when there is some kind of connection problem with the app reaching the WHMCS installation; for example if the URL or API Key entered in the app is no longer valid. Do either of those scenarios sound familiar to those experiencing this problem?

Hi @zitu4life, Thanks for your feedback and testing the v8.0 beta. You are comparing two slightly different types of interface; the first is a modal and the second is a popup window. As we work on a particular area of the software, the associated pages within the admin area are typically updated to a modern UX where appropriate, and that often involves the use of modals. That said, there might be interfaces where a popup window just makes more sense or works better. I'm not currently aware of a conscience design direction to move towards a completely white-label admin area. Whilst the client area is intended to be customisable and contain no references to the underlying software, the admin area is not. For example admins will need to refer to our documentation and help guides to use the software, so I'm afraid I don't see the benefit that obscuring the software name would bring?

Hi @bady, I've been able to reproduce this on my side as well, so have opened case CORE-15016 with our development team for further review. Thanks for taking par in the pre-release testing and sharing your feedback.

Hi @CodeCo, This isn't something currently planned for v8.0, but please do lend your support to the feature request: https://requests.whmcs.com/topic/make-it-possible-to-have-seo-urls-for-all-the-pages-including-cart-and-members-area Our approach to date has been that as a section of the client area is revised the file path is typically switched over to the new friendly URLs system. So for example the Payment Methods work made the credit card mangeent parts of the client area use Friendly URLs, and the Users and Accounts work updates the password and security settings pages.

Hi all, Thanks for sharing your feedback on the sidebar appearance. The icons have been updated with FontAwesome, the colours given an update, and it's been squared off a bit to provide that modern feeling that works well in mobile view. I would be interested to see some examples of sidebars in other software that you have in mind; both in browser and mobile view.

H @BackupAddict, We have received a further report of this, which I have been able to reproduce, and as such have filled case ID CORE-14994. As a workaround, please navigate to Configuration > System Settings > General Settings. Switch the Friendly URLs mode to Basic URLs.

Hi @BackupAddict, Thanks for sharing the full error message. First to confirm the scenario: You have a user associated with one or more account. Login as the User At index.php/user/accounts you are prompted to choose an account Clicking either option results in a Page Not Found error. Is that correct? To troubleshoot: First please try resetting the Friendly URL settings using the refresh button under via Configuration > System Settings > General Settings > General tab. Next review Configuration > System Logs, for any errors at the time of accessing the page. If the issue persists after that, can you please open your browser's network analyser tool, reproduce the error and share the Headers from the POST made to /user/accounts.

Hi @Hal9000, Thanks for taking part in the pre-release testing. Can you please confirm which version of the Ioncube Loaders you have? In our testing PHP 7.4 is working with the latest loaders (10.4.1). It may be that Plesk have not yet cascaded this out. I expect that cPanel will be making these loaders available in the next week.

Dynamic Field Translations can be quickly switched off via: UPDATE tblconfiguration SET value = '0' WHERE setting = 'EnableTranslations'; Then re-run the update via the /install/install.php file Once completed, Dynamic Field Translations can be switched back on via Configuration > System Settings > General Settings > Localisation tab

Hi @Nesooo, Thanks for your feedback. After consideration we realised that the change status workflow in the current app vs the new app involves only a single extra step: Current: Edit > Change Department > Select Department New: Edit > Department > Select Department > Save The biggest benefit of the edit page in the new app is that multiple changes can be made at once. Meaning the process of changing the department and status at the same time is 50% quicker. So whilst we won't be making this specific change, please do keep testing and sharing your feedback!

Hi @Joehighness, This app is free to everybody for the duration of the Technical Preview: https://www.whmcs.com/preview/mobile Thanks for your support ticket, I can see it's been directed to our feedback team. You can download the current production app for (which requires a subscription) via the Google Play link at https://www.whmcs.com/mobile-apps/

Hi @cyberhostpro @radwebhosting Sorry to hear you're experiencing this problem, this isn't something we can reproduce on our iPhones here. Could you please share with model and OS version you are running in this thread, so that we can collect information for troubleshooting purposes:

Hi all, If you're experiencing this error in v7.10.2, please refer to this documentation to troubleshoot the cause: https://docs.whmcs.com/PayPal_Checkout#An_unknown_error_occurred._Please_try_again @JesusSuarz This hotfix does not apply to v7.9. Please apply the 7.10.2 update.

Hi there, We've determined that similar errors to this have been caused by modifications to the MySQL database schema - presumably the result of an after-market module. In the cases our technical support team have handled, one or more of the following additional columns had been added to the tblinvoiceitems table: status created_at updated_at We also found evidence of some custom triggers added to tblinvoices and tblorders. Please consult with the vendor of your after-market module vendor on the presence of these tables and suitability of removing them. At the time of writing, these fields are not used by a stock WHMCS installation. The standard schema for these tables is described by the schema.sql files in the /resources/sql/install/ directory. I recommend consulting with a qualified database administrator to restore the modified table schemas to their original state.

Hi there, We've determined that similar errors to this have been caused by modifications to the MySQL database schema - presumably the result of an after-market module. In the cases our technical support team have handled, one or more of the following additional columns had been added to the tblinvoiceitems table: status created_at updated_at We also found evidence of some custom triggers added to tblinvoices and tblorders. Please consult with the vendor of your after-market module vendor on the presence of these tables and suitability of removing them. At the time of writing, these fields are not used by a stock WHMCS installation. The standard schema for these tables is described by the schema.sql files in the /resources/sql/install/ directory. I recommend consulting with a qualified database administrator to restore the modified table schemas to their original state.