Answers to your questions about ispmanager. How we test the product and deal with bugs

A month ago, we answered your questions about how to get ispmanager for free, which language the panel is written in, and why our logo looks like this: //. Today we take up where we left off. This time, we got the developers and QA engineers to explain how bugs are found and fixed in ispmanager. As a little bonus, we'll answer a question from one of our users about CloudLinux.

1. What is the testing process for ispmanager?

Our QA engineer's answer

We perform both manual and automated testing. For new features, the process is:

1. First, the task is given to the developers to complete.
2. Then the task is reviewed by other developers.
3. If the review is successful, the task goes to the testing department.
4. If all is well, the task's status is changed to "awaiting merger" status and then goes to release. If not, the task is revised, retested, and then released.

There are two release branches of ispmanager:

Beta – where new functionality and improvements are first introduced. All updates to the beta branch are subject to pre-release testing.

Stable – changes from the beta branch are added here after extra testing and debugging.

2. How do you deal with bugs?

We track and fix bugs both through our testing and development departments and in response to your feedback.

We process bug tickets like this:

After a ticket is received from a user, our exception developer investigates it. If the bug affects the environment rather than panel operation, our exception developer fixes it immediately, forwards it to our support engineer, or instructs the user on how to fix it.

If the bug affects panel operation, it is prioritized. Critical bugs, which tend to significantly disrupt panel operation, are eliminated immediately through the release of an unscheduled bug fix. Serious bugs are fixed as part of the next upgrade. Non-critical bugs are sent to the backlog and fixed according to schedule.

If you've noticed a bug in the panel, please contact us via your Client area so that we can fix it.

We regularly update our list of existing bug fixes as part of the ispmanager changelog.

3. Why can't any PHP (Native) version higher than 7.2 be used 4in the CloudLinux module?

Tech support engineer's answer

This restriction is not global but rather depends on which PHP handler you have installed.

Any PHP version can be used for LSAPI. However, the server administrator must allow users to use cageFS and PHP LSAPI. Also, Apache must be running in prefork mode. You can view the Apache operating mode in the Policies section of ispmanager 6 Business or in the Software Configuration of other versions of the panel.

Likewise, for FastCGI any version can be used. The PHP CGI version can be selected for the user, rather than the site, in PHP Settings under User.

For more details on the settings, see the documentation: PHP Modes in CloudLinux