Jump to content

Paul

Blesta Developers
  • Posts

    6,726
  • Joined

  • Last visited

  • Days Won

    841

Posts posted by Paul

  1. Also, to add.. if you want to have /index.php/ in your URLs, it's usually sufficient to just delete the .htaccess file included with Blesta from your server. That would certainly be the fastest way to get things working if you don't want to mess with your Nginx config.

  2. 14 hours ago, ExonHost said:

    Any update on this?

    The only update I have is to say that we are adding a special feature to the core in 4.6 that will make the domain update possible in a future release. The feature we're adding in 4.6 is necessary to the foundation of the domain update, which can only come after it's completed. The feature is useful by itself also, and we'll release more information about it as we get closer to releasing 4.6.

  3. On 3/15/2019 at 11:34 PM, adamjedgar said:

    I would like to use blesta to provision Wordpress VPS instances.

    Is it possible for a blesta admininstrator (or even clients) to manually initiate external VPS updates/upgrades?

    I dont want wordpress vps clients having access to the backends of their machines. Having said that, I also dont want to have to manually log into the backend of each machine individually to perform updates and upgrades. It this possible from Blesta? 

    I believe you can do this through the Vultr module, have you installed the free trial and given it a try? If you want to sell WordPress VPS's through another provider, then you'll probably need to make some customizations.. a startup bash script with an OS image that will install on first boot could work.

  4. 21 minutes ago, sunrisepro said:

    So the cron path on my server changed because I upgraded the server to PHP 7.2. According to my server admins, cron jobs are running properly but 

    is

    
    /home/username/public_html/backstage/index.php cron

    correct? Or should it be something different for php 7.2? Or do I need to upgrade Blesta?

    Your cron should specify the full path to PHP, ie /usr/bin/php /home/username/public_html/backstage/index.php cron > /dev/null (etcwhatever is here)

    Check Settings > System > Automation to see the recommended command. Blesta attempts to locate your PHP and show the right thing. It may not be 100% accurate all the time, but it's a good place to start. If Apache is running PHP 7.2, then CLI should be also.

  5. How long has it been "stuck"? If it fails, Blesta should pick up and retry when the task runs next. Check Settings > Company > Automation to see if the task appears to still be running, when it last ran, and what the schedule is.

    If the task appears to be running but should have been completed, it may have crashed. Check your logs ../logs_blesta/ defined under Settings > System > General.

  6. 7 minutes ago, furioussnail said:

    By the way, how does Blesta handle CC and BCC?

    How do you mean? CC and BCC recipients receive a copy of the original email, so subject & body would necessarily be the same. If a ticket is sent to multiple recipients, then I think we'd generate each email separately and it wouldn't be a CC.

    The ticket hash provides necessary security and verification.. I forgot that I was composing this, and may have had more to say and got distracted. So, I'll leave it at this for now :P

  7. {ticket_hash_code} is designed in such a way that Blesta can use it to identify the proper ticket, without leaving room for someone to maliciously modify the code to reply with updates to tickets that belong to other customers. It's designed with security in mind.

    ticket.id and ticket.code have direct relationships with real tickets, particularly ticket.id which is auto incrementing. Someone who receives a ticket with an ID of 100 can be reasonably sure that the ticket with an ID of 99 has already been created just before this one and is probably still open, and that ticket ID 101 will follow.

  8. 10 minutes ago, coreyman said:

    So I checked php7.1-fpm configuration and it's running as www-data. Files inside logs_blesta are being created as the root user and as such php scripts running through php7.1-fpm can not access the files. This causes lots of issues such as password reset emails not going out, unable to change client product pricing etc. I set the sticky bit on logs_blesta hoping that would solve my www-data problem by preserving permissions in the directory but it doesn't, files still get created as root owner. Every day I am stuck going in and

    
    chown -R www-data:www-data logs_blesta

    so I can perform administrative actions.

    
    drwsr-xr-x 2 www-data www-data   4096 Mar  4 14:33 .

    Any ideas why files are being created as root and not www-data?

    Is your cron job running as root? Did you install as root? Cron should run as the same user as your web server runs as.

  9. Do you have a ticket open? When you updated from 4.5.0 to 4.5.1 did you apply the patch originally or the full version? There's nothing in the update that should cause the error you received, unless it was a coincidence and your license hadn't been validated in quite some time.

    When you updated to 4.5.0 was everything working fine? Did you run /admin/upgrade to upgrade the database? If it was working fine, and was upgraded properly, then applying the 4.5.1 update should be fine. However, you could pretty easily roll it back by re-uploading the 4.5.0 release, or restoring from backup. Does it work if you do that?

  10. Blesta provisions paid pending orders. This means that the order is approved and paid, then the cron provisions the service.

    • Whether the order is approved depends on your settings and any anti-fraud. Check Packages > Order Forms > Settings for anti-fraud options. Edit the order form to make sure "Require Manual Review and Approval of All Orders" is unchecked.
    • Make sure your cron is running, it provisions orders that are approved and paid.
  11. 10 hours ago, alexfufayev said:

    Hi,

    I would also like to join this thread as we need to CC several people.

    It would be very useful to have email field for few emails separated by commas or to create a company entity.

    Thanks,

    Alex.

    CC who for what exactly? For most, contacts work well, especially billing contacts who will receive billing related emails.

  12. Support > Staff, click to edit the Staff member and add a signature for them under "Settings". Whatever is added to the signature will be inserted automatically into the editor when the staff member goes to respond to a ticket. The signature can optionally be removed, but it'll appear automatically.

  13. 1 hour ago, Amit Kumar Mishra said:

    i was just thinking, if you would donate this to blesta, and may be replace blesta portal, or may be a clients choice to choose from portal or cms

    and then may be then even blesta devs would constantly contribute on this...

     

    what say?

    Not an option right now. People can download and install it. :blesta: 

×
×
  • Create New...