Paul

Yes, I believe you're right Mike. We don't recommend modifying this, so tweak at your own risk.

Plugins register nav links by registering them in the database under the plugin_actions table with the actions listed below: nav_primary_client nav_primary_staff nav_secondary_staff Look in the table for examples. Otherwise, you'll have to manually edit the templates. I think @Licensecart CMS plugin allows creating nav links that link to external resources, but I could be wrong. Alternatively, you can modify the templates.

If you have an owned license with us (Pretty sure you do), you can just open a ticket to request a dev license at https://account.blesta.com/client/ (Click Support). We'll add one to your account, no cost.

Pretty sure someone could create an order template that does this now. It would break the mold a bit, but I believe it's possible. Most of the forms we looked at when we implemented this originally went from Domain > Hosting> Configure & Checkout. Reversing those first two would definitely be a good alternative and something we will consider.

CORE-2308

I am able to duplicate this, not exactly sure the cause yet. I'll create a task shortly.

All public model methods are available via the API, including those of extensions. There is a lot you can do, and I don't see any reason you couldn't build a separate application that interacts with the core and/or the order plugin for orders. You could even write your own order plugin, and disable the default one.

3. No. When making a PayPal payment, the customer has to login to PayPal to complete the transaction, so no need for Admins to have access to that. Though, you can "Login as client" to access PayPal payments. 5. Not with PayPal, Blesta does not store credit card expiration numbers when paid via PayPal, nor does it have access to any of that. 6. If the customer sets up a PayPal subscription, the payment will occur from PayPal automatically if they have enough funds. If you want to accept credit card payments directly, you will need a merchant gateway like Payflow Pro, or Authorize.net. We are partnered with Evo to provide good discount rates to our customers who want to use Authorize.net. You can sign up at https://www.evopayments.us/accept-payments/blesta/ if you are interested in that.

It's against PCI-DSS rules to store CVV data, so we do not do it. You would be out of compliance. Your gateway should be configured not to require CVV data for subsequent transactions.

TCAdmin is not included in v4. It's a big one I want to get rolling on though, and we could release it between releases. The goal for the new year is to pick up the pace on core development with smaller, quicker releases, and also release new extensions between releases. There were a lot of issues with the minPHP bridge, including issues with PHP 7 among the bridge and 3rd party libraries we use. Most of those have been corrected in beta 4 with only a couple lingering PHP 7 issues remaining that we're aware of. If you're looking to help us get to a final release, please consider doing some extensive testing with the beta. The way things are looking right now, I think there will be 1 more beta, then final release. We're working hard to get that final beta out shortly.

You can use wget, GET, lynx, or another web-based method for your cron. See https://docs.blesta.com/display/user/Installing+Blesta#InstallingBlesta-4.SetupaCronJob There is a wget example, you'll just need the cron key shown under Settings > System > Automation. Using wget would be similar to running the cron manually in your browser, so if that works then this will work for you.

The module was released by them under the MIT license on our Github at https://github.com/blesta/module-thesslstore and we will be accepting pull requests for bugs and improvements from them, us, and the community. I'm sure the module will be improved, especially after we get more feedback from people.

The SSL Store wrote this initial release and made it a requirement. I'm not exactly sure why, but I assume they had some business reason for this.

I am able to duplicate this on PHP 7 also, but only when the debugger is enabled. With error reporting enabled without the debugger, I'm not getting any errors at all and the page loads and seems to work just fine.

I'd suggest posting this on https://requests.blesta.com to request that the password link expire after it's used. It's not a bug, but it is a good idea.

If you've tried the Support Manager Pro and it's not working as expected in v4, the author may be willing to update the plugin. They'll likely want to update it anyway, to make use of the new bootstrap buttons and font awesome icons used throughout the admin UI.

No. PayPal requires the customer to login to their PayPal account to process payment, so it would be useless to an admin.

Probably, but I doubt there is any mechanism in place to invalidate the link currently.

Only clients can pay with non-merchant payment gateways. Login as the client, or checkout as a client.

Only happens with the debugger plugin? What version of PHP?

Please check to see if you get this error in Beta 4.

If the order was approved, and the service is "Pending", and the invoice has been paid, it will be provisioned the next time the cron runs. You should have the cron set up to run every 5 minutes. Look under Settings > System > Automation to see when it was last run, and what you should set up the cron job as. You may also run the cron manually here.

When you create a contact you can set permissions for the contact. Both staff, and clients creating sub-contacts. These are not the same as Staff ACLs, but should be sufficient for most cases. In this screenshot, the "Support" permission is from the Support Manager plugin, so you should be able to accomplish what you want with your Cerberus integration.

Sounds like an incomplete upgrade. Did you run ~/admin/upgrade? You can check the migration files for that table.field to see when that was added. I can look when I get to the office later this morning.

Most people won't know that it would break anything by changing the module. Most people won't write a new module with the same meta fields, and want to switch it over. I agree there should be a way to do this, disabling module changes was the simplest way to stop unaware people from making a change that would negatively impact their installation. If you're able to write a module, it shouldn't be too hard to write a query to update the packages to use the new module. In the future I'd like to create more separation from packages and services, and then we can safely allow the module to be changed.