Jump to content

linux4me

Member
  • Posts

    64
  • Joined

  • Last visited

  • Days Won

    1

linux4me last won the day on November 21 2023

linux4me had the most liked content!

About linux4me

Recent Profile Visitors

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

linux4me's Achievements

Member

Member (2/3)

9

Reputation

  1. I was using the Twenty One theme as well, and discovered from a client that it was not possible to add an address through the client UI to update a credit card. I am able to reproduce the issue on another client account using the procedure below. I've tested on both Firefox and Chromium with a clear cache. The error appears in both browsers. To reproduce the problem, log in to the client area and go Billing -> Payment Methods, click Edit for an existing credit card, then Add a New Address. Fill out the form, and then click Save Changes. When you click Save Changes, nothing happens. The dialog stays open, and in the console, the following javascript error appears: Uncaught TypeError: No method named "destroy" _jQueryInterface https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:6 each https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 each https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 _jQueryInterface https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:6 clearFieldError https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:7 clearErrors https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:7 each https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 each https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 clearErrors https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:7 init https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:7 dispatch https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:3 handle https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:2 add https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:2 C https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 each https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 each https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 C https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 on https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:3 init https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:7 initAll https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:7 each https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 each https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 initAll https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:7 <anonymous> https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:8 l https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:2 fireWith https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:2 ready https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:2 s https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 promise https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:2 <anonymous> https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:2 <anonymous> https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 <anonymous> https://whmcs.mydomain.com/templates/twenty-one/js/scripts.min.js?v=7bf6c8:1 scripts.min.js:6:19698 I submitted a support ticket, and got this response: Based on that, I recommend you switch to the Six template, as even if you fix the issue you're having with Twenty One, you're still going to have problems until the next update.
  2. I figured this out thanks to this article. I actually did look at the documentation, but I didn't find this page. It turns out the problem was my phone. It's set to get the time automatically from Verizon, but it was three minutes slow! I manually set the time in the phone and was able to get 2FA working in WHMCS.
  3. I've been using two factor authentication (2FA) with time-based tokens for WHMCS with the Symantec VIP Access App for quite a while, but today when I attempted to log in to update WHMCS from v. 8.0 to 8.1, my code was rejected and I had to use the backup code. I went into the admin to reset 2FA for my account, and my App immediately recognizes the QR code, but WHMCS gives me the "The code you entered did not match what was expected. Please re-scan or enter the code and try again." I've tried several times, but no luck. The App still works fine with the other sites I use it with. Is this a bug with WHMCS?
  4. I'm using WHMCS v. 8.0.4 and the Stripe Payment Gateway. I had a client contact me to find out why their credit card was being declined. I checked their account, and it shows the card was declined by Stripe due to, "The zip code you supplied failed validation." I checked with the client, and he had moved to another state. After he updated his address in his WHMCS account--which I verified he had done on both the Profile and Contacts tabs, I tried to attempt capture of the invoice again, but it failed with the same error message. I checked the transaction at Stripe, and it was still using the old address. Okay, I thought perhaps an existing invoice wouldn't be updated with the new address, so I created a new invoice and tried to attempt capture with it. I got the same error, and confirmed with Stripe that it was still using the old address as well. I checked the credit card he had on file, and it shows the correct address in the Billing Address box. How do I get WHMCS to use the updated address for an existing and new invoices?
  5. I'm not sure I understand what you're asking, but if you're asking if there is a way to view the contents of the tblerrorlog table within WHMCS, I think you can do so by going Configuration -> System Logs, and it will go to the Activity Log by default. (You can change the log you're viewing using the links in the left sidebar.) If there have been errors, I believe in v. 8 they are still recorded in the Activity Log if you have "Log Errors" checked as described here.
  6. Maybe the other table doesn't have a "created_at" field that the query uses in the "WHERE" clause?
  7. I'm using WHMCS v. 8.0.2, and with System Settings -> General Settings -> General -> Limit Activity Log set to a reasonable number, I don't have to run an independent script to keep the activity log at a reasonable size. You can verify that Limit Activity Log is working by going Utilities -> System -> System Cleanup, and clicking the Advanced Tab. The "Prune Client Activity Logs" section will show you how many records are in the Activity Log.
  8. The first line: // Set the cutoff date for selecting/deleting records to two weeks ago. $date = date('Y-m-d', strtotime('-2 weeks')); sets a variable to a timestamp for two weeks prior to the current date, so that only records two weeks old and older will be deleted. the second line creates the database query to be executed to do the deleting. You don't need to change those to use the script.
  9. I finally figured this out. I was using phpMyAdmin to look at the database collation of all the tables by clicking the database name in the left sidebar of phpMyAdmin. I had changed the collation to utf8mb4_unicode_ci for all the tables, but I was still getting the error above. Although the main structure view in phpMyAdmin showed all the tables were using utf8mb4_unicode_ci, when I looked at the structure of the tblsslstatus table, it still showed that utf8mb4_general_ci was being used by all the varchar fields. Once I changed each of those fields to utf8mb4_unicode_ci, the error message was gone and the SSL Sync worked when I re-ran the cron command.
  10. I'm not sure this applies to SpamExperts specifically, but there is a Hotfix concerning domain validation for MarketConnect orders that sounds like it may be, and might be worth a try while you wait for other replies.
  11. I just updated to v. 8.0, and while I was troubleshooting another issue with cron after updating to PHP 7.4.11, I discovered I was getting this error in the SSL Sync section of the cron task. Here is the complete error: SSL Sync [ERROR] PDOException: SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '=' in /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Connection.php:331 Stack trace: #0 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Connection.php(331): PDO->prepare('select `userid`...') #1 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Connection.php(664): Illuminate\Database\Connection->Illuminate\Database\{closure}('select `userid`...', Array) #2 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Connection.php(631): Illuminate\Database\Connection->runQueryCallback('select `userid`...', Array, Object(Closure)) #3 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Connection.php(339): Illuminate\Database\Connection->run('select `userid`...', Array, Object(Closure)) #4 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Query/Builder.php(2202): Illuminate\Database\Connection->select('select `userid`...', Array, true) #5 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Query/Builder.php(2377): Illuminate\Database\Query\Builder->runSelect() #6 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Query/Builder.php(2685): Illuminate\Database\Query\Builder->Illuminate\Database\Query\{closure}( ) #7 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Query/Builder.php(2379): Illuminate\Database\Query\Builder->onceWithColumns(Array, Object(Closure)) #8 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Cron/Task/SslStatusSync.php(0): Illuminate\Database\Query\Builder->pluck('userid', 'domain') #9 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Cron/Task/SslStatusSync.php(0): WHMCS\Cron\Task\SslStatusSync->getNewDomains() #10 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Scheduling/Task/AbstractTask.php(0): WHMCS\Cron\Task\SslStatusSync->__invoke() #11 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Scheduling/Task/AbstractTask.php(0): WHMCS\Scheduling\Task\AbstractTask->execute() #12 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Cron/Console/Command/AbstractCronCommand.php(0): WHMCS\Scheduling\Task\AbstractTask->run() #13 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Cron/Console/Command/AbstractCronCommand.php(0): WHMCS\Cron\Console\Command\AbstractCronCommand->executeCollection(Objec t(WHMCS\Scheduling\Task\Collection)) #14 /chroot/home/username/thedomain.com/html/vendor/symfony/conso le/Command/Command.php(255): WHMCS\Cron\Console\Command\AbstractCronCommand->execute(Object(WHMCS\Cr on\Console\Input\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #15 /chroot/home/username/thedomain.com/html/vendor/symfony/conso le/Application.php(912): Symfony\Component\Console\Command\Command->run(Object(WHMCS\Cron\Consol e\Input\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #16 /chroot/home/username/thedomain.com/html/vendor/symfony/conso le/Application.php(264): Symfony\Component\Console\Application->doRunCommand(Object(WHMCS\Cron\C onsole\Command\AllCommand), Object(WHMCS\Cron\Console\Input\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #17 /chroot/home/username/thedomain.com/html/vendor/symfony/conso le/Application.php(140): Symfony\Component\Console\Application->doRun(Object(WHMCS\Cron\Console</> Input\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #18 /chroot/home/username/thedomain.com/whmcs/crons/cron.php(0): Symfony\Component\Console\Application->run(Object(WHMCS\Cron\Console\In put\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #19 {main} Next Illuminate\Database\QueryException: SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '=' (SQL: select `userid`, `domain` from `tblhosting` left join `tblsslstatus` on `tblhosting`.`domain` = `tblsslstatus`.`domain_name` where `domain` != and `tblsslstatus`.`id` is null limit 100) in /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Connection.php:671 Stack trace: #0 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Connection.php(631): Illuminate\Database\Connection->runQueryCallback('select `userid`...', Array, Object(Closure)) #1 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Connection.php(339): Illuminate\Database\Connection->run('select `userid`...', Array, Object(Closure)) #2 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Query/Builder.php(2202): Illuminate\Database\Connection->select('select `userid`...', Array, true) #3 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Query/Builder.php(2377): Illuminate\Database\Query\Builder->runSelect() #4 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Query/Builder.php(2685): Illuminate\Database\Query\Builder->Illuminate\Database\Query\{closure}( ) #5 /chroot/home/username/thedomain.com/html/vendor/illuminate/da tabase/Query/Builder.php(2379): Illuminate\Database\Query\Builder->onceWithColumns(Array, Object(Closure)) #6 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Cron/Task/SslStatusSync.php(0): Illuminate\Database\Query\Builder->pluck('userid', 'domain') #7 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Cron/Task/SslStatusSync.php(0): WHMCS\Cron\Task\SslStatusSync->getNewDomains() #8 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Scheduling/Task/AbstractTask.php(0): WHMCS\Cron\Task\SslStatusSync->__invoke() #9 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Scheduling/Task/AbstractTask.php(0): WHMCS\Scheduling\Task\AbstractTask->execute() #10 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Cron/Console/Command/AbstractCronCommand.php(0): WHMCS\Scheduling\Task\AbstractTask->run() #11 /chroot/home/username/thedomain.com/html/vendor/whmcs/whmcs-f oundation/lib/Cron/Console/Command/AbstractCronCommand.php(0): WHMCS\Cron\Console\Command\AbstractCronCommand->executeCollection(Objec t(WHMCS\Scheduling\Task\Collection)) #12 /chroot/home/username/thedomain.com/html/vendor/symfony/conso le/Command/Command.php(255): WHMCS\Cron\Console\Command\AbstractCronCommand->execute(Object(WHMCS\Cr on\Console\Input\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #13 /chroot/home/username/thedomain.com/html/vendor/symfony/conso le/Application.php(912): Symfony\Component\Console\Command\Command->run(Object(WHMCS\Cron\Consol e\Input\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #14 /chroot/home/username/thedomain.com/html/vendor/symfony/conso le/Application.php(264): Symfony\Component\Console\Application->doRunCommand(Object(WHMCS\Cron\C onsole\Command\AllCommand), Object(WHMCS\Cron\Console\Input\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #15 /chroot/home/username/thedomain.com/html/vendor/symfony/conso le/Application.php(140): Symfony\Component\Console\Application->doRun(Object(WHMCS\Cron\Console</> Input\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #16 /chroot/home/username/thedomain.com/whmcs/crons/cron.php(0): Symfony\Component\Console\Application->run(Object(WHMCS\Cron\Console\In put\CliInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #17 {main} I checked the tables tblsslstatus and tblhosting, and they did have different collations (utf8_general_ci), but I have since changed all the database collations to utf8mb4_unicode_ci, which the majority of the tables already were, and re-run cron, but I still get the same error. I'm running MariaDB 10.3.24. How do I fix this?
  12. I just updated to v. 8.0, and when I run the System Health check, I'm seeing the following warning: Yet, when I go System Settings -> General Settings -> Mail -> Configure Mail Provider, I have SMTP set up with port 587 and TLS selected tin the SMTP SSL Type dropdown. Am I missing a setting?
  13. Good thought. Same problem using a new, private window in Firefox. I tried it with a test account in Chromium, which I have never used to log in to WHMCS before, and got the same "Password incorrect. Please try again" message.
×
×
  • 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