Jason Ryan

That file is there for new installs and to help make sure that you don't overwrite your existing blesta.php file if you're upgrading.

Hey -
I let it go yesterday since I almost had a heart attack thinking I totally screwed something up but got my backup up and running. I may try and give it another go tonight, this time paying a little more attention to what files are being moved around in "helpers' & "lib", and also making sure my existing blesta config file goes untouched. I will report back either way. Thanks for the follow up

If you never got to the upgrade screen and ran the upgrade, then your database is most likely untouched. Be certain that your original /config/blesta.php config file is in place, as it's the most critical file in your installation.. as well as the Blesta files for your exact version prior to attempting an upgrade to 4.0

I did some debugging, and it appears that the client/contact name is not available as a tag. If we were to add it, I think we'd want to first identify all of the support manager templates that it should be included in that it isn't currently, as well as the scope of the information to be included. Address? Email? Phone number?

Unlocked. Any feature requests are best to be at https://requests.blesta.com, so it's ok with me if it's a duplicate so long as it's not in the same place.
Regarding this feature, the support system does not support HTML, but it does support Markdown. So, we would be open to adding a markdown editor like stackedit.io, and we already have a task for this.. see https://dev.blesta.com/browse/CORE-2299

Oh yeah, and this screen tease is out of date too, now we have a dropdown menu. Lots of people didn't like the sub-nav looking like bread crumbs.

http://blesta-addons.com/order/signup/index/registration

You're welcome mate

Thanks Mike!

I want to add desktop notifications to the ticket system, and re-organize it a bit so you can more easily see tickets assigned to you. This might be preferable to email notifications of unanswered tickets.. improving the UI, and possibly doing something with desktop notifications.

Thanks, but the Support Manager is already a plugin and this request is something that should really be baked in as default functionality to help improve engagement and turn around time with support. Right now it is not a huge factor for me to need something developed for it. I will wait to see if @Paul and the guys can work this into V4 or maybe update the plugin itself, if not I may reach back out.
Thanks.

Hello -
I am using the Support Portal plugin and have a quick question, is there something to enable administration notifications that a ticket had been sitting for X amount of days? Something that sends an email reminder to the Staff person it is assigned to in order to remind them they have a ticket in their queue? I have an employee who constantly forgets to reply to tickets after assigning them to himself and they often go unnoticed by others, would be nice if I could set it to "nag" if 24 hours has passed or something.
Thanks in advance.

Thanks Mike! Posted

I wish I had an idea of what's going on here. I think some further testing, outside of your live environment is in order.
Install a fresh copy of Blesta, run some tests using the included Stripe gateway Install a fresh copy of Blesta, run some tests using the 3rd party Stripe gateway Do both work as expected? I think it's important to narrow down the issue to either a problem with the gateway, Blesta itself, or your specific installation. Running a test like this should help narrow it down. If you need a couple trial keys for these test installs send me a PM or open a ticket with us.

Yes, sorry for the delay. This should now be pulled and 1.0.5 released, which includes the Invoice's ID code in the statement description, rather than the Invoice ID itself.

Hi there, sorry for the delayed response.
We've tried to replicate your scenario multiple times, but are finding it really difficult to see what you're seeing. We are using test Stripe credentials, and have tested every card at https://stripe.com/docs/testing, which are all returning the expected success, or error codes, with the data being saved as expected. We're honestly not entirely sure what could be causing your issues currently, but suspect that the old data, and mismatch you have now between Blesta and Stripe (after the upgrade process) is the primary cause. 
Until we're able to replicate the issue that you're seeing, you may want to opt to switch back to the official Stripe gateway as provided by the Blesta team, sorry!

This is something we did explore when developing this addon, but came to the conclusion that as Stripe sends this information along to the bank, it's really down to each individual bank if they choose to use it. From our experience, most european banks will display the company name, phone number, URL, and statement description, but this is a lot more rare to see in the US.
It's something we'll definitely consider in a future iteration of the gateway, but have no plans currently. We're always happy to resolve and fix any bugs, but our time is pretty limited when it comes to feature requests, especially those beyond our use case, sorry! Let us know if there's anything else we can assist with, and thanks for using the gateway!

We've pushed 1.0.4 to GitHub, which upgrades the PHP Stripe SDK, and removes invoice IDs from statement descriptors for now. https://github.com/nodecraft/stripe_plus_gateway/releases
We'll look into including the invoice number on statements instead in a future release.

Ok, well that explains why I never even seen the "Upgrade" button... thanks again for the help! I will report back if I have any further issues.

@viablethought I'm happy to have helped. I'm still a little concerned about the messages you received before, but I'm glad to understood how the payment accounts got de-synced. More than likely it sounds like you have an install with a lot more mileage and the auto-recover function to find their stripe id couldn't find the correct Stripe Customer ID to use.
To upgrade you first need to overwrite the files, while the gateway is still installed. After the files have been overwritten you can finish it up by visiting the Gateways page and clicking the Upgrade button. Voila, you're done!

@Paul Thanks for the information. It appears as if `invoiceArrayToAmounts` method within gateway_payments (which is eventually passed down to our gateway) only ever returns the raw `invoice_id` and `amount`, which is all we used. I suppose we could lookup every invoice and get the invoice number instead, but that wouldn't solve the issue from appearing in any other gateways that expose this information to the client, such as via the PayPal form (albeit a little more difficult to find).
We'll push an update shortly to remove the invoice ID from statement descriptors for now until we've investigated a little further. Thanks! 

@NETLINK - Thanks for throwing this together! This will be very useful for clients no doubt. Going to install and test it out. If all goes well I will definitely donate to the cause.

A customer reports that the Invoice ID, rather than the Invoice Number is passed along to Stripe. This number is then included on client's credit card statements. It's possible that this issue exists in the official Stripe gateway as well, but I thought I would mention it here in case @Cherry doesn't mind taking a peek.
 

No date yet. The details are a couple tasks need to be done and that necessitates redesigns to make them happen. When that's done, it's beta time.

Thanks, much appreciated! Now we just need to get v4 beta out to ya, and that'll round things out nicely.