Jump to content

SSy

Members
  • Posts

    74
  • Joined

  • Last visited

Posts posted by SSy

  1. 1) I'm not sure why, but the minimum amount of time you can set the provisioning time for new accounts is 5 minutes. This poses an unnecessary issue as new clients will have to wait unnecessarily.

     

    How can I change this?

     

    2) Once a new account is created, and a user logs in, they see an unpaid invoice notification in their account until the account is provisioned. How do I change the text of that notification?

     

  2. So basically editing the portal using the second link you provided, I disabled the base redirect to "/" and that permits me to create as many custom pages as I want. 

     

    Just so I understand it - obviously as an engine of sorts Blesta comes with pre-created pages such as the product page, cart checkout, and client center. What other base systems exist within Blesta? I believe there is also a knowledgebase built in. 

  3. I apologize for creating so many replies regarding this, but it seems like such a simple, obvious, and easy thing and the fact that it is becoming a large issue is creating growing concern for me over the Blesta infrastructure.

     

    All I want to do is to be able to create a custom page. So, for example, I want to create an 'about us' page that has static content, but uses the header and footer as in structure.pdt in the template folder.

     

    I want to be able to specify what URL this page is shown on: myurl.com/about

     

    Can you please explain, step by step, how I can achieve this?

  4. Okay, regardless of all of that, I am trying to prevent index.php from constantly redirecting the URL back to / so I can basically create custom pages.

     

    So, for example, if I type in myurl.com/index.php it redirects to myurl.com/

     

    Where can i disable this so I can have more control?

  5. Thanks for that.

     

    I am now trying to just create a simple .htaccess rule so that the URLs are a bit prettier:

     

    For the url:

     

    /order/config/index/shared/?group_id=1&pricing_id=1

     

    which works fine, I am adding this to .htaccess:

     

    RewriteRule ^hosting$ /order/config/index/shared/?group_id=1&pricing_id=1

     

    However when I go to myurl.com/hosting it redirects to the homepage. I read elsewhere that this should work with Blesta - what is it that I am missing?

  6. Hi there - I'm working with Galinvelle and I'm finding what you're saying quite confusing.

     

    1) The cart page, for example - what is the URL for this on the front end on a base Blesta install?

     

    2) Forget static pages - let's talk about integral pages that are required for listing products and placing an order. How do I find out what these URLs are?

  7. Okay, thanks guys. So what it is is this - 

     

    When you create an account, the LVE Limits appear to be being set. However, for some reason, it is only showing up in the LVE manager via the Cloudlinux tab.

     

    In WHM, when you go to list accounts > click the plus sign on the account > modify account and scroll down to LVE settings, that remains blank, for some reason. Because it was blank, I assumed the LVE limits were not being set. But it seems they are via the LVE manager.

  8. You're not understanding - when it is provisioned from within WHM, everything gets applied fine.

     

    When it is provisioned from Blesta or WHMCS, everything does not get applied fine.

     

    I originally thought this may be a WHMCS problem, but now think it must have something to do with the WHM api failing to apply extensions to accounts when packages are attached to accounts via the API.

     

    So what this means is that creating an account from within WHM and applying a package somehow runs additional functionalities that the API is missing.

  9. THanks, I'll test that out.

     

    No, I have confirmed with WHMCS support that for some strange reason, when a WHM package is attached to a new client via WHMCS, the LVE restrictions do not get applied as well. Neither do the package permissions, such as CGI.

     

    It's extremely strange and buggy.

     

    Even the fact that WHMCS does not have a paypal custom style page field is kind of what broke the camel's back for me. It's literally one field that should have been added to the paypal module years ago, and because it's closed source there's absolutely no way to hack it.

     

    Who knows what other strange and odd mechanisms exist that no one talks about. The fact that cageFS limits are not auto-applied when a new account is created, and this is now a known and accepted fact, and no one talks about it, is extremely strange to me.

  10. I'm a coder and the closed source aspect of WHMCS has proven to be a serious drawback for me. I've encountered bugs that have taken days to resolve with them and it has become a taxing situation that I am seeking to avoid in the future.

     

    I've only recently begun researching Blesta and will begin with one simple question:

     

    I'm running WHM + cPanel on a Cloudlinux server with cageFS installed. Right now, when an account is created via WHMCS, two issues arise that are currently unresolved by WHMCS:

     

    1) The order remains in pending until I manually activate it (no option to auto-activate)

    2) The corresponding WHM package that is applied to this client is only half-applied; cageFS limits are not applied via the LVE extension and we have to manually re-apply the package to have the limits applied.

     

    Are these two bugs something that Blesta has covered? As in, can orders be auto-activated (I'm assuming yes since this is such an obvious functionality). How about the LVE limits?

     

    Thanks.

×
×
  • Create New...