Jump to content

Paul

Blesta Developers
  • Posts

    6,728
  • Joined

  • Last visited

  • Days Won

    841

Posts posted by Paul

  1. This fix will also be in v3.0.4. In addition, the Plesk module will now refuse to attempt to delete any subscription, customer, or reseller if filter options are missing, so as to avoid Plesk's interpretation of "delete everything".

     

    I think what Tyson did here he did after posting the hotfix above. If I'm right, the issue you experienced with changing the renewal date is already corrected it's just not in the file you downloaded. Tyson, can you confirm? I can post a new file for testing if that's the case.

  2. But where do I go to uncheck the "Use Module to add" button? I see I can do it when I try to add a service to a client, but I cant seem to do it once its added. When I go to edit the service by clicking on the "Active" link, its not an option in the settings.

     

    This is only necessary when you add the service as an admin to a client's profile. If you cancel, suspend, or edit the service through the "Active" link you will see a "Use Module" check box. Uncheck this box when performing an operation to prevent it from calling the module. You want to uncheck this whenever you don't want what you're doing to make an API call to your WHM server and affect the cPanel account there.

     

    So, I now have two duplicate services for my first client instead of one. But now I'm a little concerned that, as I can't seem to check the status of the "Use Module to add" setting, if I try and delete one of these services it may delete the hosting account back in WHM. Is that right?

     

    For the duplicate, click the "Active" link and cancel it, but uncheck the "Use Module" box when doing so.

     

    Moving forward, I plan to only add a cPanel hosting account to Blesta that's already set up in WHM.

     

    If adding it to Blesta when it already exists in WHM, just make sure to uncheck the "Use Module" option when adding. If you want to link it to your WHM server for account suspensions if they don't pay on time, then click the Active link, and input the actual username in the username section and uncheck the "Use Module" option and save.

     

    thanks for your help guys.

     

    You are very welcome!

  3. Check your email templates, it may be that it's using https:// for the link in that email when you don't have SSL set up for the domain.

     

    Regarding the other error about connecting to the remote server for the module, uncheck the "use module" option to update Blesta without connecting to the cPanel server.

     

    If you add a cPanel hosting account to Blesta that's already set up, then you'll want to uncheck the "use module" option at that time as well. After it's added, click to Manage the service, and make sure the proper username is entered for the username field. This will link it to the server so suspensions and unsuspensions can happen automatically.

     

    If you try to remove the service from Blesta and don't want it to delete in on your WHM server, always be sure to uncheck the "use module" option.

  4. I believe they are for the backend when your recording payments, I use them when doing Manual payments when my PayPal IPN broke.

     

    So you can add Bank Transfer and then click Record Payment and select one of the Payment Types.

     

    That's correct. Custom payment types.

  5. We don't make the pricing public. Did you email from the same address you signed up from the forums with? Do you currently have a Blesta license?

     

    VAR accounts are unlimited licenses on servers you own or operate for a flat monthly fee. Most customers are better suited for the standard reseller plan, which has a much lower commitment.

  6. It did mate, but I think it was a one off thing. not 100% sure.

     

    Not happening anymore?

     

    I remember before you said you had 2 windows open logged into each company watching the ticket queues and it worked great. For me, it looks like the other company but it loads the ticket queue for the last company you switch to. This can give the appearance that it's the ticket queue for company A, but it's actually the ticket queue for company B.

    Make sense? I just wonder if that's what's happening here.

  7. Like a redundant package mate?

     

    Yeah, this would be pricing in a single package. Duplicate terms with different prices.

     

    I'm not sure it will solve anything in Dave's case, but I thought I'd throw that out there since this functionality is probably not common knowledge.

  8. 1) Should the  phrase cron job must be created 

    really be cron tab entry must be added

     

    A cron job and a cron tab are pretty interchangeable, I think.

     

    2) Please have the command box be widened so the entire entry is visible.

     

    I agree, assigned to CORE-791 - thanks!

     

    3) When viewing MY SITE's automation page,

    It is unclear (to me) if I needed to update the cron key and what I would be doing with it.

    Perhaps a little more explanation could me added.

    (It is somewhat clarified reading the "running the cron via the web info box of the install+Blesta)

    +++Pease remove my comment about this at

    http://tutorials.blesta.com/video/62845736

     

    I'll see what we can do about that, there is definitely room for improvement here.

     

    4) After clicking "Run Cron Manually" ( more exact would be "run cron job manually" 

    much output scrolls ending with "All system tasks have been completed." (successfully ?)

    however "the cron (job) has never been run" is still displayed.

     

    Not sure why that is, your web server isn't doing any caching is it? Can anyone reproduce?

     

    5) Please add timezone to "the cron(job) last ran on ..."

     
    6a) Forcing HTTPS: Lines stated to be commented out in .htaccess don't seem to be there.
    6b)I don't know why I would want to force HTTPS.
     
    Forcing HTTPS was actually added to 3.1. We need to split the documentation for 3.0 and 3.1, and will be doing that shortly. Often times we have people asking how they can force HTTPS for their Blesta installation. It's a good idea to use SSL whenever possible, especially when personal and financial information may be at risk. Since not all servers have SSL, we added the rule and commented it out so that it can easily be enabled.
     
    NOW THE BIGGIE: What do I do next?
    Maybe all that is needed is a link to important+Settings
     
    If your cron job is set up and running, then installation is complete. I suggest checking out common tasks in the manual http://docs.blesta.com/display/user/Common+Tasks for what to do next. This forum is also a great place to ask for help!
     
    Thank you for your suggestions!
  9. You can set up a package with multiple price options for the same term.. for example..

     

    Package A

     

    1 Month $89.99

    1 Month $99.99

    1 Month $79.99

     

    Then just select the appropriate price point for the legacy package. This wouldn't make sense if offering it for order, since the customer would simply select the cheapest option, but for legacy services it might help with what you are trying to do and reduce the number of package permutations that are required.

  10. Thanks for the suggestion. Do you think this could be accomplished by using conditionals in the welcome email template now?

     

    It's likely we will add the ability to create custom email templates in the system in the future, and a method by which they can be utilized by the core, manually, or by other extensions.

  11. What about when I exported my Blesta 3 passwords. Are these MD5 or as Tyson said simply a case of me changing a system key so that the 3.0 export works on a new import.

     

    Is this value stored in the database anywhere so I can see what it was on the old installation?

     

    If you originally imported from 2.5, the passwords as stored in Blesta 3 will be the same MD5 hashes unless/until the user logs in and the password is updated. If you look at the users table, password field, it should be pretty obvious which passwords are MD5 and which are not. MD5 passwords are 16 byte, and will appear shorter than new passwords.

  12. Is there any way similar "price override" functionality could be brought into the import routine, or even into Blesta itself?  I'm sure I can dig in and edit the SQL data by hand, but this opens up a giant can of worms that I'd just as soon stay away from.  I'm sure I won't be the only one in this situation.

     

    A service price override option is assigned to CORE-747 and tentatively scheduled for 3.3. We might be able to bump it to 3.2, but even then it's still a little ways out.

     

    I wonder if you're able to use recurring coupons to get the pricing the way you want, though it may be simpler to use legacy packages.

×
×
  • Create New...