Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/11/2014 in all areas

  1. You can get the http request and compre with: WEBDIR.Configure::get("Route.admin") If its true than you are on admin You cam also use: if ($params['portal'] == "admin")
    2 points
  2. Tyson

    Simple Plugin Needed

    I think it is a request for a simple 'hello world' plugin.
    2 points
  3. Ah, so a special price override specific to a client and package term combination. That makes more sense, but does add to the complexity of package pricing and management.
    2 points
  4. updated the css code . - added the support for navigation link - added the support for close button in models and messages . - added the support for right checkbox and radio inputs .
    2 points
  5. UPDATED 09-05-2018 - Add an extra option on Suport Manager Pro in Plugin manager to showw All Companies Tickets. By default only shows the selected Companie Ticket, you can change it now to show all. Thanks to WebhostingNZ.com (not testes 100% because we dont have MultiCompany to test it ) - Optimised code. Removed some CSS and Javascript that was duplicated has latest Blesta alredy include in CORE - Some minor changes in Ticket Replay on Admin side to better display Notes, Replies, Logs UPDATED 15-03-2018 - Merged all Support Manager 2.12.0 Core compatible with latest PHP 7.0/7.1 - Fixed all issues found by blestares ( ) using on PHP 7.0 / 7.1 Note: Have to clean more code but is almost 95% clean now mostly change array into [ ] and " " into ' ' I have made alot of testing, but maybe I have miss something. If you found any bugs please tell me to start adding new features New Screen SHots 2016 (I will update the screen shots late this weekend to 2018 ones ) Added: GitHub repository to check, help, and download: https://github.com/qlpqlp/Blesta (have to update to 2018 code) BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! BEFORE ANY INSTALATION OR UPGRADE BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! How to Install (Only for Support Manager Pro and Blesta 4.2.2 or Above)? If you want all functionality of the "Support Manager Pro" and atthe same time have "Support Manager" original, just do: 1º- Download the full Suport Manager Pro Plugin here -> Download Support Manager Pro Plugin (updated 15-03-2018) 2º- Uncompress, and upload the folder "support_managerpro" to blesta /plugins/ directory. 3º- Go to Blesta Admin, and click on Setings->Company->Plugins->Available and it will list the "Support Manager Pro" plugin, just Click on "INSTALL" 4º- Now you will see on new menu item called "Support Pro". Now you have to configure everything like the original Support Manager. ==================================================================================================== BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! BEFORE ANY INSTALATION OR UPGRADE BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! - BACKUP!! ==================================================================================================== How to Upgrade (Only for Support Manager Pro and Blesta 4.2.2 or Above)? If you want all functionality of the "Support Manager Pro" and atthe same time have "Support Manager" original, just do: 1º- Download the full Suport Manager Pro Plugin here -> Download Support Manager Pro Plugin (updated 15-03-2018) 2º- Uncompress, and upload the folder "support_managerpro" to blesta /plugins/ directory. 3º- Go to Blesta Admin, and click on Setings->Company->Plugins and it will list the "Support Manager Pro" plugin, just Click on "UPGRADE" ==================================================================================================== 27-02-2014: A special thanks to CubicWebs for helping in the css marktup 13-03-2014: A special thanks to @cloudrck for helping in detecting a bug 15-03-2018: A special thanks to @velaware for helping in detecting a bug Any bugs or sugestions, tell us. We hope you like it Regards, PV
    1 point
  6. Hello All . we bring exclusive content , this time is the Announcement plugin . A very clean and simple Announcement plugin for Blesta , allows you to post announcements , and make them , Publicly for all or based on clients groups and service's packages. the plugin can : add/edit/delete Announcement. List All Announcements Restriced Announcement based on client Group And packages . Show widget announcement in client side . Option to enable/disable widget in client side. Setting to show announcement in full or mixed views. Set how much announcement should be displayed in widget client TODO LIST : - show widget announcement in client side . Done - option to enable/disable widget in client side Done - set how much announcement should be displayed in widget client Done - allow share buttons or announcement - allow client to ignore announcement message . - hide announcement in widget after X days . - Add RSS announcements (just the public announcements) - add setting to show announcement in full or mixed views Done Some screenshoot : Admin Side : Client Side : client widget : This Plugin is tested in our test server , no bugs at the moment , in this weekend we will add support for client widget . as always the installtion steps is : 1 - download the file http://blesta-addons.com/plugin/store/main/item/22/ 2 - upload the announcements folder inside plugin directory . 3 - goto plugins , and install Announcements Plugin . 4 - enjoy the free content . If anyone wants to have it on their portal you can use this code: (thanks to @Licensecart) {% if plugins.announcements %}<div class="col-md-4 col-sm-6 portal-box"> <a href="{client_url}plugin/announcements/client_main/"> <div class="well"> <i class="fa fa-info fa-4x"></i> <h4>Announcements</h4> <p>You can see all the latest news here.</p> </div> </a> </div>{% endif %} It will only show up if the module is installed. This plugin require Basic (Bronze) subscription
    1 point
  7. to fully support rtl-to-lft alignement , replcae the rtl.css content with this new content the file is located in app/views/clients/bootsrap/css . i hope this can be added to the core file for next release . /**** RTL BOOTSRAP ***/ body { direction: rtl; } th { text-align: right; } .col-xs-1, .col-xs-2, .col-xs-3, .col-xs-4, .col-xs-5, .col-xs-6, .col-xs-7, .col-xs-8, .col-xs-9, .col-xs-10, .col-xs-11, .col-xs-12 { float: right; } .nav { padding-right: 0; margin-bottom: 0; list-style: none; } .pull-left{ float: right !important; } .pull-right { float: left !important; } .text-left { text-align: right; } .text-right { text-align: left; } .dropdown-menu { float: right; text-align: right; } .dropdown-menu-right { right: auto; left: 0; } .nav-tabs > li { float: right; margin-bottom: -1px; } .pagination li { padding-left : auto; padding-right: 0 ; } .radio, .checkbox{ padding-left : auto; padding-right: 20px ; } .radio input[type=radio], .radio-inline input[type=radio], .checkbox input[type=checkbox], .checkbox-inline input[type=checkbox]{ float: right; margin-left : auto; margin-right: -20px ; } .close{ float: left; } .list-group-item > .badge { float: left; } @media (min-width: 768px) { .col-sm-1, .col-sm-2, .col-sm-3, .col-sm-4, .col-sm-5, .col-sm-6, .col-sm-7, .col-sm-8, .col-sm-9, .col-sm-10, .col-sm-11, .col-sm-12 { float: right; } .navbar-nav { float: right; margin: 0; } .navbar-nav > li { float: right; } .navbar-right .dropdown-menu { right: auto; left: 0; } .navbar-right .dropdown-menu-left { right: 0; left: auto; } .navbar-nav.navbar-right:last-child { ; } .navbar-left { float: right !important; } .navbar-right { float: left !important; } } @media (min-width: 992px) { .col-md-1, .col-md-2, .col-md-3, .col-md-4, .col-md-5, .col-md-6, .col-md-7, .col-md-8, .col-md-9, .col-md-10, .col-md-11, .col-md-12 { float: right; } } @media (min-width: 1200px) { .col-lg-1, .col-lg-2, .col-lg-3, .col-lg-4, .col-lg-5, .col-lg-6, .col-lg-7, .col-lg-8, .col-lg-9, .col-lg-10, .col-lg-11, .col-lg-12 { float: right; } .col-xs-1, .col-xs-2, .col-xs-3, .col-xs-4, .col-xs-5, .col-xs-6, .col-xs-7, .col-xs-8, .col-xs-9, .col-xs-10, .col-xs-11, .col-xs-12 { float: right; } } /*** RTL STYLE ***/ .header { float: right; } .header .container { padding-right: 0; padding-left: auto; } .logo { float: right; margin: 13px 0 3px 15px; } .title { float: right; } .title .container { padding-right: 0; padding-left: auto; } .nav-content .container { padding-right: 5px; padding-left: auto; } .table-curved tbody > tr > td { border-right: 1px solid transparent; } .table-curved td, .table-curved th { border-right: 1px solid #e1e1e1; border-top: 1px solid #e1e1e1; } .table-curved tbody>tr>td:last-child { border-left: 1px solid #e1e1e1; } .table-curved tbody>tr>td:last-child { border-left: 1px solid #e1e1e1; } .table-curved tbody>tr>td:first-child { border-left: none; } .table-curved th:first-child { border-radius: 0; } div.panel-body div.alert { clear: both; } .col-border { border-right: 1px solid #efefef; border-left: 0px ; } /* Loading */ .loading_container { left: auto; right:0; } /* Order Page */ .well-order .total-due { text-align: left; }
    1 point
  8. For one reason or another, we do get a lot of requests to go ahead and generate the next renewal invoice for a service early. The ability to forcibly generate these from an admin standpoint would be excellent!
    1 point
  9. Hello the Override Price feature is very helpfull , but why not a Override Price per package , as the actual sceanario we can Override Price per service . the case : you have a reseller or potential user , every time he order a service A , we need to Override Price per every service order . if we can Override Price per package, we don't need to change the price every new order . i hope it has sense for other . EDIT : just to note make them a custom or restriced package is not usefful , as we need to list all the package in the order form .
    1 point
  10. i need to check this out side the event , in a model file , and the model is not supporting some good function in controller.php . the actual workarround is the url filter like you have posted . but i prefer if thier is any easy way than that .
    1 point
  11. You can try my workaround to this issue at using Universal Module for dedicated servers for instance (you need to let the user know what's their IP address, assigned after the order is done) [blesta 3.2.1] Universal Module Workaround: Show Service Fields At Client Panel [blesta 3.2.1/3.3] Universal Module Workaround 2: Hide Certain Service Fields From Being Shown On Order Page Both should work with blesta 3.3
    1 point
  12. Service meta data (service_fields table values) can be encrypted with AES256. The module controls this, and an example is the cPanel module, which encrypts cPanel passwords. I believe module row data can also be encrypted, but Cody or Tyson will need to confirm.
    1 point
  13. Yeah, just noticed that haha...... all good!
    1 point
  14. Nope no issues, you can use the Https override in the .htaccess provided with Blesta, just remove the #.
    1 point
  15. Sounds like they didn't install Mailparse on the server, or it's not loaded in php. Have you checked phpinfo? After you're able to get passed that requirement, there's some more configuration info available in the email piping docs.
    1 point
  16. +1 I'd like to add that I think clients should be able to renew any recurring service at any time on demand from their portal. Upon payment, the system would then send them an invoice marked paid, and the service term would be extended by the selected amount from their current renewal date. For those that need a bit more control over renewals, perhaps provide a new setting in the package to allow/disallow customers from renewing until they receive the renewal invoice. In other words, the ability to toggle each package between the current Blesta behavior and this new proposal.
    1 point
  17. upload the support manager plugin from clean blesta source , and try again . also make sure you have set the correct path in blesta settings .
    1 point
  18. you are meaning callback ? normally it should /callback/gw/1/your_gate_way/?client_id=xxxx
    1 point
  19. It is worth it, otherwise you have to wait every 5 minutes when the cron runs mate.
    1 point
  20. so ; for me that is not a bridge . is integration via API . it was better to make it as plugin for wordpress . Bridge = if(logged_in_wordpress ? logged_in_blesta : null); this plugin has this function https://wordpress.org/plugins/blesta-shared-login/ . i prefer if you can do it as a plugin fro ordpress , that way is better .
    1 point
  21. Yeah you're right, it would be better for usability if the payment account nav link did not appear if both payment types were disabled. It's definitely my preference, but there may be some current limitations to that in terms of how the navigation is created. I'll discuss with the team.
    1 point
  22. Payment accounts are for merchant gateways only. In the case of PayPal and other non-merchant gateways, there is nothing for Blesta to store. If you want to disable credit card, or ach options you can do so under Settings > Company > Billing/Payment > Accepted Payment Types. If you disable both credit card and ACH, then payment accounts will be disabled. If you only accept non-merchant gateways like PayPal, you may wish to do this.
    1 point
×
×
  • Create New...