Jump to content

Paul

Blesta Developers
  • Posts

    6,726
  • Joined

  • Last visited

  • Days Won

    841

Posts posted by Paul

  1. 13 hours ago, kikloo said:

    Clientexec is also available at same price. No wonder belsta has blocked their importer script in htaccess file.

    FYI we blocked it because it allows data from Blesta to be PUBLICLY available to anyone who visits the URL. It's a security risk. If that's the kind of company that you want to work with, that puts your data at risk and could care less about security, I don't know what to say.

  2. We've sped up development dramatically. Blesta is used by more companies than ever before. "Just create modules" isn't helpful feedback, though we have created a lot of modules over the past 2 years. We add modules that a decent number of people request and will use. We don't arbitrarily create modules that have no demand, that would be a waste of our development resources. I don't recall having a conversation with you or anyone recently about CCAvenue (if it requires mcrypt, just install mcrypt) or internetbs.

    Pretty unhelpful thread. </thread>

  3. Glad to hear that worked! I'm not sure why /app/views/admin/default/ would have fixed it though, since that's the admin templates and the order form is generated with a combination of client templates and order form templates (/app/views/client/bootstrap/, and /plugins/order/views/templates/)

    Either way, it looks much better now :blesta:

  4. 14 minutes ago, mezoology said:

    I didnt modify any file. so if i re-uploaded some file. which file i shouldn't re-upload to avoid re-issuing the license. its internal license with my host.

    To be safe, I would recommend re-uploading all of the files from the official zip for the same version you are running. As long as your IP, hostname, or install path doesn't change you don't have to re-issue the license. Good idea to make a backup of the files first just in case something goes wrong.. (e.g. some FTP clients delete everything and then upload the new stuff, that's very bad because /config/blesta.php is your config file that contains some very important information so don't lose it)

  5. 3 minutes ago, mezoology said:

    Hey Paul, I PM'ed you the site link. also "Root Web Directory" is correct.

    There is no link for any .css file

    Thanks for the link. The CSS loads on your portal page, on your order page it only loads a partial view. There is no header or footer, so the CSS is not loaded. If you modified any of the templates it's likely that broke it. You can check your error logs to see if there's anything there, ../logs_blesta/ defined under Settings > System > General. This has nothing to do with Nginx as far as I know. Possibly a syntax error. Haven't seen that happen before.

  6. There is certainly a link to the CSS in the markup. Your server is probably returning a 404 error because it can't load it because of the rules. View the page source, find the links to the CSS and find out if they are not correct.

    There is a possibility that the "Root Web Directory" path defined in Settings > System > General is not correct, it should be the full system path to your document root.

  7. 55 minutes ago, mezoology said:

    Thanks for answering Paul,

    Yes, it Nginx, and did as you suggested, but still plain text.

    not sure whats wrong here.

     

    Thanks

     

    Use the inspector in your browser, or view the source and look for the style sheet links, anything ending in .css. Can you open those files in your browser directly without getting an error?

    For example, in the demo at https://demo.blesta.com/order/main/packages/hosting/?group_id=1

    https://demo.blesta.com/app/views/client/bootstrap/css/application.min.css
    https://demo.blesta.com/client/theme/theme.css?dir=

  8. 1 hour ago, mezoology said:

    hey guys,

    Im currently setting up blesta, but my client order page is showing in plain text. was working fine yesterday.

    Im new to blesta btw.

    Thanks a lot.

    It sounds like the style sheets are not being loaded. I also see that /index.php/ is in your URLs. Can I assume you are using a web server other than Apache? If you are running Apache, then you may not have uploaded the .htaccess file that is included with Blesta. If you are running another web server like nginx, then you need the right configuration to rewrite URLs through index.php and handle style sheets https://docs.blesta.com/display/user/Installing+Blesta#InstallingBlesta-Nginx

  9. Selling dedicated servers with Vultr? Seems like there are no available locations returned by Vultr's API for that call. Does this happen with all Vultr servers? Does it work properly with a standard VPS from Vultr?

    Anything in your ../logs_blesta/ log files when this occurs? I wouldn't expect an API error to result in the page not working at all.

  10. tab_client_login.pdt has never existing in the official cPanel module.

    Here's all of the files that were included with the cPanel module in version 4.0.1:

    [root@goshen cpanel]# tree ./
    ./
    ├── apis
    │   └── cpanel_api.php
    ├── composer.json
    ├── cpanel.php
    ├── language
    │   └── en_us
    │       └── cpanel.php
    └── views
        └── default
            ├── add_row.pdt
            ├── admin_service_info.pdt
            ├── client_service_info.pdt
            ├── edit_row.pdt
            ├── images
            │   └── logo.png
            ├── manage.pdt
            ├── tab_client_actions.pdt
            ├── tab_client_stats.pdt
            └── tab_stats.pdt
    
    6 directories, 13 files
    

    An SSO powered login has since been added to cPanel by clicking the cPanel service row to expand the section, not under the "Manage" link, though we are open to adding it there also.. if you want to create a request.

  11. Also check your Blesta file logs ../logs_blesta/ and make sure that Apache and your cron run as the same user. If files in ../logs_blesta/ are owned by different users, that would be a problem.

    But, considering the page is slow and eventually loads, probably trouble connecting with the Vultr API, so Jono's suggestion to look at the module log under Tools > Logs > Module would be a good place to start!

  12. 1 hour ago, Tjw said:

    Hi Paul, I am currently on Blesta 4.11.2.  I was using timezone UTC +7 in the setting, and when I am trying to generate a report from the database, somehow it picks up UTC timezone.

    So, my report would be off by 1 day. For example, If I was looking for invoices starting from 1 July - 31 July. The report would not pick up the invoice created on July 1, since the database would show that invoice was created on June 30 at 17:00 hours, instead of July 1 at  00:00 hours. The difference is exactly +7 hours.

    From what I understand Blesta stores all dates in UTC in the database, then based on the timezone in the settings, it would offset them to fetch based on the appropriate date & time. So I assume it might be possible that the offset correction does not occur anywhere in Blesta 4.11.2. 

    Please look into this. Thanks.

    Which report(s) is this? Timezone offset likely occurs in the majority of locations in Blesta, so if it's not occurring in a specific location we can take a look, we just need to know where.

  13. Blesta version 4.12.0-b1 (BETA 1) is now available. You can download it from right here (Client Area Login Required). Read the blog post announcement at https://www.blesta.com/2020/09/17/blesta-4.12-beta-released/

    This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT.

    Please report any bugs you find in the v4.12 beta bug forum.

    Installing Blesta

    See Installing Blesta in the User Manual for instructions.

    Upgrading Blesta

    See Upgrading Blesta in the User Manual for instructions.

    Release Notes

    See Blesta Core - Version 4.12.0-b1.

    For older releases see all Change Logs.

  14. 7 minutes ago, turner2f said:

    We have at least one Department that is available to the public  ( for those that are not registered ).

    Just curious, can this  be used in reverse to block SOME IP addresses ?

    Would be for Brute Force or Spammers to the ticket system.

    If so, how ?

    See https://htaccessbook.com/block-ip-address/ for more information on these kinds of rules, for blocking specific IPs while keeping access otherwise globally open.

×
×
  • Create New...