EasySocial Dashboard/My Profile causing WSOD

By Zach Anderson on Tuesday, 11 October 2016

Likes 0

Votes 0

Hello,

I am having an issue where if I (and I alone: this does not currently happen for any other Users) navigate to /homepage on our site (which is an EasySocial - Dashboard Menu Item with the Link index.php?option=com_easysocial&view=dashboard&type=all) I get a blank White Screen Of Death.

Using Chrome's Developer Tools I find the page's entire HTML is simply this:

<!-- saved from url=(0034)http://uee.islandwood.org/homepage -->

<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div class="stream-files multiple-files">

    </div></body></html>

No errors appear in the JS Console nor have I been able to capture any PHP or server errors. As you can see from the HTML above the Joomla! Debug Console doesn't even appear.

Checking the Timeline in Chrome Dev Tools I do see the page content and scripts getting loaded into the browser. The last script I see firing is easysocial-1.4.12.static.min.js:556 (see attachment)

I can navigate to other EasySocial pages (such as /component/easysocial/friends?Itemid=) but if I click My Profile underneath my name in any EasySocial page I get the same WSOD issue (/component/easysocial/profile?Itemid=)

None of my other users are experiencing this issue but I'd like to resolve and understand it before onboarding a new quarter of students.

Thanks!
-Zach

Now that is odd... EasySocial Dashboard and My Profile are both working for myself (User Zach) and for our test User (Darth Vader)... maybe there's more problematic Streams?

You mentioned an error message: may I know where you were seeing the message? I'm still new to Joomla and haven't for the life of me been able to find error messages to help me diagnose these problems. I've set error reporting to maximum, changed templates, changed flags in configuration.php (which I have since reverted)...

You can check my attached screenshot below, the happen when I click load more button from the dashboard or click on the left sidebar filter, it will not show the correct result.

As for the logout problem I created those three Menu Items as a science experiment to diagnose the problem:

Logout is a Menu Item Type of Users - Logout with a Link to index.php?option=com_users&view=login&layout=logout&task=user.menulogout
Signout is an External URL with a Link to http://uee.islandwood.org/index.php?option=com_users
Signoff is an External URL with a Link to http://uee.islandwood.org/component/users/?view=login

I also added a Login Module to the Footer: it behaves the same as Signoff. The first one (Logout) is the one that I want to work.

Logout gives that error that you saw 0 Call to a member function get() on null.
Signout works but is ugly and I'd really prefer to get Logout working.
Signoff just refreshes the page. Now, if you try to use EasySocial's logout button (see attachment) it does the same thing: it refreshes the page but doesn't log you out or throw any errors.

You'll notice clicking each of those three gives a different behavior... I was hoping it would give insight into what the problem is.

After I started having problems with the EasySocial Dashboard for my User I updated everything, including to Joomla 3.6.2
If that update broke something how do I identify and repair it?

I think you do not need to create any extra login/logout menu item on your page is because it seems like I already found out where is the issue coming from, but I am not really sure that is that rules from your .htaccess file, but as long as when I remove these code from your .htaccess, everything seems work perfectly fine.



AddHandler application/x-httpd-php70 .php .php5 .php4 .php3

<IfModule mod_expires.c>

ExpiresActive On

<FilesMatch "\.(pdf|flv|jpe?g|png|gif|js|css|swf|cur|ico)$">

Header set Cache-Control "public"

ExpiresDefault "access plus 1 month"

</FilesMatch>

</IfModule>

May i know what is these rules purpose?

Arlex Wong

Friday, 14 October 2016 13:36

0 Likes

0 Votes

0 Comments

#291783

I should probably also mention I have tried updating everything possible, even doing an uninstall/reinstall of EasySocial but the same issue persists.

-Zach

Zach Anderson

Wednesday, 12 October 2016 00:14

0 Likes

0 Votes

0 Comments

#291424

Hello Zach,

I believe this is most likely an issue with one of your installed EasySocial app but to be sure, could you try turning on error reporting at the back end under Joomla's Global Configuration area and see if you get those errors?

I tried to login to your site but the login you provided isn't working for me

Mark

Wednesday, 12 October 2016 01:46

0 Likes

0 Votes

0 Comments

#291429

Hey Mark,

Under Global Configuration > Server > Server Settings I have Error Reporting set to Maximum but am still not seeing any errors.

Are you using the credentials I supplied with this post or the credentials listed in my account/profile here on Stackideas? I can double check that they're accurate.

-Zach

Zach Anderson

Wednesday, 12 October 2016 01:54

0 Likes

0 Votes

0 Comments

