Site Warnings after ES 2.0.6 Upgrade
By Jared Hungerford on Wednesday, 07 December 2016
Posted in Technical Issues
Replies 6
Likes 0
Views 257
Votes 0
After Upgrading from ES 1.4.12 to ES 2.0.6 and upgrading the K2/EasySocial plugin to 2.0.1 the Directory portion of my site shows the following error messages.

ISSUE #1
I receive the following warning on the main directory - https://www.opensourceliving.org/index.php/business-directory :

Warning: Missing argument 3 for PlgK2EasySocial:: onK2PrepareContent(), called in .../libraries/joomla/event/event.php on line 69 and defined in .../plugins/k2/easysocial/easysocial.php on line 269


ISSUE #2
When the K2 - Easysocial plugin is disabled, business pages are accessible but then get the following EasyBlog Notices:

Notice: Undefined property: stdClass::$intro in /home/openso90/public_html/plugins/opengraph/easyblog/easyblog.php on line 416

Notice: Undefined property: stdClass::$content in /home/openso90/public_html/plugins/opengraph/easyblog/easyblog.php on line 416


ISSUE #3

I've had to turn off my backend Admin Template because it seems like there may be an offset. Please see the screenshot provided.
Regarding with your first issue, I've applied some fix in this file .../plugins/k2/easysocial/easysocial.php, it should work fine now.

But I would like to make sure what is your K2 current version? Because I was unable to access your backend now. it keep redirect back to your frontend.

Regarding with your second issue, it seems like that error is coming from this opengraph - Easyblog plugin, you should consult with this plugin provider and see how it goes.

Regarding with your 3rd issue, I will continuous to check once I can access your Joomla backend.
Arlex Wong
·
Wednesday, 07 December 2016 10:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex,

Thanks! I've edited the OP with the updated backend access. My apologies for that.

I am currently using K2 v2.7.1

The template in question is an Administrator template called JA Admin
Jared Hungerford
·
Thursday, 08 December 2016 01:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Jared,

I've checked in your site, it seems like these following 2 users some of the custom field is not stored correctly from database :
- Lester Crafton (Registered Users)
- Isabela Chagas (Registered Users)

Can you update your PHPMYADMIN access as well?

Regarding that K2 issue, I will update the fix in next release version as well.
Arlex Wong
·
Thursday, 08 December 2016 15:20
·
0 Likes
·
0 Votes
·
0 Comments
·
Regarding those two users, I believe it may be because after upgrade the field settings for that app in profile type were reset to required for registration and they both registered via FB quick registration method. I have since turned those switches off. I am not sure what else it could be causing an issue with those two users??
Jared Hungerford
·
Friday, 09 December 2016 06:34
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Jared,

Currently I am not really sure is is related to this yet, perhaps you can provide us with your PHPMYADMIN access so I can able to modify it back to correct dat.
Arlex Wong
·
Friday, 09 December 2016 10:59
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post