Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/12/2015 in all areas

  1. Kangaroo

    Im A Human

    hi all, After ticking the box "Im a Human" on order forms. I am not able to see "im a Human". Am I not human ?
    1 point
  2. Hello Blestars UPDATED 25-07-2014 Fixed: bug found by user lodoit that images were not being loaded wen blesta in on a sub-directory. New Order Forms added: Wizard Clean Curve Just see the instruction below, how to download and install. This Order Forms are for any buisnesses Wizard Clean Curve Order Form (now 100% responsive) How to Install/Upgrade: 1º- Download the Clean Order Forms: Download Here (updated 25-07-2014) 2º- Uncompress, and upload the folder "clean" to your blesta instalation in /plugins/order/views/templates/ directory. 3º- Go to Blesta Admin, and click on Packages->Order Forms, now Add an Order Form or Edit your Order Form and you will see the new Order Forms, just select, and save. 4º- Now give it a trie If you like it, and want to donate, please use this PayPal link: Donate Here! Any bugs, or problems please tell us. We hope you like it Regards, PV
    1 point
  3. Paul

    Invoices Not Sending Out

    Some need to use /usr/local/bin/php on cPanel. You can always run the cron manually under Settings > System > Automation. If it runs fine there, then the cron may not be correct.
    1 point
  4. Kangaroo

    Im A Human

    Does this areuahuman suppose to work for support ticket forms ? or just order forms ?
    1 point
  5. Today I started developing our custom code for Blesta, because we're coming from WHMCS where we created much custom code for. Now, I see this "bad" (when I compare it to WHMCS) domain management, I can't continue to switch to Blesta because of this. I hope a better domain management will being implemented in the near future. I don't think you'll need to do this per module, which will get very messy over time (all different way's of handling things). My ideas for the domain management, which you may consider while implementing this: - Centralized WHOIS information over multiple registries, with ability to "override" this for a specific domain by the customer. - Centralized nameservers over multiple registries, with ability to "override" this for a specific domain by the customer. - Proper transfer handling (including a cron). - TLD syncing with automated price updates - WHOIS through the preferred registry for a TLD - Some TLD's have different requirements (e.g. a domain needs to be renewed x days before expiry). Thanks!
    1 point
  6. I think this will be easier once the marketplace is available, where developers can list each of them for download.
    1 point
  7. I've worked with him fixing a module. He is good, I personally trust his abilities.
    1 point
  8. They did pay for it. The cron job was not running, but just now I run it manually and the package was changed. It's 3.5. Thanks a lot for reminding the cron job.
    1 point
  9. The main reason I want to use this is for the bubbles and merging abilities. But I have a hard time trusting 3rd-party scripts from individuals. When the author loses interest, then we're screwed, as updates that break it are always going to happen. I've been there dozens of times over the years. I wish this mod simply added features to the existing support system, and not replaced it altogether. Better yet, I wish that the Blesta would just integrate these things into the core. The biggest item is the ability to import/export between the two support systems.
    1 point
  10. Cody

    Support Manager Last Reply

    Excellent. Closing this as fixed for 3.0.4 (CORE-781).
    1 point
  11. Please post 1 feature request per thread, and include as much information about the feature as possible. Having 1 feature request per thread allows the thread to focus entirely on that feature. One of our goals is to gauge community interest in a particular feature, which helps us prioritize the feature if we decide to add it. If we do add the feature to our project management system, we will usually post a task ID associated with it. The feature can then be tracked in the thread to completion. Posting multiple feature requests in a single thread waters down the request, and it will usually receive fewer responses. So, sticking to 1 request per thread increases the odds of it being implemented!
    1 point
×
×
  • Create New...