Jump to content

Search the Community

Showing results for tags 'debug'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • News
    • The Lounge
  • Community
    • Pre-Sales Questions
    • Support
    • The Marketplace
    • Contribute
    • Show Off
    • Feature Requests
    • Bugs
    • Contests
  • Developer Corner
    • General
    • Extensions
  • BlestaStore's Forum
  • BlestaStore's BlestaCMS
  • BlestaStore's Resellers
  • BlestaStore's BlestaForums
  • BlestaStore's Promotions
  • CubeData's Official Announcements From CubeData
  • CubeData's Peer Support
  • CubeData's Resellers
  • ModulesGarden Club's Topics
  • Blesta Addons's Topics

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Wire


Location


Interests

Found 3 results

  1. Hello, Im doing a module for blesta, so it can work with centos web panel. But at some point i need to debug, xdebug but i was not able to do a debug session, it starts at line one of the index and if i say continue to run then it never reaches my breakpoints and gets stuck at loading the webpage in browser. How do you guys debug? I use php-storm and netbeans booth with x-debug.
  2. Hi, I am sorry to open this as a bug request, but imho, this may become a security bug, if the person who configure the universal module don't want to configure the email notification, or just want to configure the notifications at a later time. In /components/modules/universal_module/universal_module.php i see those lines : if (!isset($vars['package_email_html'])) $vars['package_email_html'] = "{% debug %}"; if (!isset($vars['package_email_text'])) $vars['package_email_text'] = "{% debug %}"; if (!isset($vars['service_email_html'])) $vars['service_email_html'] = "{% debug %}"; if (!isset($vars['service_email_text'])) $vars['service_email_text'] = "{% debug %}"; As a result, if you forget to add your own tags, then it may send emails with the server SSL key, as well as the Blesta encryption key. The email is also stored in the Blesta logs, and i am not sure this is the correct place to store this kind of stuff. I would strongly recommend to add a feature in the config files to disable this tag, or at least to comment those lines, and give us the choice to enable this or not! Or maybe someone can explain why it's there and what's the exact purpose of this, because the debug logs sent by this tag do not seems to include anything that can help to diagnose template issue! This tag seems dangerous. Thank you for taking this into consideration! Cheers! Carl
  3. Hello 1- Describe the issue you're experiencing. Re: There is a bug on some areas of Blesta that only shows wen enabling Debug Mode. 2- Provide detailed steps necessary to reproduce the issue. Re: Wen enabling debug mode on blesta.php to Configure::errorReporting(-1); On, navigating in some settings like for exemple: If you have eNom Module Installed (or any outher registrar module) If you have a Domain Package added and active on one client ,and then on Blesta Admin, navigate to: Clients->Browse->{click on a client with an Active eNom or outher Registrar Domain}->{Click on Manage on an Active Domain}->Whois You will see that the page dosent parses and it sows the error: strlen() expects parameter 1 to be string, object given on line 54 in /{blesta instalation root path}/helpers/html/html.php I have reproduced this bug in several outher areas os Blesta 3.1.3 (dont remeber where , but is the same bug) 3- List any generated errors. (The "Oh Noes" error pages are very helpful.) Re: strlen() expects parameter 1 to be string, object given on line 54 in /{blesta instalation root path}/helpers/html/html.php 4- Include the URL the error occurred on, relative to the installation path, ie "/admin/login". Re: admin/clients/servicetab/1/2/tabWhois/ 6- Include your configuration settings, i.e. OS, version of Blesta, version of module/gateway/plugin if applicable, version of PHP & MySQL. Re: Blesta 3.1.3, PHP 5.3, MySQL 5.1.73
×
×
  • Create New...