Jump to content

Search the Community

Showing results for tags '7.8.3'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


WHMCS.Community

  • The latest WHMCS Release
    • V7.9 Beta Discussion
  • The Latest from the WHMCS Team
    • News & Announcements
    • The WHMCS Blog
  • WHMCS.Community
    • Community Announcements
    • Introduce Yourself
  • Using WHMCS
    • Pre-Sales Questions
    • Admin & Configuration Questions
    • Installation, Upgrade, and Import Support
    • Using WHMCS
    • Troubleshooting Issues
    • Vendor Discussions
  • WHMCS Beta Program
  • WHMCS Showcase
    • Showcase Your Site
    • Share Your Best Practices & Tips
  • Developing & Extending WHMCS
    • Third Party Add-ons
    • Service Offers & Requests
    • Developer Corner
    • Building Modules
    • Share Ideas for WHMCS Modules
  • Community Competitions
    • Competitions
  • General Discussions
    • General Discussion
  • General Feedback & Assistance
    • WHMCS.Community Tips & Tricks
  • Third Party Developers's Topics
  • Turkish International Discussions's Topics
  • Russian International Discussions's Topics
  • Spanish International Discussions's Topics
  • Portuguese International Discussions's Topics
  • French International Discussions's Topics
  • Italian International Discussions's Topics
  • German International Discussions's Topics
  • WHMCS Brasil's Topics
  • WHMCS Brasil's Tópicos
  • ModulesGarden Club's Topics
  • Hungarian International Discussions's Segítség
  • ThemeMetro Club's Topics
  • WHMCS Services Club's Topics
  • SwiftModders Club's Topics
  • WHMCS Global Services Club's Topics

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 7 results

  1. I've just recently updated to PHP 7.3 from 7.2 and I'm getting the following warning in System Health Status: Cron PHP Version Mismatch Your environment appears to be running a different PHP version (7.2.23) for the System Cron than the currently loaded PHP version (7.3.11). This may cause issues running your System Cron. This is the log for the System Health: WHMCS Health Check ================================================================================ error: * The system cron does not appear to have completed successfully within the last 24 hours. Check your activity logs or learn more about enabling the cron in our documentation. warning: * Your environment appears to be running a different PHP version (7.2.23) for the System Cron than the currently loaded PHP version (7.3.11). This may cause issues running your System Cron. notice: * Your PHP memory_limit value 1024M meets the recommended value of 128M. * - Your environment appears to meet the minimum requirements for Automatic Updates. To update, you will need to ensure you have at least 250MB of available disk space. * You are running MariaDB version 10.3.20. This version supports all features required for full compatibility with WHMCS. * A verified SSL certificate was detected for your site. * cURL reports that it does support Secure TLS 1.1 and 1.2 * cURL reports that it does support SSL * You currently have version 7.66.0 of cURL installed. This version uses a secure cipher list. * Your PHP environment uses a valid timezone. * PHP session support is enabled.Session autostart is disabled.The PHP session save path /var/cpanel/php/sessions/ea-php73/ is writable. * Your PHP installation has all required functions enabled for WHMCS to operate. * Your permissions are appropriately restrictive. * Your PHP installation has all recommended extensions loaded and enabled required by certain modules and addons of WHMCS. * Your PHP installation has all extensions loaded and enabled required for WHMCS to operate. * Your system is setup to not log unnecessary error levels. * Your system is not currently set to display errors. * Your PHP version 7.3.11 is supported by WHMCS. Your PHP version is actively supported by PHP for both bug fix and security releases. * Your WHMCS installation is using custom templates which will not be overwritten on upgrade. * You are using custom paths for all the recommended WHMCS directories. * Your SMTP settings are using encryption to ensure that sensitive data in email cannot be leaked in transit to your mail transport agent. debug: * Here are the paths for customisable directories in your WHMCS installation: - Attachments directory: /home/username/attachments - Downloads directory: /home/username/downloads - Compiled templates directory: /home/username/templates_c - Cron directory: /home/username/crons - Admin directory: /home/username/public_html/admin_folder All the cron seems to be running when i check the Activity log but I'm missing the daily WHMCS Cron Job Activity email:
  2. Hi, I have installed & configured the latest version of WHMCS on an installation with PHP 7.3. When attempting to order a product, my customers are presented with the attached screen. I've disabled domain registration so I'm not expecting to see a "register domain" field, however since it's a cPanel website hosting package then I believe there should be a "choose existing domain" field, which is failing to display. Looking forward to a resolution. Cheers, Josh
  3. Hello! after i install the latest version of WHMCS 7.8.3, when im trying to add a new server on the WHMCS control panel this happen: WHMCS\Exception\Validation\InvalidHostAddress in /home/sites/1/agahagha/public_html/vendor/whmcs/whmcs-foundation/lib/Filter/HostAddress.php:0 Stack trace: #0 /home/sites/1/akrjtg/public_html/admin/configservers.php(0): WHMCS\Filter\HostAddress->__construct('', '', '') #1 {main} i read somewhere and they say that may be problem the SSL???...
  4. Version 1.0.0

    215 downloads

    An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that prevents payments being processed via payment gateways using transaction references: MODULE-7154 - Sagepay Repeats MODULE-7146 - PayPal Pro Reference Payments MODULE -7140 - PayPal Payments Pro with Reference Transactions option enabled CORE-13810 - Prevent Client Area access to Add Payment Method page with only Reference Gateways We have also identified issues with the eWay Rapid module in this version: MODULE-7134 - Correctly report the status of declined payments in eWay Rapid MODULE-7132 - Correctly report the status of refunds in eWay Rapid MODULE-7131 - Error "Call to a member function getKey() on null" when adding a pay method via the admin area using eWay Rapid We have also identified an issue with Authorize.net CIM: MODULE-7143 - Ensure credit cards can be added/updated when Validation Mode is set to "Live" We have also identified three issues with Stripe: MODULE-7151 - Payment descriptor shows "Shopping Cart" when placing a new order via shopping cart MODULE-7141 - Correct interpolation of merge fields for Stripe Statement Descriptor MODULE-7155 - Invalid Positive Integer error when paying with existing card for an order total of 0.00 We have also identified an issue with 2Checkout: MODULE-7144 - 2Checkout deducts promotion code amount twice in Inline mode We have also identified an issue with Accept.js: MODULE-7148 - Retain pay profile when updating card expiration date The following generalised issues surrounding Pay Methods have been identified: CORE-13838 - Save local expiry date when updating tokenised card details CORE-13851 - Disable admin attempt capture button on Draft invoices CORE-13788 - Trigger CCUpdate hook in all expected scenarios This hotfix applies only to 7.8.3
  5. Version 1.0.0

    67 downloads

    An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that can prevent clients from accessing the client area in certain circumstances. An error message will be logged in the server PHP error logs or an Oops! error output on screen. The error details contain: Error: Call to undefined function WHMCS\Payment\PayMethod\run_hook() in /path/to/whmcs/vendor/whmcs/whmcs-foundation/lib/Payment/PayMethod/MigrationProcessor.php This occurs when when there is a client "Remember Me" cookie but no session and pay method data to be migrated. This hotfix applies only to 7.8.3
  6. Version 1.0.0

    41 downloads

    An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that can result in non-card tokens (such as GoCardless Mandates) being migrated to a remote credit card Pay Method type instead of the expected bank account type. This occurs when running v7.7 there is both credit card information and a Mandate token stored for a client, and GoCardless is the only active payment gateway module. Upon applying the 7.8 update and performing the Pay Method migration for an impacted client, a remote credit card Pay Method may be created. This hotfix applies only to 7.8.3
  7. Version 1.0.0

    73 downloads

    An issue has been identified in the 7.8.3 release - published on 23rd September 2019, that when opening a ticket as a support contact via email causes the first CC'd email address to be combined with the submitter's email. This could result in ticket notifications not being sent to all the expected recipients. This hotfix applies only to 7.8.3
×

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated