Jump to content

CavalloComm

Member
  • Posts

    209
  • Joined

  • Last visited

  • Days Won

    1

CavalloComm last won the day on September 15 2023

CavalloComm had the most liked content!

About CavalloComm

CavalloComm's Achievements

Senior Member

Senior Member (3/3)

1

Reputation

  1. Was there a resolution to this? Our system is stating a connection error with the license server even though it tests fine and one of our partners is having the same issue and opened a ticket and got a reply that WHmcs is aware of a license server issue?
  2. We have some escalation rules to actually close out tickets (not using the other type of auto-closed) - because it depends on the queue they are in. We are on 7.1.2, and I do see when running the cron.php with a --force -vvv that it states it's running the rules, but they just stopped working a few months ago. Anyone else having issues? It seems to be ignoring all the rules.
  3. We are attempting for the first time to use the Autorelease module on a "service" product, in turn to open a ticket. Is there any way to actually make it state more information in the ticket as to what actually was ordered? As of now, the subject just says "Service Provisioned" and the content is "Service ID # XXX was just auto provisioned" Is there a way to have it contain more info than this? Like what the product was or something to that effect? Has anyone done this?
  4. I opened a bug report - wondering if we can get this fixed.
  5. Ok - so how do we stop it from posting to the activity log every 5 minutes? It makes it hard to look for "real" activity...
  6. Will this stop it from posting to the log since I have been running this separately?
  7. This is not a solution? We actually USE ticket escalations, so we run that CRON job every 5 minutes or so, and the log is FULL of this - so we can't really see what happened before? I don't want to skip them at all. Question also would be - do we still need a SEPARATE cron for ticket escalation anymore? (Such as this: crons/cron.php do_escalations) or does that run with the main cron every 5 minutes and does not log? Perhaps we are doing this by running it separately?
  8. I get the first one like above, then a second email stating that the job completed successfully. My email is offsite using SMTP, and I am using Linux Plesk
  9. We upgraded to 7.1.1 and PHP7, and all of a sudden iWHMCS seems to have a problem. You can login just fine, and get the main stats page, but the minute you tap on "Support", the app crashes. Also you can go to billing, and then when you tap on one of the links from there like invoices, it crashes. We've restarted our phones, and even reset the accounts, and it still does this. Can't find anything in the logs on the server related to this, although can see a 200OK when the app tries to hit the api.php file under includes. Not sure whether this is a 7.1.1 issue or PHP7 Issue at this point. Anyone else have this problem?
  10. Can this be worked out on the V4 template instead of "Blend"?
  11. We are using 7.0.1 It seems that modifications to the Support Ticket email templates no longer pull in anything from the subject line. It seems to be only placing "[Ticket ID: XXX] {$ticket_subject}" in the email subject line. We had ours modified to also show the status, and such. Is this a bug?
  12. We are using 7.0.1 Has anyone noticed that when a user fails login, and it's a "Client Contact" - it's linking to a different client all together. It seems it's reading from the 'id' field of the client contact table, but links over to the 'clients' table, therefore when you click on it, you get a different client altogether.
  13. Has anyone noticed that when a user fails login, and it's a "Client Contact" - it's linking to a different client all together. It seems it's reading from the 'id' field of the client contact table, but links over to the 'clients' table, therefore when you click on it, you get a different client altogether.
×
×
  • 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