Paul

The problem is that you added "qty" as a Package option not a Service option for your Universal Module Product. This should be under "Service Options" not "Package Options"

Do any records in support_tickets.date_updated = '0000-00-00 00:00:00'? They shouldn't. If any do, update them. You can set the date updated to the same date the ticket was closed, or opened. Backup database first. This is most likely the reason for your error.

Does this mean our module will continue to work again because you've resolved on your end, or will we need to make any changes? If we need to make any changes, your help is much appreciated!

I just emailed Litespeed support, we were talking with them back in January, so hopefully they can help.

It sounds almost like they don't want anyone to use their API. In order to correct the issue, we need something to go on. Trial and error with the API will take far too long. Is there someone from their team you could put us in touch with?

? VND isn't supported by GoCardless. I don't understand what you mean, can you elaborate?

I'm not surprised that debugging enabled can break things. I don't know the reason, and maybe Tyson can shed light on it, but I've seen debugging break things before which is why when we ask people to enable error reporting and debugging, we ask them to disable debugging as soon as they are done testing. I hope debugging is not enabled in your production environment?

Yes, if you add it as a Service field in the Universal Module Product, the customer will be able to set a value during checkout. Care to share your configuration? A screenshot would work. There are different ways to handle quantities. Adding a "qty" field on a Universal Module Product. (What I have been talking about in this thread) Adding a Configurable Option of the type Quantity. The first option will take the quantity entered or selected, and multiply it by the Package price. The second option is additive. For example, if the Package is $10/mo, and you have a Config Option quantity where each item is $1/mo, and the customer selects 5 of them, they would pay $5 for the config option + $10 for the package, $15/mo total.

For quantity - using the Universal Module, you can create a Product with a Service field called "qty". This can be a text field, or drop down, or whatever you want. The price will be Quantity * Package Price. Note that there is a bug with package quantities like this in 4.3.0, resolved in 4.3.2. So if you are running 4.3, make sure it is 4.3.2.

You want to add something a user can order and then you get an email? Here are the basic steps: Install a module, or use the none module. If using the Universal Module, create Universal Module Product. If you want to ask the customer for something during checkout, like their domain, then enter a service field for that. You cannot charge extra for service field options Create a Package using the module, and add it to a Package Group Install payment gateways you want to use (Settings > Company > Payment Gateways) Create an Order form, and assign your package groups to it, and select your gateways and currency. Packages > Order Forms Under Billing > Overview, click the cog/gear icon in the Orders widget, here you may subscribe to get order notification emails.

If there is no change, then it's probably night the right one.. or you aren't using the right language. If you are using en_us for example, and you translate es_es then it wont be loaded.

"None - Show Listing" will show all the user has permissions for. The alternative is to select a specific order form, which I guess could have no products or no payment options.

The task is CORE-2798 but I don't have an ETA and its not assigned to any sprints. PM me if you want to continue our discussion, I don't recall where we left off.

Only thing I can think of - Create a department for the Staff member, then change a ticket's department when you want to assign it to them. The Staff member will not see any tickets in departments that they are not part of. Easiest way to limit what a Support Staff member sees.

Oh, also.. you can check your logs, typically under ../logs_blesta/ for any entries that are written when you get the white page. You can also enable error reporting in /config/blesta.php (Change Error Reporting from "0" to "-1") which may output the error to your browser instead of the white page. Be sure to change back when done.

What version were you running, and which did you upgrade to? Did you upload the full version of Blesta or the patch? Patches only work if the patch version changes (z in x.y.z). Did you run /admin/upgrade after uploading the files? Did you check under Settings > Company > Plugins to see if the Support Manager has any upgrades that need to run? I'm able to create new departments under 4.3.2 without any trouble.

Where can we find API documentation?.. and why in the world would they implement backward incompatible changes to their API right out of the gate? I hope this isn't a sign of what to expect from them going forward.

A new GoCardless alpha non-merchant gateway is available. To install, download the attached gocardless.zip and unzip the file. Upload the gocardless directory to ~/components/gateways/nonmerchant/ and go to Settings > Company > Payment gateways to install it. Documentation is right here - https://docs.blesta.com/display/user/GoCardless Any comments or suggestions, please post them below.

Are you referring to the "Order" navigation link in the client area? This always appears, but where it links to depends on your Order Settings under Packages > Order Forms > Settings tab. If Default Order Form is set to "None - Show Listing" then the link will show all order forms. If you select a specific order form, then they will only see that one.

Apart from release videos, which show new features on our blog we only have install and upgrade tutorials at http://tutorials.blesta.com/ We are planning to start producing a line of video tutorials for using different features. If you have some suggestions on where we should start, that'd be great. If you need help doing something in particular, I can help.

What module are you using? What configurable options are you trying to create? The basic flow is this: Create a Config Option Group Create your Config Options, and assign to the Group Create a Package Group Create Packages, selecting the Config Option Group previously created, assigning the package to the Package Group If you have trouble with that, and can explain what options you're trying to create, pricing, etc. and want to PM me your login, I would be willing to create a package with 1 or 2 config options as an example for you.

What option should you select when? When "Recording Payment" - manually adding a transaction as an admin? You can select whichever option makes sense. IF you have 2checkout and PayPal installed though, the customer should be able to make payment with those methods and the transaction be applied automatically to their account. In that case, there's no need for you to select either. 2checkout and PayPal are both non-merchant gateways, meaning the user can pay with them by name. They leave Blesta to complete payment, and then return. CC & ACH options are intended to work with merchant gateways like Authorize.net, Stripe, and others where the customer completes the payment all within Blesta.

What version of Blesta are you running? The issue described in this task was resolved in 4.3.2.

All of the AJAX templates are a single page. AJAX Slider, AJAX Boxes, and AJAX List. Wizard templates are multi-step, and would not be all on one page.

Can you give a use-case for this? Where do you intend to display the messages, and what are the messages for? I would like to add a messaging system to Blesta, for both Staff and Clients, that can alert them of specific things in the interface, from any page. Curious if that fits in with what you're thinking.