evolvewh

This doesn't look to preserve the original subject line when the customer sends the email / support ticket.

I think you're talking about putting this is in the body of the email right? I'm looking to change the subject line only.

Right now, the subject line to clients for all support tickets is Update to Ticket {ticket_hash_code} How can I change this to show something like: Update to Ticket {ticket_hash_code} Original Subject Name ? (I'm mainly after having the original subject shown) Customers do not even realize these are tickets and they do not take the time to login to the portal so they don't even know what ticket # whatever is and they are stating that it's confusing. I'm looking to enhance the customer experience any way I can.

Do you have multiple contacts under one client that is setup to receive responses? I don't like this feature either because I only want to respond to the person at a given company that sent the email. I forgot what the response was but Blesta had different reasoning for this.

I have the LogicBoxes Reloaded module and it gives the customer the ability to update namservers, lock/unlock and get the EPP code. http://www.blesta.com/forums/index.php?/topic/2678-logicboxes-reloaded-extra-feature/?hl=logicboxes I did have to add domain privacy and DNS management as configurable options. I have to manually apply the privacy protection if they sign up for it. I can't remember but I think my configurable option for DNS is what allows the customers to manage nameservers. I could be wrong on that though.

I hope there is more to it than 'just pricing tables'. On the admin side, when a domain is pending transfer from another registrar, Blesta is trying to provision the service every 5 minutes (or whatever the persons cron time interval is) and I hope this can be dealt with. There's also no place to enter an EPP code if an admin creates the order on the admin side for the customer. I think the 'Basic Options' section of 'add a new service' needs to have the options 'Transfer or Register' and if Transfer is selected, a field for an EPP code (optional) should appear. As far as the pricing tables, I think a simple setup of 3 tabs in the pricing section of packages -->> browse that say 'Register', 'Transfer' and 'Renew' would work just fine. I don't know if these 3 tabs would be triggered from the 'Account' and 'Type' under Module options. That way it only shows if the type is 'Domain Registration'. The other features that would be nice to have are 'Privacy Protection' and 'DNS Management' built right in. This may be a Logicboxes specific request though. Right now, if someone orders Privacy Protection, we have to login separately and activate this features vs. the system automating it. I forgot to add one thing. Domains should be separated in the admin and client area. Not grouped together with the other services. We (and I'm sure many other companies as well) have clients with 20+ domains and it's not so easy for them to sort out and manage them. Yes, the domain system is useable right now but it requires a bit of manual work from the employee / admin side. For the companies with hundreds and thousands of domains to manage, this causes a lot of extra work and automation and productivity is lost. There are other features such as 'Resend verification email', 'Child Name Servers', etc that I would imagine are going to be handled by developers creating an 'extended' version of each registrar module. Just my 2 cents.

Tyson - Is there a specific thread that we should provide feedback for this feature revamp or do you guys already have it all mapped out?

I figured that was the case but thanks for the confirmation.

I know this module update is not a priority right now but I wanted to document this 'concern'. I've had clients wanting to add additional SANs after the initial order so I have been creating an invoice for them and sending it but I can't 'manage' it from the admin side to change the additional number of SANs. I'm sure it's a similar programming issue to what was mentioned above.

Is it possible to add Domain Redirects to the module?

Fingers are crossed in hopes that this can make it into v4.0. Excited for the new release!

I did read that ModulesMatic is ready to create an Extended version of Logicboxes but I think he'll wait until 4.1 is released to see what change Blesta makes to the core.

I'm wondering if this new feature can pull from the terms defined in the packages.

I can see that this could get very cluttered in terms of what can and can't be renewed and for how long. I wonder if it would suit most users to have 2 or 3 years as a default and then allow up to 10 years for domains once that area of the software has been updated? This would allow customers to renew for 2-3 years on hosting, dedicated IP's, SSL and software licenses. If you try to keep it simple, maybe two years is the way to go since EV SSL can only be renewed for 2 years at a time. I'd like to see opinions from other users as well.

I'm waiting for JIRA to load again but I think some of the wording needs to be changed in the UI and I think there needs to be a limit on the number of cycles they can renew for but I wouldn't be opposed to letting them renew for more than 1 cycle. Especially on domains. If someone wants to lock in a price for 5 or 10 years, I'd be ok with that.

It does look like an issue on the Stripe side. I'm using the module with v3.6.1 and there are no issues for me. Hope they get it resolved quickly for you.

Let me give this some thought and get back to you. Hopefully others will chime in as well.

You're welcome! I'm glad it helped out another cPanel user!

I had issues for awhile as well. Try this: http://www.blesta.com/forums/index.php?/topic/5300-auto-debit-cron-stopped-since-dst/page-2#entry40034

Maybe my post was a bit worthless. I don't know the technical programming side of this and what it takes to make it all work. How would bulk renewal work? It would allow multiple services to be checked for renewal and then step them through the options available prior to an invoice being generated?

I wonder if this needs to be done on a per service basis (hosting, domain, ssl, etc)? This is kind of what I would invision: Admin side: Click the manage button next to a service and under the 'Actions' section, there is an option to 'Extend Renewal Period'. I don't know if this could or should be tied into the 'Change Renewal Date' option. From there, we would see the pre defined terms available (similar to upgrade/downgrade) and we could choose the correct one. From there, an invoice would be generated and sent at the scheduled cron time. I agree with Jonathan's comment here: I agree with the due date reflecting what the actual due date would normally be for that invoice cycle. I don't know if there is a clean way to 'mass update' with this feature. Client Side: I think the button should be placed under 'Manage' again. I wonder if a notification of some sort should be added on the client home page to alert them about this feature? Once they click manage, they're presented with a new button under 'Actions' and given the pre defined option to pay ahead. As I look at all of this, I wonder if it overlaps features such as 'Change Term'. It might make sense to us in the industry but not to the customer. A simple change to the wording on the action button could take care of this. We have had customers who wanted to pre pay one service but not the others which is why I present it this way.

Not sure what you mean. We turned off the username and password field on purpose.

Are you using the CORE cPanel module or one of the extended versions? We use the cPanel Extended version from ModulesMatic which gives us the option to show or hide the username and/or password field. Look it over before you make a change because there is no easy way to switch back and forth from CORE to non CORE modules. This may help you out. http://www.blesta.com/forums/index.php?/topic/5552-module-cpanel-extended-v42/

ModuleMatic, Thank you for maintaining and developing new features into this great module! Are you accepting donations anywhere? Can you look into why the IP address will not print in a welcome email? I have the IP entered in the 'Hostname' field and then I'm using this tag in the welcome email: {module.host_name} Should it be {module.hostname} instead? I'm also having issues getting the nameservers to show up. I'm using this tag: {module.name_servers} Thanks! EWH

We are receiving more of these requests too. I think clients want to lock in a guaranteed rate and it's great to boost the revenue stream. Any updates on this?