Jump to content

bear

Member
  • Content Count

    4118
  • Joined

  • Last visited

  • Days Won

    49

bear last won the day on May 27

bear had the most liked content!

Community Reputation

195 Excellent

About bear

  • Rank
    Senior Member

Recent Profile Visitors

9443 profile views
  1. Brian! doesn't visit much, and isn't getting notifications of threads or mentions as far as I know. You may get lucky and he visits sometime soon, but I wouldn't count on it.
  2. Pretty much no. Waste of time, usually, and quite a few threads about it have been posted here (though negative threads sometimes vanish).
  3. My feeling was the changes they made to the user/client/owner system (which is awful, by the way) caused issues with password changes and they simply didn't want to spend the effort to make it work. Badly thought out and implemented (IMHO) and cascaded into this issue, which will forever remain something that's ignored by them. Now if they found a way to make a few pennies on a password change....well...
  4. Right click one and see where it's trying to load from. Make sure the images are in that location?
  5. If you wrote it that way, that's likely why. It should be <br />
  6. Most of the security updates don't translate back more than a few versions, so small comfort in that. 😉
  7. Good to hear, but what fixed it?
  8. If it stopped immediately after the move, make sure cron daemon itself is running, and your user has the rights to access it. If cron is ok, then check your settings. If they're correct (for this server), then have it do the 5 minute run that's recommended. If it fails to run, check the cron logs as well as the error logs to see if its permissions on files and so on.... Basic troubleshooting there.
  9. That's exactly the same issue (the later posts) you explained here. How does that have anyone "get" the issue?
  10. Since the cron is set up on the server and not within WHMCS, you need to ask your provider (or troubleshoot it yourself) to look into it and make sure it's running and calling the right PHP version (if you're not using the server default). I'd assume there's also something in the WHMCS logs if it was an issue with the WHMCS cron script?
  11. The risk he's taking is something we all get to share. Good times. 😉 Quick question, and hopefully it can be answered; can it be exploited without being enabled, or only if it's active?
  12. Being a notification (based on the footer), it's from your WHMCS installation, and assuming you send via SMTP in WHMCS, that makes sense. From what I know about this particular spammer, you will likely find he sent in a form (contact? support?), and this was WHMCS letting you know it arrived. Looking forward to what they say about it.
×
×
  • 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