500 error on View Orgs and Person Dashboard

Hello UNA Community,

I have ran out of options to try to solve this issue on my site - Have worked at it for a few months now and recently had some assistance from one of the UNA experts.  However the problems persists.

Firstly a logged in user tries to access their Dashboard - and get a blank page or the 500 error depending on browser for this url https://molosserdogs.com/page/dashboard

Secondly he Organizations module allow the creation of an Org but viewing the org throws the above mentioned error. Upon creation the profile is switched to the recently created Org but the page is blank or has the 500 error. Accessing other pages shows the profile is logged in.

https://molosserdogs.com/page/view-organization-profile?id=1

Error logs does not show much of anything that pertains to the 500 error except that the hosting comapny did find this.

  [22-Sep-2020 17:19:02 UTC] PHP Warning:  unlink(/pathtomysite/public_html/storage/bx_organizations_pics/s/s5/s5s/s5s8ygtyz85cejqnpka9r6h79kmfnvbv): No such file or directory in /pathtomysite/public_html/inc/classes/BxDolStorageLocal.php on line 112

I suspect that the two instances of the similar 500 erro above may be related to something on the site or server but cannot figure it out.

For testing purposes and to see the behavior without creating an account you may use: 

cron@molosserdogs.com and TestUser1

Generally speaking the error-log has nothing related to this specific error

  • 733
  • More
Replies (7)
    • Hello, I suggest that you deactivate all the blocks on the problematic page and then reactivate them one by one to determine which one is responsible for this error.

      • Baloo - thank you so much. I did that and identified that the membership block is causing the problem. At I will continue to activate and see if any other ones does the same.

        • I had a similar problem with account number 1, all users were able to see their profiles but account no 1 when logged in was giving a gateway error to see its own profile.

          After checking the modules one by one with Baloo's method and deactivating Profile stats it was cured.
          Interestingly eventhough I reactivate it it is alright now.

          • On the person dashboard the culprit was a block called "content". what does that block do?

            • That is very interesting - theoretically it should not be alright.  Lol. Ghost in the machine.

              • we checked the situation with Leonid.
                His diagnose was very big profile page, mysql was giving timeout error.
                So I shrinked the profile page, now it works with no problem.

                • Mine was some rogue blocks and Baloo's suggestion of deactivating blocks until I found the culprit worked.

                  Login or Join to comment.