Jump to content

polyglot2

Member
  • Content Count

    58
  • Joined

  • Last visited

Community Reputation

0 Neutral

About polyglot2

  • Rank
    Level 2 Member
  1. Oh, and the client area is also empty except for the "Logged in as Administrator" text at the upper right corner.
  2. We are testing upgrading to 7.0.2 (using PHP 5.6, CGI mode) from (yes, old, we know) 5.3.14. The upgrade went smoothly, except that we are no longer able to get to the admin area. The error message is "Critical Error: You are attempting to access the admin area via a directory that is not configured. Please either revert to the default admin directory name, or see our documentation for Customising the Admin Directory." We don't use custom admin path previously. So I tried adding '$customadminpath = "admin";' to configuration.php. Still the same error message. If I try using some non-existing directory, e.g. '$customadminpath = "foo";' then the error becomes "Critical Error: You are attempting to access the admin area via a directory that is different from the one configured. Please refer to the Customising the Admin Directory documentation for instructions on how to update it." Any idea how to resolve this? I'm wondering what other check condition WHMCS is using to determine that the admin area directory is "configured". Any hints appreciated.
  3. After clicking on: https://WHMCS/configuressl.php?cert=<GUID>&step=2 an error shows up: Catchable fatal error: Object of class stdClass could not be converted to string in /path/to/docroot/includes/functions.php on line 0 WHMCS 5.0.3, Debian Linux Squeeze, PHP 5.3.3.
  4. Still, what you're saying doesn't make sense. What's the point of doing a SELECT ... LIMIT <maxlog>, 99999 to fill some HTML table that's going to displaying a certain page (say 100 rows) only? To know the total number of rows? That's what SELECT COUNT(*) is for. Also, sorry for my ignorance, do you have access to WHMCS source code?
  5. Could you elaborate on this: "The purpose of the query is to populate the tables for the admin activity log." How does a SELECT query populate the (database) table? And why do you need to populate it?
  6. I see, but wouldn't "SELECT COUNT(*) FROM tblactivitylog" be much faster (on a MyISAM table anyway)? And what's the second 99999 supposed to do? And perhaps the checking can be done less often (with the consequence of the limit being overrun for a few records, which is not that big of a deal).
  7. I'm always seeing those queries whenever running "mysqladmin processlist". This query each takes around 8-12s on our server, and these seem to be slowing things down. What is the purpose of these queries? The LIMIT values seem weird.
  8. Well, WHMCS can display "Sorry, can't check domain availability right now, please [click here] if you want to check manually. Or try again later". I think it's much better than just displaying "Domain already registered" (which is just a slightly less stupid assumption).
  9. Tested on versions 3.8.2 and 4.1.2 Currently entries in includes/whoisservers.php are like these: .com|whois.crsnic.net|No match for .org|whois.publicinterestregistry.net|NOT FOUND .org.uk|whois.nic.uk|No match .edu|whois.internic.net|No match for .tourism.pl|whois.dns.pl|does not exists ... which indicates that WHMCS only search for a negative indicator. But it does not look for a positive indicator. This means that if the response is an error page, or blank, or there is some other network error, etc, WHMCS can't tell the difference. Maybe the entries can be made like: .com|whois.crsnic.net|No match for|Already registered .org|whois.publicinterestregistry.net|NOT FOUND|ALREADY REGISTERED or whatever. And WHMCS should check both the existence of negative and positive (and reports error when there are both found, or there are none found). Here at our servers, we experience network problem from time to time. When that happens, during the period WHMCS will report domain as not being available every time, even though it is. This disrupts the ordering process.
  10. Sorry for the long time between replies. I forgot about this thread. Thanks, it doesn't seem to be the case here. I've checked all the admins and they have valid email addresses (no typos, no spaces, etc). And I think WHMCS should print the error detail anyway.
  11. We have lots of entries like below in the Activity Log. Admin Email Notification Sending Failed - (Subject: WHMCS User Details Change) Admin Email Notification Sending Failed - (Subject: WHMCS New Order Notification) Admin Email Notification Sending Failed - (Subject: WHMCS Automatic Unsuspension Notification) Admin Email Notification Sending Failed - (Subject: New Cancellation Request) Admin Email Notification Sending Failed - (Subject: New Cancellation Request) Admin Email Notification Sending Failed - (Subject: WHMCS Automatic Domain Renewal Success Notification) Admin Email Notification Sending Failed - (Subject: WHMCS New Order Notification) I wonder if there are details as to why they failed.
  12. No, what I meant was, I accidentally added the same payment twice. There is only one actual payment from the client and therefore there should not be any credit. Since I added the payment again, there is now an overpayment credit showing up for the client. The problem is that after I undo my mistake by deleting the extraneous payment (via clicking the red [x] button in the Edit Invoice page), WHMCS doesn't delete the overpayment credit. It should, shouldn't it? Of course I can also delete the client's credit manually, but that's not the question here.
  13. WHMCS 3.8.1. There's $100 invoice. If I add a payment with transID 'abc123' for $100, and then accidentally add the same payment twice $100, a credit will appear for the client for $100 due to "overpayment". If I then correct the payment by deleting one of the payments, shouldn't WHMCS "debit" the client's credit? Or delete the overpayment credit (if it can track from which payment it came from)?
  14. Is anyone interested in a WHMCS-Moodle integration, e.g. for selling courses/online trainings? Moodle is module-based and can play rather well with external systems and already has PayPal/Authorize.Net payment gateway support, so is WHMCS. They two seem to be a nice fit.
  15. When a ticket is deleted, its attachment file is not deleted.
×
×
  • 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