Paul

I had updated your ticket. Since you re-issued the license, your installation has not called home. You should try re-saving the license key. If that doesn't work, it hasn't been properly restored. It's very important that your original config file, original Blesta files, and original database have been restored.

After uploading the files, before running the upgrader try removing the following files, per https://docs.blesta.com/display/user/Upgrading+Blesta If Blesta redirects to /install it's usually because it doesn't detect a config file config/blesta.php This file should not be removed when upgrading, it's critical that it remain in place and unmodified.

The task is CORE-2397 which appears to be a side affect of CORE-912

I am able to duplicate it. The renew date is changed when it's provisioned and I think I know what task caused this to happen. I'm going to create a task for this and discuss internally.

What I was thinking was that you'd be alerted by the hook and then make a modification to the line items as necessary. I think I don't understand enough about what you're trying to do, and it's the Friday before a long weekend so my mind is a bit distracted. If there's another hook we could create to accomplish your goal, we'd be interested in looking at that. However, if modifying the core is the only way to do it, we might be interested in possibly adding it to the core. It'll depend, we'll have to look at what you've come up with and make a decision internally based on the direction of Blesta.

The gateway is available at https://github.com/blesta/gateway-payumoney If you'd like to contribute to it, so that it supports all of those regions, a dropdown option when configuring the gateway so that it knows which API endpoint to use may be the way to go. Feel free to submit a pull request.

To disable CSRF for a specific resource, see https://docs.blesta.com/display/user/Configuration+Files#ConfigurationFiles-Encryption Specifically: Blesta.csrf_bypass You may also disable CSRF system wide, but we highly recommend against that.

Mike wants to run code from our master branch lol

You may want to look at https://docs.blesta.com/display/dev/Event+Handlers Using an Event/Hook will allow you to tie into something like Invoices.add or Invoices.edit to trigger your plugin to immediately modify the invoice to reflect whatever discounts you want to reflect. Blesta also supports price overrides, which can be set for each service individually. Overrides override the normal package price, but not any configurable options.

We've been replying via ticket, but the most likely cause is that the Blesta.system_key does not match the database. This is a good place for someone with the same issue to start: https://docs.blesta.com/display/support/Encrypted+Data+Won't+Decrypt

I updated your ticket. The credit card data appears to be invalid, and should be re-saved. Possible encryption issue.

Are you saying that services ordered where a package is set to use pro rata to the 1st, generates the invoice correctly but the service renew date is not based on the pro rata date, but rather the anniversary date of the order?

Mike just told me the task is private. Yup, it is. I can't change the privacy without re-opening and closing it again and I don't want to do that so you can all just trust me on this.

I did some debugging, and it appears that the client/contact name is not available as a tag. If we were to add it, I think we'd want to first identify all of the support manager templates that it should be included in that it isn't currently, as well as the scope of the information to be included. Address? Email? Phone number?

You can ignore the bit about System.debug as that's in 4.x only. Is the issue entirely intermittent? Or are you seeing specific kinds of emails failing? If you have bad tags in an email template, that can cause the emails to error during send and not go out. Apart from those things, there may be something going on with your server.

Which voice servers are you having trouble with? I personally tested Mumble, and it worked for me. More details would be great. EDIT: Also be sure you're using the latest release https://github.com/blesta/module-tcadmin

We are not in a hurry to implement this, due to more highly requested items. We do have plans to do it eventually though, and the default option would be not to update automatically. The preferred method would be to click a button to upgrade. In terms of automation, there would be some options. [x] Never update automatically [ ] Security patches only [ ] Patches only (including security) [ ] Minor releases (including patches) [ ] Major releases (including minor releases and patches) [ ] BETA RELEASES (AT YOUR OWN RISK) Something like that.

I don't think it makes sense to log actions that are planned to happen. Logs are historical records. If you want to get a picture of what is going to happen, it may make sense if that was shown in Blesta someplace that it can be dynamically determined.

Because the cache directory was empty, it was removed automatically by our build process. This was corrected in CORE-2366 for the full build of 4.0.1, and will ship with full builds going forward.

Glad I could help. Be sure to change your passwords.

See https://docs.blesta.com/display/dev/Module+Methods, specifically calls to the method $this->log. Good question regarding monolog. I imagine extensions would be able to use the logger as well, we should consider putting together some documentation for that. Our plans are to do more internal logging over time using the new logger.

The page seems to be loading now, did they resolve it for you?

Did you check the mail log in Blesta? Tools > Logs > Mail log. I'm curious if Blesta tried to send a response, but it did not go through. If you'd like us to take a look at it, please open a ticket with the admin login to Blesta + your cPanel login (with SSH access.)

I see your ticket, but you didn't provide what we asked. I have updated the ticket.

Do you get any kind of bounce or reply when emailing the support department that is piped in? Do you have a single company in your Blesta install? If the ID is not 1 for the company, pipe.php should be updated to reflect that If there is no bounce or reply, check your mail log Tools > Logs > Mail log, to see if the support manager tried to send any response. In my experience, email to the piped in address should always respond with something, either a bounce from your mail server, or a reply from the support manager that there was an issue, or a ticket was created. Sometimes staff members are not assigned to the department that is receiving email, so check also that you are assigned to all departments.