Leaderboard

We had a brief power outage and MySQL failed to start on Jira, fun. Domains are a good example of renewing for more than 1 cycle, however domains are also very unique in that they have many other restrictions. For example, you can't register a domain for more than 10 years. I wonder if this type of functionality should be delegated within domain management and kept separate from standard services. (When we add better support for domains) If a case can be made for renewing other services for more than a single cycle, perhaps the setting that allows clients to renew early can also allow a maximum number of cycles to be specified. There is nothing preventing someone from renewing in advance again (Unless that were also included as part of this) so there is no upper limit.

If this is just for configurable options, it makes sense for it to be a setting for the option. For example, in the "Basic" section at the top of Packages > Options > Create Option. [x] Allow Upgrades [x] Allow Downgrades The issue is that how do we know what is an upgrade or a downgrade? There are different types: - Checkbox (Should we assume that checking the box is an upgrade, and unchecking is a downgrade?) - Radio / Dropdown (Should we assume that items toward the top of the Options you set are upgrades or downgrades?) - Quantity (Should we assume a larger quantity is an upgrade, and a smaller quantity is a downgrade?)

The cron is run via CLI, so Apache does not handle the request, and your virtual directories are not known. The virtual directory aliasing only occurs with Apache, so you should either remove the virtual directory aliasing to Blesta's directory so the path can be determined correctly via CLI, or run the cron via wget so that it will use Apache instead. If you opt to remove the alias to Blesta (i.e. rename the 'blesta' directory to 'services') and you get a 'license invalid' page when you try to login, then you just need to reissue your license key. To do this, log into your account, click to manage the service, check the 'Reissue' checkbox and save. Then the license will revalidate at the new location when you login to your installation.

Template files can be cached automatically by specifying so, e.g. class MyController extends AppController { public function myPage() { $this->startCaching(Configure::get("Blesta.cache_length")); ... } }

If you can make a service with OpenSRS and get us the service fields for that, and then go to a service with the Universal Module we can make a map for free.

Normally the plugin should add the folder in installation or update . Like the support manager . @tyson , what if we want to cache pdt file instead of calling it every time ? Your example for caching just a data .

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

Okay I have the following.. "*/5 * * * *" via the Cpanel's schedulor and "/usr/local/bin/php /home/CpanelUser/public_html/dirofinstallion/index.php cron/?cron_key=mykey >/dev/null 2>&1" as the command in Cpanel. Okay now it working! Thanks you very much.

In terms of what you recommend for the client side, this is almost identical to what the task describes in CORE-2058. From the admin side, an option under Actions would be fine unless we allow bulk-renewal as specified in the task.

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.

This sounds like a great start. I agree with the due date reflecting what the actual due date would normally be for that invoice cycle.

Please see CORE-2058. This thread will serve as a point of discussion on this task.

This not change the cPanel Password, Only changes the password in the Database. You can Log in as Client and change the password in the Change Password Tab. In the next update I will add an option to change the password from the Admin Area.

Please see CORE-2056

If the support department is 'hidden', then clients cannot see the department nor open a new ticket in that department. However, they can still reply to tickets that are opened in that department.