#291431

Hello Zach,

Our updated forums are now a little more intelligent. If you add your site details in the post, it will inherit from the post, otherwise it'll use the one you specified in https://stackideas.com/dashboard/site

By the way, could you edit your post and also include your own account which can reproduce the error and with the FTP access as well? I believe I may need to modify some of the files to try to scoop out the errors.

Mark

Wednesday, 12 October 2016 02:04

0 Likes

0 Votes

0 Comments

#291433

Hey Mark,

Thanks for the quick replies

I added the credentials to this post that should allow you to login to the Joomla admin interface. I double checked and the URL, username, and password are all correct.

I don't have a username/password set for SFTP on hand: I use a private key set. If you can't get in to the Joomla admin I can setup SFTP for you.

-Zach

Zach Anderson

Wednesday, 12 October 2016 02:15

0 Likes

0 Votes

0 Comments

#291435

Hello Zach,

Thanks, I am able to login to the back end now but I can't login on the front end

Is there some sort of policy that prevents admin to login on the front end?

Mark

Wednesday, 12 October 2016 02:51

0 Likes

0 Votes

0 Comments

#291438

No... in my efforts to fix this EasySocial WSOD issue I believe I broke the Login module.
The following link should grant you access to the front end:

http://uee.islandwood.org/component/users/?view=login

Zach Anderson

Wednesday, 12 October 2016 02:54

0 Likes

0 Votes

0 Comments

#291440

Hi Zach,
After checking the homepage, it seems there's a fatal error associated with this file JoomlaFolder/administrator/components/com_easysocial/includes/storage/storage.php
Can you set up a SFTP account for us as you mentioned so we can help you troubleshoot this issue further? Thanks.

Raymond

Wednesday, 12 October 2016 11:42

0 Likes

0 Votes

0 Comments

#291462

Hmm... the button to edit this post appears to have disappeared (see attachment).

I added the FTP credentials to Site Details under my profile here on Stackideas. If you can't get to it there you can also login to the backend of my Joomla (the credentials for which should still be attached to this post) and open the FILEman component: I left a file there for you which should help.

-Zach

Zach Anderson

Wednesday, 12 October 2016 23:19

0 Likes

0 Votes

0 Comments

#291571

Hmm... the button to edit this post appears to have disappeared (see attachment).

Can you check again, that edit button should be appear now.

I added the FTP credentials to Site Details under my profile here on Stackideas. If you can't get to it there you can also login to the backend of my Joomla (the credentials for which should still be attached to this post) and open the FILEman component: I left a file there for you which should help.

I can access your backend now and FTP server, but suddenly now I unable to login from your frontend, you can check my video here : http://screencast.com/t/WBzQIlpl , do you have have hit this kind of issue before?

Arlex Wong

Thursday, 13 October 2016 00:08

0 Likes

0 Votes

0 Comments

#291579

Thanks; I see the edit button again.
The EasySocial and Login (basic/default) Modules both aren't working for me right now. I believe this happened when I was attempting to resolve the EasySocial problems.

Login from the following URL still works: (using the Component, not the Module)
http://uee.islandwood.org/component/users/?view=login

Zach Anderson

Thursday, 13 October 2016 00:13

0 Likes

0 Votes

0 Comments

#291581

! It looks like it's working again!
... that is you who fixed it, right?

-Zach

Zach Anderson

Thursday, 13 October 2016 02:11

0 Likes

0 Votes

0 Comments

#291591

So, while I am able to view my EasySocial Dashboard without the WSOD I still have two questions:

What did you do to fix it? I've another site with EasySocial and want to be prepared in case it happens again.
EasySocial seems to be futzing with my login process (as you experienced firsthand). Using the Timeline in Chrome Dev Tools I'm seeing 'easysocial' in the URL of the GET request even when clicking a Menu Item of Type Users - Logout

Thanks,
-Zach

Zach Anderson

Thursday, 13 October 2016 10:40

0 Likes

0 Votes

0 Comments

#291621

Hey there,

I am sorry for the delay of this reply,

Yes, I found out one of the problematic stream causing the issue, so I run 1 queries to set this stream to unpublished :



update uee_social_stream set `state` = 0 where id = 4727;

So that error message will not appear now, but yesterday night until now, but it seems like that is not working for me.

I feel curious why you said it working fine now.

EasySocial seems to be futzing with my login process (as you experienced firsthand). Using the Timeline in Chrome Dev Tools I'm seeing 'easysocial' in the URL of the GET request even when clicking a Menu Item of Type Users - Logout

Do you mean from this 2 logout menu item?

