linveo

I see that Vultr is going to disable API v1 on June 30, 2023 and this is what the module currently uses.

In Invoice and Charge Options I have Invoice Days Before Renewal set to 10 days. However recently I had an invoice generated on October 25th, 2021 for a service that renews on November 20th, 2021. Does anyone know why this is happening?

Good to know! I must not have waited long enough for the cron process to re-create the Invoice. I created a manual invoice and the cron process didn't create a duplicate. There must be some sort of logic in there to prevent dupes.

I recently had a user schedule a cancellation before an invoice was generated (7 days before due date). Then the day before the due date/cancellation date they removed the scheduled cancellation. I noticed that the system did not generate a new invoice to reflect that there was not a payment due and I manually created one. Is this a known issue? Or should an invoice have been generated?

Thanks everyone! I guess if I need to re-check I will try the temp install.

I think you have misunderstood my question. I know the install does not change any of the PHP modules. It shows whether or not the recommended ones are installed. I'd like to review that page against the updated server configuration to make sure that all of the recommended modules are enabled.

During the install process, there is a page that checks for the required and recommended modules. Is there a way to view this page post installation? I just want to check that everything is still green after making some server configuration changes.

Yes, you can disable certain php functions in the php.ini.

Yes, I have the PECL version installed correctly. The error message went away after I enabled phpinfo.

Hello, On a new Blesta install I kept getting a warning while setting up the Department mail accounts that the PECL mailparse was not installed. However, it was installed and functioning correctly. The true issue was that phpinfo was disabled and Blesta could not verify that mailparse was loaded. I spent a good amount of time troubleshooting mailparse when it was actually the disabled phpinfo module. This may be an edge case, but it would be more helpful for the system to recognize its verification method could fail via phpinfo and not that the required modules aren't installed.