evolvewh

Forgot about that so it's the overall feature that I want to +1

I wanted to show my +1 for this task: https://dev.blesta.com/browse/CORE-11 I would like to see more than 7 days shown if possible.

+1 to the Logicboxes I'm not sure if you're aware but the domain system is supposed to be revamped in 4.1 whenever that happens and I would imagine it would change a lot of your coding between the 2 versions of Blesta.

+1

Cool. Then this is my +1 for it!

I'd like to start a thread about not being able to re open tickets (as an option chosen on the admin side). There are too many times where a client replies to an older email with a different subject and often to the wrong department. They should realistically start a new email / ticket, but they don't. I do realize there is a 'split' feature but it's about efficiency and not having to do that all of the time. I think there could be a setting on the admin side (perhaps by department for flexibility) to allow or not allow a client to reply and re open a ticket. This could possibly be done with a time frame as suggested in other threads (allow them to re open the ticket within x amount of hours that it was closed). If the setting is active, it would send an email to the person saying they must open a new ticket to the proper department. Our company has different hours for different departments and if they send a ticket about hosting support to a department that is closed (We only answer website development questions until 6pm), they expect a reply. We don't check after hours department emails until the next day. I try to set the boundaries because I don't want to be living on the computer all night long! I know it gets specific but I think it also makes Blesta more flexible to allow the different users to customize the behavior to meet their business needs.

Cody, I know it's hard to satisfy everyone! I will make a feature request and I think having options makes the software more versatile and can be done without making the overall system cluttered. Thanks!

Are we able to over ride this and not allow client to re open a closed ticket? It's very annoying when someone replies to an older email and tickets have to be sorted and split. I would rather have a response sent to them saying that they need to open a new ticket. P.S. I am using v3.6.1 but I responded here since this is the version the feature was introduced in.

I think there is enough evidence on this forum to show that the 'standard' cron command doesn't work well with cPanel. You may want to reference my post here: http://www.blesta.com/forums/index.php?/topic/5300-auto-debit-cron-stopped-since-dst/page-2#entry40034

I think the fuss is more about dealing with transfers and renewals and then with the different pricing levels which I believe will be taken care of in 4.1. Selling a brand new domain is not a pain right now.

There are a few things that I see missing and I hope are incorporated. One thing is a place to enter the EPP code if an admin creates the order for the customer and sends them an invoice. There are times when a client has the EPP code and asks the company to create the order for them. I know some here would say that's what the front end ordering system is for but I know that I'm not going to turn away business over something simple like this. If the customer wants the extra customer service, I'll give it to them. Also, I don't know if this is logicboxes specific or not but the additional features such as domain privacy and DNS management should be controllable through the API. Right now, I have to login to the reseller site and manually process a domain privacy or DNS Management option. It's ok to do a few that way but when you're dealing with 20+ renewals / registrations at a time, it would be a lot easier to have this automated. The different pricing levels have been talked about so I don't need to re iterate that but it's important.

How do we get this added as soon as 4.0? I think this is a 'common usability' feature that should be added. It's not a lot of fun spending time going through the database and moving/merging duplicate accounts. I would be willing to sponsor this too.

I've now got this working for 2 days in a row and I'm pretty certain this is the fix. For anyone using cPanel and having issues, you may want to try this format for your cron command: */5 * * * * /usr/local/bin/php /home/your_cpanel_username/public_html/index.php cron/?cron_key=your_cron_key If you update the cron key from the admin area of Blesta, you'll need to update this command too. Hope this helps others out as well. If it works for others, maybe this link could be updated: https://docs.blesta.com/display/user/System+%3E+Automation Also, I don't want to add clutter but it may be helpful to have a link within Blesta's admin to point users to this documentation.

There isn't a row for Auto Debit. The rest are there.

Tyson, Thanks for the tips. I disabled PHPIDS and then updated the cron key. It did update to a hash within the database after. I had to wait until today to see if auto debit ran and unfortunately it didn't. I'm at a loss and I would really like to get this resolved. Should I wait for 4.0 or open a support ticket now? I've also got 2 other tickets open that I'm waiting to hear back about. Thanks, DL

I feel your pain and while I don't have the answer to get back to the stock configuration, I did see that cyandark is working on a way to merge Tasty cPanel to his version of cpanel Extended. This may be an option for you?? http://www.blesta.com/forums/index.php?/topic/5552-module-cpanel-extended-v41/?p=39797 Otherwise, I'm not sure what you can do. I've done the same and I'm not installing any more 3rd party plugins or modules either. I wish Blesta could grow a bit faster and get more of these great features integrated into the core. Hopefully some day soon.

I have left the database_version as 3.6.0-b1 and I put exchange_rates_auto_update back to 'false'. I did have PHPIDS running so I've disabled it, updated my cron key (from the admin area) and I'll see what happens tomorrow when auto debit should run again. I'll report back then. Thanks.

I think I have finally figured this out. I looked in the settings table and it was never updating the cron_key when I changed that through the admin UI. I manually edited it through phpMyAdmin and auto debit worked perfectly this morning. On a side note, database_version (3.6.0-b1 but I don't run betas on my live site) has not updated like it should and exchange_rates_auto_update was the same way. I can guarantee that I ran the auto update script successfully.

Thanks for the help. {module.host_name} is not working for me and I do have information entered within the module setting (an IP address). By having an IP entered in Hostname, I thought I could use Server IP: {module.host_name} in my welcome email

Do you know what the email template tags are for the following when using this module? Control Panel URL (before propagation) Server IP Temporary FTP Hostname My welcome emails are blank for those values right now.... Thanks.

Very nice! Thank you!

Just when I thought it was working properly, it didn't run yesterday.

I ended up deleting the cron job from cPanel, updated the cron key and then re entered the cron job into cPanel. This appears to have fixed the issue. Thanks.

Right now, I have additional contacts setup (used the add contact link within their account) so that they can open tickets. What I'm seeing is that when I reply, it not only goes to the person that opened the ticket but the main email address listed on the account. There's probably no way to 'shut this off' but it is annoying for the client who is receiving it in multiple places when the conversation doesn't even pertain to them. Is this correct or is there a way I can change this behavior?