sanfranciscohost

I have experienced this as well. From version 4.1.2 To version 4.2.1 Matt? Help!

Hi Keith, Doing that now. Thank you! Deirdre

We are interested in this as well. Can we help you test this new feature? Thanks! This is a much needed add-on to our billing system. Deirdre Smith San Francisco Host

The behaviour I mentioned in the reply above has already been discovered in v4 and reported to Matt here: http://forum.whmcs.com/showthread.php?t=20231 Just FYI. Deborah

I am finding that the "Next Due Date" field for the domains listed on the clientsdomainlist.php page are not reporting the same value from 'nextduedate' in the database. The "Next Due Date" field is reporting the correct value in the clients profile "domains" tab. Can someone else confirm? I am not sure if I need to refresh cache / templates to see the new values so let me know if that is the case. Thanks! Deborah

TY Gustave! Now I see the expected due date in the database but it is not showing up correctly on the clientsdomainlist.php page. It is showing up correctly on the client's profile however so I will let Matt know to take a look. Deborah

Hi Matt, Love the new look! We are playing with it now. Wondering if when we roll our mouse over the "setup" tab is it supposed to cover the top banner like that? Maybe its just me and I am using Firefox on Fedora 10. It also shows the same behavior in Firefox on a Mac, and Safari on a Mac kind of sticking on pages not advancing to the linked page. Haven't checked it yet in IE. Dunno. Also, where can we see passwords for the billing login of a client? All we see is "enter to change". Maybe I am missing something? Love the direction though, very nice. Well done! Deborah

Hi n2972s, everyone, Thanks for contributing! This community is part of the reason we migrated here from MB as well. So many great ideas .... We using this script to update the domain due dates to coincide with the billing dates and we are not sure what we are doing wrong but its not working on our installation as expected. It will calculate the correct due date and set it to be the 1st day of the month in the screen output but when we look at the database it is still setting the due date to the number of days we have in the script and ignores the billing date of the month option. Here are the options we have set at the top of the script: // Path to WHMC Confiruation File include("/path/to/my/configuration.php"); // Mode (1 = Test Mode / 2 = Live) $mode = 2; // Output Format (1 = Screen / 2 = Email) $output = 1; // Reset Date $resetdate = "-30 days"; // Day of the Month Billing ( 0 = False / 1 = True ) $dayofmonthbilling = 1; // If Day of the Month Billing is True then What Day ( Number ) $dayofmonth = 1; // Email Addresses - Used if an email is sent. $to = "email@email.com"; $from = "email@email.com"; The script runs without errors and the screen report says this: somedomain.com 2011-01-27 2010-12-01 Success! somedomain.com 2010-03-14 2010-02-01 Success! somedomain.com 2011-08-12 2011-07-01 Success! somedomain.com 2010-05-30 2010-04-01 Success! somedomain.com 2009-08-19 2009-07-01 Success! So you can see that it tells us that the script has done its job and reset the due dates to be the first of the month. Yay! When we query the database for those same domains, we see these dates instead: somedomain.com 2011-01-27 2010-12-28 somedomain.com 2010-03-14 2010-02-12 somedomain.com 2011-08-12 2011-07-13 somedomain.com 2010-05-30 2010-04-30 somedomain.com 2009-08-19 2009-07-20 Boo! Why is it not updating the due date to the 1st day of the month in the database when it is calculating it correctly on the screen output? How can we fix this? We just recently moved to v4 but the behaviour of the script was the same before the upgrade. We were hoping there was something in the upgrade that would fix this but we have no joy. Thanks for your help, as this is driving us crazy! Deborah

UPDATE: We replaced the 4.0 module with the one from our last installed WHMCS and tried to create an account again. This time it seemed to have created the account without a problem. I will report back in this thread if there are any further issues. Deborah

We are seeing this here too when trying to create an account on our Plesk 8.2. Module Create Failed - Service ID: 544 - Error: 1005 - Protocol version '1.6.0.0' not supported. Current protocol version is '1.5.0.0' What do we do? Matt? Thanks! Deborah

I don't know if anyone will find this helpful but instead of deleting things in the templates I use either a comment tag to make those lines I don't want to show up just disappear or I use a css style declaration to make the display: none. For example, in the template we are looking at for this thread: (clientareadomaindetails.tpl) To get rid of the Nameservers line, place a comment tag around it like this: <!--<p><strong> » {$LANG.domainnameservers}</strong></p>--> To get rid of the forms, place a CSS style definition to make it not show up like this: <form style="display:none;" method="post" action="{$smarty.server.PHP_SELF}?action=domaindetails"> You can use this in images or tables as well: <img style="display:none;" src .....> <table style="display:none;" .....> Its always nice to be able to preserve code that you might need to reenable further on down the line. If anyone thinks there is a problem or a downside with doing things in the way I suggested let me know. Deborah

Hello all, Just getting here from MB and wondering how we can set up everything to work like we need it to work and had a few questions. First, what is a "product group" and how/what do you use it? Is it by server? By package type? How do you use it for your business and why? We have a few shared servers and adding another one soon. We have more than a few VPS / Deds and some Windows servers with Cisco Pix on there. How do we seperate all of them? Is this what groups are used for? Can we copy one plan from one group (server) to another and how do we keep them straight? TIA Deborah