Jump to content

Paul

Blesta Developers
  • Posts

    6,719
  • Joined

  • Last visited

  • Days Won

    841

Posts posted by Paul

  1. 6 hours ago, ewebhosting said:

    Is it possible to import a list of domains and pricing from csv or similar? Maybe there is a way through SQL?

    Not currently, but the latest version of the Namesilo module (shipping with 4.10, or available on Github) has an import option to import and markup pricing based on your pricing with the registrar. It's likely more domain registrars will have this option in the future, after our domain update.

    It would be technically possible to write a simple script to find your TLDs in Blesta and update pricing from a CSV.

  2. What's the "Visibility" of your order form set to? Public is the default and is what most people will want to use. If it's "Client Only" and you are not authenticated as an existing client, then it will redirect. If that doesn't help, a screenshot of your order form configuration would be helpful, along with the settings tab (Packages > Order Forms > Settings tab)

    There was an issue, likely unrelated to the Standard template in 4.9.0, which was resolved in 4.9.1. If you are running 4.9.0 I would recommend updating to 4.9.1.

  3. 3 hours ago, SLIBINAS said:

    Hello, after Blesta upgrade, I already getting again this error. I tried to go system general settings, I got this error.

    My php.ini settings
    open_basedir = none

    Are you sure you modified the correct php.ini? You may have a different php.ini for CLI vs Apache. To check what the path is to your php.ini as used by your web server, create the following code and upload and access it in your browser.

    info.php

    <?php phpinfo(); ?>

    Access in your browser, then search the file for php.ini

  4. 14 hours ago, WinsomeHost said:

    Hello Sir,

    I was using blesta on members.winsonehost.com ( sub domain of winsomehost.com) on another server. For now, I want to use same licence of blesta for the same domain "winsomehost.com" at the location "winsomehost.com/clientarea" at another server with fresh installation.

    Please suggest me what I will have to do regarding it. fresh installation means nothing want to import from old installation.

     

    Best Regards,

    Arvind

     

     

    12 hours ago, domaingood said:

    Hello Arvind,
    Just need to go Blesta lisence panel and Click manage then Reissue License Click Reissue.

    Then you can install any domain as you want.

    domaingood is right, but it's worth noting that you can only have 1 installation active at a time unless you are going to buy another license. If you re-issue and install elsewhere, then the previous install will no longer work.

  5. 3 hours ago, Joseph H said:

    after uploading the files blesta goes blank. I got the above text by debugging blesta.

    From the docs, after you upload a new version of Blesta you must run /admin/upgrade in order to run any database migrations. The error you received indicates that either this was not done, or it did not complete successfully. So, if you did not run /admin/upgrade, then the white screen you got is expected. Please run /admin/upgrade to upgrade your database to the new release.

  6. 45 minutes ago, Joseph H said:

    I'm running Blesta 4.8 trying to update to Blesta 4.9.0 but i keep getting an error

    
    SQLSTATE[42S22]: Column not found: 1054 Unknown column 'plugin_events.enabled' in 'field list' on line 196 in /home/admin/domains/domain.com/public_html/vendors/minphp/db/src/PdoConnection.php

    PHP version 7.0

    Did you already run /admin/upgrade after uploading 4.9.0? The plugin_events.enabled column is added in Blesta 4.9, but it looks like you don't have it.

  7. If you have an SMTP server for your domain, you can use that. If not, services like Mailgun will work. You may want to update all your email templates under Settings > Company > Emails so that they are addresses @yourdomain.com whatever that is, rather than a subdomain. Blesta auto detects on install based on your domain, if it's a sub-domain then usually it must be updated.

    For importing emails into tickets, most use IMAP as the option for email handling. Piping will only work if your MX record goes to the same server you are running Blesta on and can create a forwarder to pipe email to an application (Blesta). IMAP and POP can check external mail servers and import mail from there.

  8. On 4/18/2020 at 2:53 AM, qba82 said:

    It is not so easy to create multiply paypal accounts, that why we could make blacklist of abusive users paypal accs, so they can't create more accounts. Regarding to IP, yes You can use other IP, but abusers often doesn't change them. It would also help in finding customer, that was seen on website monitoring like analytics or matomo.

    I'm not sure I understand what you're asking. CORE-3573 has been completed for 4.10, which allows for searching the reference_id column for transactions, which contains the PayPal payer's email address.

    But it sounds like you want the ability to ban users based on PayPal account or IP address? That sounds like a different feature entirely. You can make an official request at https://requests.blesta.com 

  9. On 4/18/2020 at 9:49 PM, HostPhoton said:

    @Jonathan Hey Jonathan, can you please help quick. So i followed the instructions. Went to components/modules/ in my directadmin file manager, and created folder called namesilo. I uploaded zip file into that folder and extracted it. Nothing shows up in settings, modules, available. The originals modules are there that came with Blesta installation, but no name silo. 
     

    You may not have unpacked it correctly. Check that you don't have a /components/modules/namesilo/namesilo/ directory. The contents of the namesilo directory from the zip file should be in /components/module/namesilo/

  10. 500 errors are generally server-side and can happen for any number of reasons, the most common being incorrectly installed ioncube loaders. If the .htaccess file is missing, you should re-upload it. You might consider re-uploading Blesta entirely (after making a backup) to make sure no other files are missing. Check the logs ../logs_blesta/ defined under Settings > System > General to see if there are any errors being logged. Also ensure that your log files are all owned by the same user and have write permissions. Your cron should run as the same user as Apache. If you are executing your cron using wget, GET, lynx, etc as a web request then it should be, but this is not the preferred way to execute the cron.

  11. 44 minutes ago, Jason said:

    I am trying to keep it from generating the invoices and sending out emails on the weekend, but then complete those tasks on Monday.
    I don't remember what version of Blesta is was, but it worked for several versions. I may have had to move where the line of code was located, but I was able to successful utilize the code through a couple of different releases/version. I believe the workaround was in place somewhere from around 2016 till 2018 or 2019 before it stopped working.

    I grabbed some of the code from a backup file I have from a previous version where I had used the code...

    
    	private function createRenewingServiceInvoices() {
    		
    if (date('N') >= 6) { $output = ""; } else {
    	
    		$this->uses(array("ClientGroups", "Coupons", "Invoices", "Services", "PackageOptions"));

    and of course I closed the if statement lower on down after the function was finished. It isn't pretty but it worked as expected.

    I also extended it to include Christmas as a day not to send invoices.

    
    $month = date('n');
    $day = date('j');
    if ((date('N') >= 6) || (strtotime(date('Y-12-25')) == strtotime(date('Y-m-d'))) ) { $output = ""; } else {

    The idea was to simply have it skip creating the invoice on those days, the following day it would see the invoices had not been created and voila it would create it as it was supposed to.

    As for why ... I observe Sunday as a day of rest for religious reasons, and didn't want the billing system sending out bills to my clients on that day. I am also primarily a web designer, so while I do host websites, having them only billed Monday through Friday lowers the amount of potential questions and emails on the weekend :-).

    I don't see a problem necessarily with your code, it's just checking if it's Saturday or Sunday (6 or 7), and not executing the code to generate invoices. Personally I would have made Sunday 1 and not Monday as Sunday is actually the first day of the week, but I digress. Maybe @Jono has something to add.

  12. 14 hours ago, Jason said:

    I am looking for a way to limit invoices to sending during weekdays. In older versions of Blesta I added a line or two of php to cron.php to check if the day of the week was Saturday or Sunday and if it was to simply skip creating the invoice.

    
    if ((date('N') >= 6) .....

    Since I upgraded a while back my code no longer works. I added it where I thought it should be, but it hasn't kept the system from sending invoices. So I am either adding it in the wrong spot, or Blesta no longer uses the cron.php file to determine if an invoice is sent. Any ideas how I could accomplish this?

    Thanks,
    --Jason

    What version of Blesta did you do that with? Are you trying to prevent the generation of invoice, or only email delivery? You edited the /app/controllers/cron.php file? Can you provide a snipped from the file showing your change and a few lines above/below?

    Out of curiosity, why no weekends?

  13. On 4/13/2020 at 2:25 PM, franksidebottom said:

    Hi, I am looking at returning to using Blesta, it has been some years since I last used it, can you please tell me if this module is still functional with the latest version of Blesta?

    I would guess that it works, but the best way to find out is to give it a try. If you need a trial key and already had one let me know via PM and I can get you one.

  14. 19 hours ago, Jake said:

    Now I feel really stupid.  I had spaces in the array keys.  This is fixed. Sorry to waste everyone's time

    Looks like you figured it out before anyone had a chance to look into it. :blesta: 

    Glad to hear it's working now!

  15. 5 hours ago, Jono said:

    Unfortunately this is stored in the transactions.reference_id field which is not currently included in the transactions search.

    Do you see any reason we shouldn't search those fields in a transaction search? I know we added the reference_id after the search was originally written, but it's a field we should probably be searching.

  16. On 4/11/2020 at 10:03 PM, S.H. said:

    Don't use from marketplace it is v1.8.4 that I think had some incompatibilities with newer versions of Blesta. I cannot recall specifically but I remember it not working properly. Use GitHub and download the latest code, which should be v1.8.5 at this time. Also the instructions are on the GitHub page.

    We recommend using this version, it will be shipping with Blesta 4.10 https://github.com/blesta/module-namesilo

  17. 2 hours ago, franksidebottom said:

    Hi, I am looking to return to using Blesta having spent some years away, is this logicboxes module still functional with the latest version of Blesta?

    Welcome back! I'm not aware of any issues with the module, the official Logicboxes module works fine and we didn't make any changes to the core that should have broken 3rd party modules.

×
×
  • Create New...