Tyson

What he's suggesting to do is to assume "[]" is equivalent to "array()" and set the same line as the OP: Configure::set('Blesta.csrf_bypass', ['config::preconfig','domain_form::index']);

Having a specific solution is very useful, so if you can have a unique module dedicated to the management of each of your SaaS apps, then all the better. That makes it easier to manage changes granularly. The Universal Module (or even the None module) is there to use when you don't have a specific module or don't need one that is more complex than collecting a few extra fields and notifying you of an event. It sounds like your solution right now may be to use the Universal Module until you create separate modules for your applications. Whenever you do that, you can make the packages using the Universal Module inactive, stop using them, and maybe even write an importer that will move them over to your other custom module. Whatever you decide to do will come down to what is the best trade-off for your business to pursue long term.

I'm not sure what you mean, could you clarify?

You don't want to upload the "Omnipay-Blesta-Module-1" folder to the server. You want to upload its contents. That folder should contain two folders: "components" and "vendors". Upload those to the Blesta web directory on your server. There should already be a "components" and "vendors" directory in Blesta's web directory, and the folders will be merged when you upload them. Then, you should have the gateways listed in Blesta.

You can FTP to your backup location and remove old backups you don't need. Blesta doesn't currently enforce a rotation policy on database backups off-site.

We'll have to duplicate the issue first and see what can be done to fix the ip/port. Not sure why that behavior would have changed with Multicraft though.

Yes, the JavaScript file was updated to that in v4.4.

That would mean that the gateway is already installed, so you should look for it under the "Installed" tab of the gateway list.

What order template are you using? Your site looks like it has custom changes to the order plugin. That could be responsible for the problem. I wasn't able to duplicate this behavior on an AJAX or Wizard order template. The Order plugin shouldn't redirect to another page when you redeem a coupon, it should just refresh the Order Summary section via AJAX.

What's in the log that indicates it is a problem with executing cURL? Typically, a 500 or cURL error is due to a server misconfiguration, like a closed port. Are ports 2030 and 2031 open?

It's going to take some thinking to determine what the best route to follow is for what you're doing, but your best option is probably going to be to write a plugin and provide end-points to that plugin via the API or web to perform your new functionality. Plugins in Blesta can access the configuration setting to get the key as-is, so that shouldn't be a problem. I'd be curious to know why accessing the key from a database table would work, but an API call to a plugin wouldn't.

I'm not aware of an existing extension tying into Firebase. I'm also not familiar enough with Firebase to determine whether what you're aiming to do is possible through it, but Blesta can integrate with third-party services to manage them, so you could provision a service using Firebase through Blesta and manage it from within Blesta if you constructed an extension supporting those features.

You can only update to new patches within your current minor version. So if you are currently using v4.5.0, then yes, you can update to v4.5.2. You will need the support and updates in order to upgrade to v4.6.0+.

Are the URLs to the sandbox, live, and refund end-points identical to what they were before, but just at the EU TLD? It looks like the US DOJ charged the company with a felony and took down their website for processing transactions without a license, so that's probably why they moved operations to their EU domain.

It looks like they do development themselves since they created an integration for WHMCS, among others, which are available on their github. I would be inclined to ask them if they could develop a module first.

Thanks, I've created CORE-3204 for that

Have you asked PayFast if they would be interested in integrating their gateway for Blesta? It looks like they have done so for various other platforms.

Thanks, we'll take a look.

I may not have been clear in my last post. I meant to ask if there should be any visual display/text to describe what the limits are when using those buttons? It may be that no text is necessary and the button limits will suffice.

The navigation is not currently editable from the UI, but you can create a plugin that adds a link to the navigation that will accomplish what you would like. Also, we have some payment gateways that support ZAR, are they not available for use in South Africa? e.g. Braintree, Converge, Stripe, 2Checkout, Payza, Skrill? What payment provider do you use?

This would be a replacement for the quantity slider, correct? How would you suggest handling the limits in this case? For example, if I handle a quantity in the range [0, 500] at increments of 5, should I make those min/max quantities known anywhere?

What change to the default template do you think should be made?

The renewal price will be grayed out on the package if it is the same price as the base price right next to it. In this case, the difference is moot. Is that the case for you? e.g. the price is 5.00 and the renewal price is also 5.00?

What do you use to determine if someone should be disallowed to create an account? Perhaps such constraints should be supported by Blesta some other way. If we had before and after events for actions, I'm not sure we would necessarily prevent an action from completing based on what a before-event does. We currently don't do this with after-events now.

Are you sure there was an error? It will set errors if there exist errors. The integration is very similar to your suggested source updates.