Jump to content

evolvewh

Members
  • Posts

    1,007
  • Joined

  • Last visited

  • Days Won

    9

Posts posted by evolvewh

  1. 2 hours ago, Web Hosting UK said:

    Interesting debate. I'd rather wait for the domain manager rather than having a buggy release with endless issues. W....S also has an advantage as it came out before Blesta.

    I've no doubt that the domain manager will possibly be added in one of next major releases.... 5.0 maybe?

    I hope you're right and hopefully v5.0 isn't still  a year away. Since we moved back, I haven't found any major issues that didn't have solutions provided. Maybe we're not using it to the extent you did. Not sure.

  2. 20 minutes ago, coreyman said:

    Put your money where your mouth is. I'm sure you could hire any number of blesta developers that could finish this out for you and you wouldn't need to use WHMCS and could contribute the work to Blesta.

    To an extent we did and there comes a point where it's not cost effective to keep doing so. I'm not the best developer so I did what I could. We also contributed to CyanDark for the cPanel module that unfortunately didn't happen and patching customizations after every main release is very time consuming as well. We have no issue using WHMCS so I'm sorry if I sound like I'm complaining. I was trying to state why we left Blesta. That's all. Our business isn't to be developers so we've purchased another solution that has what we need to run our business. I support Open Source and it's awesome to give others the ability to write their own code and modify software. We are also the reason Blesta users have a plugin with SupportPal to integrate with their support ticket software. We sponsored that development with SupportPal.

  3. 2 hours ago, Blesta.Store said:

    Blesta 3.0.0 was fully re-written no 2.5 code was passed onto 3.0. WHMCS hasn't changed their base code since they started in 2005. They've just built on top of it which is why the 2013 localhost exploits effected EOL whmcs versions as-well as their current one at the time. https://web.archive.org/web/20131031051528/http://www.localhost.re:80/p/whmcs-528-vulnerability

    I get that and respect that. I really don't understand @Paul lack of updates on any of this. If it was high priority, I would think 'something' would have been released by now.

  4. 14 minutes ago, Blesta.Store said:

    Thanks, you're a great guy as-well and I do understand I have ran a webhosting business but I'd prefer security over features which is why I moved to Blesta back in 2013. I had mysql issues which is why I closed my webhost and provided the clients with discounts from my mates in the industry a month before the server was cut off because innoDB backups were screwed up before we found out we still had databases screwed up so I had no backups with Gigenet. That's when I went full time at Licensecart minus my part-time job at the time. I know what you are missing and I understand but they only have a team of 3 unlike the alternative which have been building on their software since 2005. 2005 base vs a 2013 base. Security holes which is now hidden by a bugcrowd vs a open code software which has no security holes so far.

    I understand the security concern which is always an important consideration. I also think by taking steps to properly harden the server, follow the recommended WHMCS security steps (moving the cron folder, config file permissions, etc) and even using a WAF and/or service like cWatch, many of these issues become non issues or minimal. Sure they cost a little bit extra but well worth it.

    Part of my last response is a push for @Tyson and @jono who need more help on the development side. It's sort of a case of 'spend money to make money' and advance the software faster. Quality control and bugs can still be monitored and caught through testing and different software applications available even when working with bigger teams. Blesta itself didn't start in 2013 either. I didn't use v2.x so I'm not sure when the company actually formed. Trust me, I didn't want to go through the process of manually moving (WHMCS importer doesn't work) but in our case, it had to be done.

  5. 28 minutes ago, Blesta.Store said:

    They can repeat themselves all the time I assume for you then :D "We're working on it"... or if you wan't a detailed version every time... "We've done the pricing table for the domain system" next time "did the form for the order form" or "did a function for the domain system" or "we're working on it still"...

    As an 'outsider' it looks like this is forgotten. It may not be internally but @Paul could really use it to it's advantage to build marketing hype. Release a teaser with a screenshot or something. It was originally slated for v4.1.0 which was released a year and a half ago. That's a long time. Sure they're releasing other things but there hasn't been that much that's major and to advertise this as the 'billing platform for hosting providers' is just false without better domain management. I can't even begin to list the number of issues I found as we migrated over and cleaned out the numerous domains that had been expired, transferred away, etc because everything has to be manually checked in Blesta on a daily basis right now. When a system allows customers to make changes 24/7, notifications to admins and automation throughout is a must.

    I get it that you don't sell domains and may never wish to but for those of us that do and our customers who wish to purchase from us, it's a nightmare. Try manually checking domain renewals on a daily basis and manually renewing whois protection on hundreds or thousands of domains. Not fun. Try manually notifying each customer of why a domain transfer is stalled instead of having it automated with an email saying the auth code is missing or incorrect or the domain is still locked. The embarrassment of sending a renewal invoice to your customer for a domain they let expire years ago or one they transferred away because it wasn't caught manually and deactivated in Blesta.

    I would have been happy to pay even more for Blesta to have these features in place already. 2 developers for a system with ambitions as high as Blesta's is brutal on them. These developers simply need more help! They're great at what they do and they deserve a lot of credit. Your days of saying 'Blesta just did an entire re write and they're working to catch up' aren't as relevant anymore. v3 was released on Aug 14, 2013 (almost 5 and a half years ago). You're a good guy @Blesta.Store but your comments about why things like this aren't implemented just don't make business sense anymore.

    I want Blesta to succeed and I'm just as excited and was just as supportive as the next guy for an alternative to WHMCS. That's what we used before and I took the time to transfer to Blesta on hopes of a much better system. It wasn't fun transferring back to WHMCS but it had to be done for our customer's sake. I get it we all have choices to go elsewhere and that's what we did. I didn't plan on saying this much but after reading the comments again in this thread, I felt I should add this.

  6. 5 hours ago, coreyman said:

    All of these systems are made to be customized. With that in mind, I would probably be interested in buying your license.

    Send me a message and make a reasonable offer.

    Totally understand it can be customized and we did a bit of that. Unfortunately, 'customizing' an entire domain management system isn't feasible for us.

  7. 2 hours ago, Blesta Addons said:

    are you leaving blesta ? why ?

    Yes, we left Blesta over the Summer and we left for many reasons but this one is the biggest:

    https://www.blesta.com/forums/index.php?/topic/7197-domain-manager-we-need-your-feedback-on-domains/&tab=comments#comment-45629

    Honestly, Paul's lack of any response to this just tells me that nothing is being done and we can't run our business with the answer 'we hope to have something available by the end of 2018'. We're there now and there's still no sign of this.

    I don't want to create a list that makes it look like we're bad mouthing the software or anything but there are many other features we need and we discovered others after making the switch. I believed in Blesta and wanted to stick with it but it ultimately comes down to useability for our clients and Blesta isn't quite there yet for our business. We'll keep an eye on the progress and if it gets where we need it to be, we'll move back.

    There are a lot of things to appreciate with Blesta too and depending on your company and needs, it's a great piece of software. I am in no way saying WHMCS is superior or anything like that. It just has the hosting features that we need for our clients. I feel we gave Blesta a fair shot by sticking with it for over 3 years.

  8. We're going to sell our owned, unbranded lifetime license and have no clue of what it's worth. Any suggestions? This license doesn't have active updates (buyer will need to add that). I'm just exploring now to see what it's worth and once it's time to sell, I'll make sure Blesta verifies the license and whatever else needs to be done for a smooth sale. This was purchased directly from Blesta prior to the v3 release.

  9. It's already setup so there is a credit added to the customers account after you record the payment and once it's applied to an invoice, it says the original payment method and amount applied to it.

  10. 14 hours ago, Tyson said:

    Oh, so you had changed the location of your Blesta installation a while back? I can see why Blesta never receives the IPN then.

    It's unfortunate that PayPal does not allow you to update existing subscriptions to change the IPN URL.. are you able to have the old URL forward to the new URL? By default, the URL should be https://domain.com/PATH_TO_BLESTA/callback/gw/COMPANY_ID/paypal_payments_standard/ where PATH_TO_BLESTA is your Blesta web directory and COMPANY_ID is your company ID. GET and POST data will need to be passed along.

    I created a redirect in the .htaccess file and it should work. I'll have to wait until the next recurring payment comes in to confirm. This fixed the issue. Thanks for your help with this.

  11. Response from Paypal in case anyone else runs into this issue:

    I apologize for the frustration. When a Subscription is created the Instant Payment Notification URL that is on file or the notify_url that is sent in with the payment request is the notification URL that is used for the life of the Subscription.
     
    Here are the options to resolve this issue:
     
    You can see if your Web Developer can setup a forwarder from the incorrect Notify URL to the Correct Notify URL.
     
    The other option is to create new subscriptions and cancel the old subscriptions, which isn't the best option.
     
    I confirmed with the PayPal Product Developers that the IPN Notify URL gets setup in the batch server when the Subscription is created, so it cannot be changed on the subscription.
  12. So far, it looks like Paypal attaches the callback URL to the Recurring profile so if you change that URL under the settings page (in your Paypal account) it does not reflect on any of the recurring profiles. We changed the URL to our billing portal about 4-5 months ago. That explains why it works for 1 time payments and not for recurring payments. Still working with them to figure out how to update this because i don't see a place within our account to do so unless we were to cancel all recurring profiles and set them up again.

     

  13. On 6/25/2018 at 10:33 AM, Tyson said:

    You may want to check with your PayPal account to be sure that the IPN request is set up to be made for the recurring payment. Sometimes, particularly if the IPN request had continuously failed, PayPal will disable it and no longer send IPN requests. It might be referencing the wrong URL (for example, if you moved your Blesta installation to a new location), or if the server hosting Blesta does not support TLS 1.2, PayPal will not be able to negotiate a handshake with the server in attempt to send the IPN. The latter doesn't seem like the issue since you receive manual payments, but still worth double-checking. If either of those is the problem, you'll need to resolve them first and then re-enable the recurring IPN in PayPal.

    Sorry for the delay and thank you for the additional info. I've got a ticket open with Merchant Technical Support right now and I'm waiting to hear back from them. I'll update once I hear back from them.

  14. 1 hour ago, Paul said:

    I'm not sure what you mean by the main package page.. do you mean the admin area packages, or the order form?

    As of 4.3, package groups can be sorted on the order form, and packages have always been able to be sorted in their groups, so the display order is now fully configurable on order forms. If you mean the display in the admin area, right now they are just sorted by newest package, though the Packages > Package Groups page will display packages in their sort order. There are some improvements we can make here in the future.

    Packages > Browse Packages is the page I'm referring to.

  15. 9 hours ago, alexistdev said:

    how to insert value for type "select" form input? i've made for datacenter location like this:

    datacen.png

    but its wont appears on member client form order.

    datacen2.png

     

    But when i input only 1 value( SG:Singapore) , its shown.

    Hover your mouse over this tool tip and you'll see the format needed (shown in attached image)

    Screen Shot 2018-06-17 at 7.13.40 AM.png

  16. If a client does not have a 'set package' and they go to order through the portal, the restricted group is still shown to them. This happens as soon as you click the 'order' link in the client nav bar. If a client continues further by clicking that group and then clicking 'skip, order other items', the group finally goes away. IMO, this group should never show when the client clicks 'order' initially.

     

    Also a client who is authorized to order a restricted package, still can't order it through the portal. Ignore this. I was thrown off because they are sent to the domain lookup field first. 

     

×
×
  • Create New...