By the way, I did try click "logout" menu item, it seems like that is not working, hitting this following error :



0 Call to a member function get() on null

It seems like your current Joomla version is not fully installed, because that menu actually is coming from the Joomla. May i know do you have facing this issue before?

Arlex Wong

Thursday, 13 October 2016 13:35

0 Likes

0 Votes

0 Comments

#291648

Now that is odd... EasySocial Dashboard and My Profile are both working for myself (User Zach) and for our test User (Darth Vader)... maybe there's more problematic Streams?

You mentioned an error message: may I know where you were seeing the message? I'm still new to Joomla and haven't for the life of me been able to find error messages to help me diagnose these problems. I've set error reporting to maximum, changed templates, changed flags in configuration.php (which I have since reverted)...

As for the logout problem I created those three Menu Items as a science experiment to diagnose the problem:

Logout is a Menu Item Type of Users - Logout with a Link to index.php?option=com_users&view=login&layout=logout&task=user.menulogout
Signout is an External URL with a Link to http://uee.islandwood.org/index.php?option=com_users
Signoff is an External URL with a Link to http://uee.islandwood.org/component/users/?view=login

I also added a Login Module to the Footer: it behaves the same as Signoff. The first one (Logout) is the one that I want to work.

Logout gives that error that you saw 0 Call to a member function get() on null.
Signout works but is ugly and I'd really prefer to get Logout working.
Signoff just refreshes the page. Now, if you try to use EasySocial's logout button (see attachment) it does the same thing: it refreshes the page but doesn't log you out or throw any errors.

You'll notice clicking each of those three gives a different behavior... I was hoping it would give insight into what the problem is.

After I started having problems with the EasySocial Dashboard for my User I updated everything, including to Joomla 3.6.2
If that update broke something how do I identify and repair it?

Thanks again.
-Zach

Zach Anderson

Thursday, 13 October 2016 21:59

0 Likes

0 Votes

0 Comments

#291710

Nice catch Alex! I swear I looked through the .htaccess files...

I don't know! To my knowledge there's no need for them.

So before I wrap this ticket up do you have any theories as to how that got added to the .htaccess file? I'm assuming that since this issue is recent that .htaccess must have been modified recently... would updating Joomla and/or Extensions do that? I know I never changed it.

-Zach

Zach Anderson

Friday, 14 October 2016 22:14

0 Likes

0 Votes

0 Comments

#291839

Currently I have no idea why these code being added into your .htaccess file, but I can confirm one thing is when during the update Joomla and other extensions, it will not update this .htaccess file.

But I realised your site .htaccess file permission is set to 644, I would suggest you set to 444 regarding this .htaccess because this file should be only allow yourself to edit it, if not other user can go through this way to hack into your site.

Arlex Wong

Friday, 14 October 2016 23:55

0 Likes

0 Votes

0 Comments

#291853

Thanks man! Chmod 444 done.

So to recap:

Login issues were due to modifications to ~/public_html/mysitename/.htaccess
How these changes happened is a mystery
Fixing EasySocial had to do with a problematic Stream.

Which leaves me with one final question (and back to the original topic of this post, after our Login detour):

How did you identify which Stream was causing the issue? (id=4727 in this case)

-Zach

Zach Anderson

Saturday, 15 October 2016 00:05

0 Likes

0 Votes

0 Comments

#291854

Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

So to recap:

Login issues were due to modifications to ~/public_html/mysitename/.htaccess
How these changes happened is a mystery
Fixing EasySocial had to do with a problematic Stream.

Yes, that is correct.

Which leaves me with one final question (and back to the original topic of this post, after our Login detour):

How did you identify which Stream was causing the issue? (id=4727 in this case)

if i recall correctly, I saw that was some PHP fatal error as my colleague mentioned in earlier, so I check further it seems like it coming from the user file app from Easysocial, once I disabled it, then it won't show that error again.

Then I try to take a look of your stream data from backend, it seems like someone uploaded 1 file from your Easysocial, then I try to temporary disable it, then it work fine, so I through this way to identify this problematic issue coming from this stream id.

Arlex Wong

Saturday, 15 October 2016 17:50

0 Likes

0 Votes

0 Comments

#291895

Excellent! Thank you Arlex!

Cheers

-Zach

Zach Anderson

Saturday, 15 October 2016 23:29

0 Likes

0 Votes

0 Comments

#291912

Hi there,

You are most welcome. Glad to hear that your issue has been resolved now.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.

Arlex Wong

Sunday, 16 October 2016 09:55

0 Likes

0 Votes

0 Comments

#291925