
turner2f
Members-
Posts
614 -
Joined
-
Last visited
-
Days Won
14
Everything posted by turner2f
-
@Blesta Addons I understand what you mean. But it would be an improvement to RE-vamp this output, since I imagine many of us would default to ( and benefit from) the understanding that when you manually change the "Payment Received" that it should show up on the invoice too. ============= Again, hopefully Blesta will see the value of doing so in an update, as i have already posted this as a "Request" . ============= I imagine many of us would be more concerned with when the checks are actually cashed and posted, rather than when they are "received" ============= And ALSO, this is an issue when we are receiving RE-curring PayPal or Authorize.net payments that are not connected to the Blesta system, since those RE-curring payments were already in place BEFORE we were using Blesta.
-
Already did for some of them. Although, I do not have time to post a separate request for each and everyone of them as previously requested. ========== Hopefully Blesta will see this post and take the personal initiative to put it on their own "To-Do" list.
-
Thanks for the clarity. And as you mentioned ... As I am not certain why we are allowed to pick a "Date Received" when it does not even appear within the "Transactions" section of the client's page within the Admin area either. This really should be improved in an upcoming update on BOTH ends.
-
@evolvewh I agree. I discovered this exact same issue back in January 2017. I received some checks back in October 2016 before I installed Blesta, and wanted to get them recorded into the system once I got Blesta setup. I recorded a " Manual Payment " for these checks, set them up as being received in October 2016, and they STILL showed up as January 2017 on the back-end and on the receipt sent to the client. So it would appear as if I received the checks in January 2017 when they were actually received and cleared in October 2016. ============== In fact, here are two (2) screenshots of where I received a PayPal payment ( for an invoice not connected to Blesta ) and needed to manually record the payment as coming on March 27th, and it STILL showed up as on March 28th instead on the day before.
-
My " two-cents " is that Blesta needs to use many of the various features that the 3rd party plugins offer as a " blueprint ", and then to integrate those same features into the core so that they can be stable and extensive . Without many of these 3rd party plugins the user-friendliness, and rich features of Blesta would be missing. Please consider rolling these same features into the core, and then expand on them.
-
Thanks. Resolved it.
-
@evolvewh Thank you for your reply. The "Deletion" and "Filtering" functions will be a welcomed update. @Paul Thanks for the reply. I will give it another go concerning the "Sub-Account Ticket Bounce" ... https://www.blesta.com/forums/index.php?/topic/8613-sub-account-emails-receive-a-ticket-bounce-email-notification/ https://dev.blesta.com/browse/CORE-2361 ======== Before doing so, do you have an online demo of Blesta where I can test this out as an Admin and a Client ?
-
Found another issue with the Ticket System. Merged Tickets get Truncated when "Closed". When a tickets get "Merged", you can see all the merged contents while the ticket is "Open". When the ticket gets "closed", the merged ticket only shows the most recent ( the newest ) part of the ticket only. ============= Desperately looking forward to an update or a re-vamp of the core ticket system. Too bad Paulo V's plugin no longer works in version 4 Stable. Many of us LOVED the functions and options it had. Please consider using it as a blueprint . ============ Look forward to your assist or reply.
-
@Paul OK. So are you saying that many of the same features that were in the plugin will be "cleaned-up" and then implemented into the core ? If not, it would be great if we could get the "sub-account" issue resolved so we can allocate our ticket system for folks that only have a main account or sub-account. Is the "sub-account" issue being reviewed for version 4.1 ? Currently the support ticket system has to be "open" to everyone, even spammers .
-
@Paul or @Tyson We really need the ability to delete these tickets, instead of having to go through PHPMyAdmin. We had to leave our departments "wide-open" until an update can be made concerning the sub-accounts issue at This leaves us open to getting spam, and constantly having to "close" them while they build up. Is there a decent ETA on getting this function for the tickets ? Or can you just "reverse engineer" the "Support Manager Pro" plugin so that it will work with Blesta v4.0 Stable ? The "Support Manager Pro" plugin was practically perfect for everything many of us needed . ======== I recall Paulo V. mentioning that he/she was completely ok with Blesta taking over his/her Support Manager Pro plugin by " adding it to the core ". And Cody saying, that, "A number of these features we have in mind for adding to the support manager" . This was back in 2014.
-
Voted.
-
Hello Adam, Sure hope you get the assistance you need. Checked out CERB, and it looks fantastic. And it's got all the functions we all need too. Will be happy to stress-test your plugin when ready.
-
@Blesta Addons Thanks for the insight on what happened. Well, while Paul and the team are working on the "EU invoicing system" and "domain pricing system with a logical hosting order(domain+hosting)", hopefully they will create a plugin very similar in functionality to Paulo V's "Support Ticket Pro". ============= The "Support Ticket Pro" plugin had quite a bit of useful functionality essential to the Support Ticket experience. ============= @Paul Being that most of the work is already done will Blesta consider taking over and integrating the "Support Manager Pro" plugin ( with Paulo V's approval ) so that it will work with Blesta v4.0 Stable? Is this a consideration for the Blesta Core team ? Look forward to your reply.
-
The bounce for SUB-accounts still occurs in Version 4.0 STABLE When the Department Email is set to YES for "Allow only clients to open or reply to tickets"
-
"Limitations do not apply to renewing services" for coupons is not working. It does NOT appear to override the Max Uses on "renewable services" And if I try to RE-insert the SAME coupon for a service I get an error that says, " That coupon does not appear to be valid. " Please see the screenshot.
-
Just posted a request at... https://requests.blesta.com/topic/need-notification-if-a-ticket-is-manually-closed-by-customer-with-no-updated-message
-
Had to give up using the "User Manager Pro" extension since it seemingly does not work with Blesta version 4.0 Stable. So we are now using the core version of the ticket system. Really look forward to having at least three (3) functions added to the core version... 1) - The ability to delete tickets and their attachments 2) - The ability to have the Departments in a left-side navigation tab (folders) where we can allocate the tickets for user-friendliness OR Alternatively, if we could have a user-friendly " filter function " for the Departments 3) - The ability to see the Client's name next to the ticket's name so that we can quickly identify THEIR ticket when viewing the list of tickets on the dashboard. ============ Look forward to your consideration.
-
RESOLVED. I cleared the cache and now it's fine I used the "Admin Tools" plugin found at ... https://www.blesta.com/forums/index.php?/topic/2925-plugin-admin-tools-more-options-for-staff/#comment-20938
-
Upgraded to Stable Version 4.0 Changing the URL's within the Config - - > Routes.php file does NOT change Top Menu and Dropdown Link URL's within the Admin area. /** * Admin panel directory name */ Configure::set("Route.admin", "adminarea123abc"); /** I even went to the "Upgrade" page and the links are still using /admin/ instead of /adminarea123abc/ FYI - This issue is only affecting the Top Admin Navigation menu and the Dropdown links. All the other links within the page interface are fine.