javacodemonkey

Solved: I found that I had other websites that were producing similar issues and I saw this as one of the paths that were being checked "/opt/cpanel/ea-php74/root/usr/lib64/php/modules/php_intl.dll.so" So I figured that if I created a file in that directory and used the intl.so file instead I could potentially fix the issue. I used the cp intl.so php_intl.dll.so command and confirmed that it didn't break my system. Then I navigated to the WHMCS site that we run and attempted to produce the error (generally happens when navigating back and forth between logging in as a client). Instead, I received a whoops error message that stated the system had already loaded an intl file. I removed the new php_intl.dll.so file that I created in my system path and now it works on php 74. Thanks everyone for your help

Found that I can revert the site back to php 7.3 which allows the issue to be resolved for live. However, neither the 7.3 or 7.4 have the php_intl.dll file in the directory supported by this error message.

We've recently been getting an error message on our WHMCS where when logging in, when attempting payment collections manually, and when navigating the site generally. Because errors were hidden, we would just get the "Oops! Something went wrong and we couldn't process your request" page. This wasn't a huge issue because we could just refresh the page and it would display correctly afterwards. However, now we are getting complaints from users that state the payments they submitted wouldn't go through and we can confirm this by checking that Stripe received the Oops page as well. I pulled a copy of the site over to a dev domain and was able to see what the error was (attached). The system is stating that it couldn't find our php_intl.dll but I confirmed that it is installed in our version of php (7.4). Is this a known reported issue and is there a way to correct this? Our WHMCS is fully up-to-date on 8.3.1.

For clarity, I have been keeping my site updated with all new stable releases. Running php 7.4. Accessed through Clients > View/Search Clients > [CLIENT] > Log In As Owner Button Already attempted proposed fix by going to Utilities > System > System Cleanup > Empty Template Cache

After updating with the most recent stable release (8.30.0), I went through my standard testing process to see if anything is no longer working. I found that the Login As Owner function no longer works and, instead, updates the url to be (URL + #). Is this something that has already been looked into for correction? Are there any hot fixes that are suggested?

I ended up doing something similar by checking the URL and sending to the login page with an if/else statement. I'll share it here so that others may use it as needed. <?php if (!defined("WHMCS")) die("This file cannot be accessed directly"); function hook_ForceEveryoneToLogin($vars) { $clientID = intval($_SESSION['uid']); $adminID = intval($_SESSION['adminid']); // Create the link for the incoming URL. $link = "https"; $link .= "://"; $link .= $_SERVER['HTTP_HOST']; $link .= $_SERVER['REQUEST_URI']; if ($adminID===0){ if (!in_array($vars['filename'], array("index")) && $clientID===0){ // Check if the link is accurate. if($link != "https://billing.dang-designs.com/index.php?rp=/login"){ header("Location: login.php"); exit; } } else if($clientID===0){ // Check if the link is accurate. if($link != "https://billing.dang-designs.com/index.php?rp=/login"){ header("Location: login.php"); exit; } } } } add_hook("ClientAreaPage", 1, "hook_ForceEveryoneToLogin");

@Brain!, You were right. The inclusion of that filename allowed the page to stop redirecting but now it won't redirect to the login page. It will go there naturally when selected, but not when the I select other pages (like store, announcements, etc.). I'm a developer but these hooks confuse me beyond belief.

After making the update to WHMCS 8.04, I found that this hook causes excessive redirects and must be disabled. Is there a modification that needs to be made to it for it to function properly? Here is the code specified in the aforementioned posts if (!defined("WHMCS")) die("This file cannot be accessed directly"); function hook_ForceEveryoneToLogin($vars) { $clientID = intval($_SESSION['uid']); $adminID = intval($_SESSION['adminid']); if ($adminID===0){ if (!in_array($vars['filename'], array("login","dologin","clientarea","pwreset", "register")) && $clientID===0){ header("Location: login.php"); exit; } } } add_hook("ClientAreaPage", 1, "hook_ForceEveryoneToLogin");

After running the updates on the site and copying the files over to another domain, I'm seeing that the init.php file is causing a redirect constantly. The whole file is encrypted, so it's impossible to determine how to correct it (along with every other file (thanks WHMCS for doing this by convention)). Found this was the file forcing the redirects by replacing the index.php, clientarea.php, and login.php files that continuously redirect. Still hunting for the solution that allows this to work.

For those that have a similar message they encounter, it appears the WHMCS site causes this issue if updates are not made consistently. In fact, any page where a submit button is pressed causes the page to error out with the same message. Updating the site to the newest version causes my whole site to crash and I'm working to find a solution. At least I'm somewhere further than before.

I have recently been tasked with setting up the G Suite add on for our WHMCS set up and I have been following the instructions as thoroughly as possible (link provided below). I have already set up the OAuth project and I have gotten to the point where I am setting up the product under the group under Setup > products/services > products/services. When I attempt to use my OAuth client secret and ID to Grant access to Google Account, I am redirected to a Forbidden page (also listed below) in the module settings screen. I have checked my path (which is configured correctly), file permissions (all set to 777), and my Google Project (which has the logs showing that the authorization was granted). I've been working on this non-stop since yesterday and would greatly appreciate any advice or direction out there. Forbidden You don't have permission to access this resource. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. https://www.docs.modulesgarden.com/G_Suite_For_WHMCS