Jump to content

vdswin.com

Retired Forum Member
  • Posts

    49
  • Joined

  • Last visited

Everything posted by vdswin.com

  1. Please add Easy translate support for custom fields
  2. Thank you. This is EXACTLY is I was looking for.
  3. Yes, with "six" or "twenty-one" theme all existing records are passed to $invoices and DataTables has all of them. But with custom theme it is like default &itemlimit=10 is set and so only 10 records is passed to $invoices. So there is only 10 records in page source. And DataTable can display only 10 invoices (like there is ONLY 10 invoices exists) regardless of settings, changing Limit in datatble, or setting "pageLength": -1. "Showing 1 to 10 of 10 entries" until I add &itemlimit=10 and then get "Showing 1 to 10 of 54 entries" like in "six" or "twenty-one" theme. 1) Is it possible to change some internal WMCS setting, that is managed by adding URL parameter &itemlimit from 10 to "all" by default? 2) Why can WHCMS return different number of items with different theme? 3) Could you please try add any custom theme to WHMCS, place just {$invoices|count} into clientareainvoices.tpl, clear cookie and check how many records will WHMCS return by default? If it is only 10 - could this be changed to "-1" or "all" in some way?
  4. Not so easy.... In fact it does not matter what pageLenght is set (I set it to -1) because WHMCS gives only 10 records to DataTables. So if create clientareainvoices.tpl just as {$invoices|count} it shows "10" by default until I add &itemlimit=all to query string. So this issue has no relation to DataTable settings =( I can not figure out why theme "trweny-one" sets this itemlimit to all by default ((
  5. I faced with same trouble. Only 10 items is displayed by default for any table (tickets, invoices, email etc.). Smarty value {$invoices} contains only 10 items. If I add &itemlimit=all to URI - it start displaying all items until logoff / cookie clear. How and what should I change, so all items was displayed by default? If I enable default twenty-one theme there is no such issue, all records displayed by default.
  6. Same problem here. Still waiting for working patch about a month ((
  7. Seems that you have wrong configuration for your Crontab. It runs every 3 minutes but should be run only one a day. Please send me your Crontab settings for check.
  8. I think they also updates files in distributive, so you can try just download a last archive with v5.1.2 and replace files.
  9. I have opened a ticket about this issue and Andrew send me attached patch that resolve it. adminfunctions.zip
  10. We use our own modules for KVM VPS and have not any issues with suspend / unsuspend automation in v5.1.2.
  11. This patch is only for message_preview. It does not fix "No Recipients" issue.
  12. As I can seen, Cron set accounts without active services to "inactive", seems that is correct. BUT, when such user place a new order and paid it, his account remain inactive regardless he have active order! And only on next Daily Cron runs this account will be set to "Active". So I do not think this is a bug, but this should be enhanced, that account set to "active" just after accepted order.
  13. This bug is easy reproduced in 5.1.2. Is there any patch for it?
  14. I noticed that status "inactive" was set only for clients who has not active services. All who has active services remain "active"... Did you mean that yours clients with active services was marked as "inactive"?
  15. Could you please describe more detailed how to reproduce this "bug"?
  16. I think you have Debian OS that have different php.ini for php5-mod and for php5-cli. So PHP scripts that you run via Apache is working, but you did not edit php5-cli php.ini afer IonCube installation, and that your php scripts that run from CLI is not working. Just add ioncube loader string to php.ini in /etc/php5/cli/php.ini as you did for /etc/php5/apache2/php.ini
  17. I have no any troubles with promotions coupons in 5.1.2. May be you just not notice pagination at the bottom of list ;-) ?
  18. В текущей версии (5.1.2) есть с десяток багов, их постепенно фиксят, но скорее всего скоро будет выпущен 5.1.3 - лучше подождать его.
  19. My support ticket was processed and resolved with attached patch. There is instruction from Matt: [ATTACH]3118[/ATTACH] After replacing those two files all is OK now. Thank you for great support!
  20. Also this error occurs when Daily Cron runs while autoclosing tickets: PHP Fatal error: Call to undefined function ticketsummary() in /www/clients/admin/../includes/ticketfunctions.php on line 0 Fatal error: Call to undefined function ticketsummary() in /www/clients/admin/../includes/ticketfunctions.php on line 0
  21. I can reproduce and confirm error Fatal error: Call to undefined function ticketsummary() in /www/clients/includes/ticketfunctions.php on line 0 while adding a reply to ticket. Reply is added successfully but instead of redirect to ticket get this error.
  22. I can reproduce and confirm all of this bugs.
  23. Simple module. Does not have suspend and unsuspend functions. There is a free php-class sample from Hetzner, can be used to write own module easy with really full functionality.
  24. If you change AUTO_INCREMENT to 500 the next ID will be 501, than 502 etc.
×
×
  • 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