Jump to content


Alpha Developers
  • Posts

  • Joined

  • Last visited

  • Days Won


velaware last won the day on September 3 2017

velaware had the most liked content!

Profile Information

  • Gender
    Not Telling

Contact Methods

  • Wire

Recent Profile Visitors

2,055 profile views

velaware's Achievements

  1. I wrote a small script that aims to help people start on projects extending Blesta. Currently it only allows creating a plugin, but I will be pushing up more templates sooner than later (want to get at least simple module template done too). Any feedback is welcome. This is written with simple PHP in mind, as I didn't see a need to use a full blown framework, so the code may be a little spaghetti. Originally this was going to be written in shell but wanted to make this useful for non-*nix users as well. Project link: https://github.com/velaware/blesta-developers-tools
  2. Per my fixes they are within the SMP plugin itself. As are gosu's.
  3. I have not put up my changes as they are minor really. If there's a demand for it I can, though. For the support ticket issue, it sounds more like an issue w/ your email's spam filtering not working as well as it should vs. an issue with Blesta. Unfortunately there's not much that Blesta can do about that besides putting some sort of validation in place. But, they also offer an option to disable anonymous users from sending emails to departments.
  4. I can see reasons why Blesta wouldn't allow this. Other systems too don't allow this. I.e.: Kayako doesn't (or at least hadn't in the past). For historical reasons, and I'm sure some legal aspects, it's usually best to limit what can be deleted in a client-facing software. ALso thanks @gosuhost for the further explanation. If you want I will edit my fix post with what you gave.
  5. 1. As far as I could tell, yeah. I'm still not 100% following the badge issue but rather investigate than say it's wrong off the bat. 2. When I have some time, sure. 3. Given Blesta is an ever-changing platform, there's no guarantee of future proofing any 3rd party element. Essentially it is up to the author or maintainer to ensure consistency. If the author wants to turn the product over to someone else like I, then I can do my best.
  6. It will work at least up to 4.0 on PHP up to 7.0. I haven't tested it against 4.1. There is a side effect to my badge fix that I wasn't aware of initially, that someone PM'ed me about. When I have some time I will see how that goes or if they want to post here they can.
  7. I have not looked into User Manager Pro (nor was I aware of such plugin). My fix is strictly for the most recent version of the Support Manager Pro plugin. If you are looking for a solution to get UMP to work with Blesta 4.x feel free to PM me and we can discuss the matter. I really don't want to side-track this plugin's support with something else.
  8. Here's the fix for the issues I've seen posted here so far, and have experienced personally. This runs just fine on PHP 5.x and 7.x, and Blesta 4.0. This requires some DB modifications and file changes so if you don't feel comfortable doing that you can either reach out to me for assistance or post here. The below is from a fresh install of the plugin. YMMV but I hope this at least helps bridge the gap between those who can and can't upgrade Blesta over a plugin. * When creating ticket, says ticket was created but no ticket actually shows * No tickets also show in admin panel * No ticket # is generated ERROR: ERROR 1364 (HY000): Field 'name' doesn't have a default value The same error occurred for the other 3 columns as well. CAUSE: The INSERT SQL is not using these columns, but they are marked as NOT NULL in the db, which is blocking the SQL from executing successfully. FIX: alter table support_ticketspro modify name varchar(255) null; alter table support_ticketspro modify reading varchar(255) null; alter table support_ticketspro modify readed varchar(255) null; alter table support_ticketspro modify cfields varchar(255) null; * Badge not rendering CAUSE: On the initial load of pages with the tab, there's validation to ensure that the user is a client or staff, where as the $this->{type} property does not exist. Which is causing PHP to throw an error. An alternative fix is to have property_exists($this, {type}) before the $this->{type} but seeing as how everyone is wanting to move to 4.x I decided to ignore that solution. FIX: Edit file support_managerpro_plugin.php Line 1209: remove "&& $this->staff" (property does not exist anymore on class) Line 1233: remove "&& $this->client" (property does not exist anymore on class) * Enabling this causes extra padding at top of page due to jQuery to get the ticket count due to response being full HTML page instead of expected single line, so instead of just rendering the badge data it's rendering a full HTML page CAUSE: I'm not really sure what the cause is here. It's basically an HTML page without any real content, but it was breaking the design. But, since this was an Ajax call being made anyways I don't know why the original author just did not go this route to begin with. The method has existed since Blesta 3.x FIX: Edit file support_managerpro_plugin.php Line 1218: change newRowCount.trim() to newRowCount.content.trim() Line 1223: repeat change above Line 1242: repeat change above Line 1247: repeat change above Edit file controllers/admin_tickets_count.php At end of index() method add this: return $this->renderAjaxWidgetIfAsync(true); Edit file controllers/client_tickets_count.php At end of index() method add this: return $this->renderAjaxWidgetIfAsync(true);
  9. I'm a little confused as to what is being asked here. So, correct me if I'm wrong. If a payment is being made on an invoice, and it is <= invoice amount, then set applied date to the current date If a payment is being made on an invoice, and it is > invoice amount, then don't set the applied date You also mention credit, so would the apply date in scenario #2 only be set on the credit amount?
  10. Pushed up a fix so you go to http://<ip>/ instead of /blesta now.
  11. There's 3 images on the Docker Hub for Blesta, 2 of which were invalid for me and another that ran in PHP 7 and seemed to come with the kitchen sink. That didn't sit well with me so I decided to create a bare bones instance of Blesta that also passes all required and recommended set ups. The end result is here: https://hub.docker.com/r/velaware/docker-php-blesta/ It does assume some knowledge of Docker (i.e.: how to find the IP and image ID). But, overall, it will get you up and running. This currently comes pre-packaged with 4.0.0 ready to install, but will be improving on this soon. Changing this isn't that difficult. This is in the README.md file too (just go to the GitHub repo) but to access this for now you need to go to /blesta. This will be fixed soon.
  12. To be fair Blesta, from what I can gather, doesn't use stream wrappers anyways, thus the dependency on cURL on install. So, they won't benefit any from that regardless.
  13. Thanks for the clarification; didn't know those files were hotfixed every new release of some sort.
  14. Yeah but you don't have to plop the hotfix in every single time you upgrade, as long as app/app_controller.php and app/app_model.php isn't overwritten you're good once. Plus the hotfix is only for 5.5 (not 5.6 or 5.4), because with 5.5 ionCube had to do some different stuff. However the standard Blesta files will work up to 5.4 without having to worry about the hotfix.
  15. Actually only if the app_controller.php and app_model.php files are modified. Those are the only 2 files I know of in Blesta that are encoded and those are the only 2 in the hotfix folder. If those files aren't touched the encoding is going to stay the same after all.
  • Create New...