Jump to content

dimsum

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by dimsum

  1. Thanks for the replies!

    My installed Blesta version is 3.6.1.

    I've enabled the php error logs, but I see anything wrong in error_log files.

    I've also tried the developer tools on Safari and noticed something weird.

    There's a "d" in front of the JSON for services for clients that doesn't show the service widget. Clients that has the service widget doesn't have the "d".

    Regards.

     

     

    Screen Shot 2018-02-13 at 1.06.06 PM.png

    Screen Shot 2018-02-13 at 1.09.04 PM.png

  2. Hey everyone,

    I need some help here. I have no idea what happened? I haven't touched the database/pdt files.

    Yet for some odd reason, some clients have service widgets showing and some do not.

    All clients have services bound to them, I can see the widget if I type in the URL with "[website]/admin/clients/services/[client_id]/" but if I go back to the normal URL "[website]/admin/clients/view/[client_id]/", the service widget is missing.

    I've asked a client to check on his own client dashboard and he is missing the service widget as well.

    Can someone point me in the right direction?

    Regards.

    Screen Shot 2018-02-13 at 00.37.28.png

    Screen Shot 2018-02-13 at 00.38.04.png

  3. Thanks for everyone's help! This has finally been solved. I hope this thread will help someone in the future.

    The problem was the cache server didn't have my domain as an exception. I'm not sure if it's because the cache didn't work, causing the session not to work, resulting in the CSRF token being generated on each refresh.

    But the fix was to add the domain to the cache server exception list and everything works normally.

    So no need to disable any services or add the following to .htaccess.

    Quote

    Header set Cache-Control "max-age=0, private, no-cache, no-store, must-revalidate"

     

  4. I'm using the default theme.  It's a fresh install with one staff account that was required to be created in the installation page, other than that everything is default.

    The _csrf_token changes every time I refresh the page.

    I add the following code into the Blesta folder .htaccess, it should stop all caching.

    Quote

    Header set Cache-Control "max-age=0, private, no-cache, no-store, must-revalidate"

    Sadly, this still doesn't solve the issue. Now I'm trying to see if I can temporarily disable the caching, so that I can at least confirm if it is or is not the root of the issue.

     

    Regards.

  5. Hi!

    I'm having trouble with the client login page. For some reason, no matter what I input in the client page, it only returns "The form token is invalid.". The admin page is working fine tho.

    Things I've tried

    • Reinstalled 3.6.2 and 3.6.1
    • Configure::errorReporting(-1); - No idea where to see the logs
    • Configure::set("System.debug", true); - No idea where to see the logs
    • Configure::set("Blesta.verify_csrf_token", false); - Works, but I rather have CSRF enabled

    Current settings are cPanel using Softaculous to install Blesta.

     

    Has anyone encountered this error? Or can anyone kindly tell me how can I find out what's causing this?

     

     

    Screen Shot 2016-08-15 at 22.14.28.png

×
×
  • Create New...