Paul

Are you trying to get the user id of a client or admin?

Are you asking how your customers can see the package and order it? Create an order form under Packages > Order Forms When creating the order form, select the Package Groups you want to sell, these Package Groups contain the Packages you want to offer. Under the "Settings" tab, you can select which order form should be the "default", which will cause it to be selected when clicking the "Order" link on your portal page. (That you linked above)

Yes, it would be possible to do that by modifying the invoice template. I don't have an example for you, but someone on the forums may be able to help you, especially if you're willing to pay for their time. Should be a pretty simple, 30 minute change if that.

It's not possible to add another text field to cPanel, either as a config option or to the module unless you modify the module's code to add that functionality. That might be an option. The other thing you could do is create a new Package for this, using the Universal Module, and a Universal Module product with 1 or more service fields that ask the information you require. You can make the package an addon to your cPanel package, and it can have a $0.00 cost. The client will then be able to add the addon during checkout, and specify those options. It may not be as intuitive as if it were a module text field, but it should work.

The gateway will be open source and made available at github.com/blesta/ soon, so feel free to submit a pull request if you have something to add of value to the community.

User/Pass for an admin panel script install, is that something the customer will provide to you? What module are you using now? If you are using the Universal Module, create another service field for it under Settings > Company > Modules > Universal Module by editing your Universal Module Product.

Might be, will have to wait on a fix for contact logins in order to determine that.

Support contacts should be able to open tickets yes. I suggest doing a little test. Login as the contact to the client area, and open a ticket in the UI. All work fine? Then, update the ticket as an admin, and have the contact reply to the ticket to update it. Get a bounce, or work? What version of Blesta?

I'm guessing you used an IP for your cPanel/WHM server listed under Settings > Company > Modules > cPanel? You can use your servers hostname instead, which I would recommend. If you have an SSL cert for the server, it's better to use the hostname so the user won't get any SSL errors/warnings. I also suggest enabling the WHM setting that redirects to the server's hostname. For example, mydomain.com/cpanel -> https://your.server.com:2083 for the same reason.

If running the cron manually under Settings > System > Automation works as expected, it should work the same exact way if you set up your cron to use wget, GET, or lynx which simulate a web browser. From https://docs.blesta.com/display/user/Installing+Blesta#InstallingBlesta-4.SetupaCronJob

Check out the beta version of the PayUmoney gateway at

Attached is a beta PayUmoney an Indian non-merchant gateway. Please give it a try and let us know if you have any issues with the gateway. To install: Unzip payumoney.zip Upload payumoney directory to ~/components/gateways/nonmerchant/ Access Settings > Company > Payment Gateways > Available, and click to install & configure payumoney.zip

Probably. When? I'm not sure.

That depends on the error, what error are you getting? Can you give us more context?

Text fields are not included for configurable options because config options affect the price, and there's no way to determine a price for a text field. Checkbox, Radio, Drop Down, and Quantity are different. Text fields are typically used for things like domain name. These fields are specified by the module. If using the Universal Module, you may create service fields that are text fields that do not affect the price. For a domain like cPanel, an additional text field would have to be added to the module as custom code. What is the purpose of the text field?

Assigning a class to the outer div, and setting it to display: none; would be preferable. Still a change that would have to be re-added when upgrading.

Just FYI to the OP, this has been implemented and is available at https://account.blesta.com/client/plugin/license_verify

I don't have an example for you, but if you hide this and someone tries to sign up using the same username for an account that already exists they will be unable to register and either have to select a different email address, or login. We have some customers who have multiple accounts for legitimate reasons, so we wouldn't want to restrict this. A feature request has been made for a setting to force email address as username, so it's something we're considering implementing system wide. The approach I would take is assign a class to the div for the form element, and in CSS set it to display: none;

REQUEST_URI being undefined is troubling, I'm not sure what would cause that. What I would suggest as a test, is try running your cron via wget, GET, or lynx instead. See the example at https://docs.blesta.com/display/user/Installing+Blesta#InstallingBlesta-4.SetupaCronJob "Running the cron via the web". Curious if that resolves it. Might then be an issue with your CLI.

You could hide the option with something in CSS like "display: none;"

Very useful, nice work! Does it work on the order forms? I noticed it works on the portal, if it works on the order forms also, would be very useful.. maybe a screenshot of that would be more effective. I can see people using this for discounts on holidays, and the order form would be a perfect place for it to appear. Can't wait to see how this looks in Blesta v4 and the new UI.

You should check the task, it's not likely we'll post here when its resolved. We're working to get it in beta 5, so i'd suggest checking back once we release beta 5 to see if it's in there.

That probably explains it, hang on and watch the task status.

That's what I'm thinking, why I asked for the version.

We don't use 30 days for monthly, it's calculated as (date +1 month) for monthly. The term and period as configured on the package is always used. (day, week, month, year). Typically a service added on the 1st of the month will renew on the 1st of every month, but it's possible depending on the time it was added that the invoice could be due on the last day of the current month.