Hello Elvira,

Sorry for late reply to this,
It seems like you hitting this error Initializing Database Stored Functions Failed, can i have your phpmyadmin access so we can help you check on this? Please advise.

Hi Alex,

Yes of course, I included it.

Tnx

Hello Elvira,

Regarding your issue with upgrading to 1.2.17, can you make sure your db user has granted the privilege to create / execute db stored function?
If your db user already granted the necessary privilege and the upgrade process still failed at 'Initializing Database Stored Functions', then most likely you have to request with your webhosting provider to help you execute below command from your mysql

mysql_upgrade -u root -p

Reference list : http://dev.mysql.com/doc/refman/5.0/en/stored-routines-privileges.html

But I already installed easysocial before and (with a little bit of help from you guys) it always went ok. How could it be possible I don't have access anymore. I did move the site from a subfolder (test version) to the mainfolder. (html) Would that make a difference?

Hello Elvira,

Yes, that was because we have re-factored and revamped the whole stream library, so some of the database by default is not give the user privilege to manually have that store function, then when re-install that time failed in this error 'Initializing Database Stored Functions'.

can you make sure your database user has granted the privilege to create / execute database stored function? So we can try to install again and see how it goes? Please advise.

Also, the backend is saying: Awesome! You are running on the latest version of EasySocial.
Installed version: 1.2.17 . But on frontend big error.

Should I just uninstall the component and try to install it from the start?

I'm not sure Alex. Should I be able to see this somewhere. Support is available on Monday . I know I have a lot of permissions. So can we test this?

Hello Elvira,

Yes, because your installation is not load complete yet, stuck in 39%

What you need to do is make sure your database user has granted the privilege to create / execute database stored function? Then try request with your webhosting provider run this sql in your database

mysql_upgrade -u root -p

If your webhosting provider asking that why need to run this sql, you can paste this reference link to them
-> http://dev.mysql.com/doc/refman/5.0/en/stored-routines-privileges.html

Ok, I sent the message. Hopefully they will respond this weekend..

Hello Elvira,

I'm sorry for make you inconvenience with this currently
Okay, keep us updated then.
You can temporary re-install back 1.2.16 version in your Easysocial first.

Hi Arlex,

I got an answer: The database has create and execute rights.

Could you help me install the new easysocial version? I restored a backup (which took a bit of time) to make the previous version work, and I'm a bit hesitant about pressing the 'update' button.

FYI, if you use GoDaddy Shared Hosting they will not do this for you.

James

Luckily I'm not using GoDaddy

They are horrible! I told myself not to switch to them and didn't listen!

Hello Elvira,

Sorry but not too sure if I get you here but did your hosting provider already fixed the privileges and we can proceed with the upgrade?

Hi Mark,

Yes they said I have the privileges. But if I understand correctly, I need more privileges than I needed before to be able to update to the latest version?

I don't like the way of installation. It should be easy without asking hosting providers like previsous installation.

Hi Elvira,

I am sorry for the delay of this reply.

Today I logged into your phpMyAdmin and attempt to execute below create function script but I hit access denied error. Please see http://screencast.com/t/mnYR8af4Dw

DELIMITER $$

CREATE FUNCTION `es_isfriend` (p_source int, p_target int) 

RETURNS INT 

DETERMINISTIC 

READS SQL DATA

BEGIN

    DECLARE cnt INT;

    select count(1) into cnt from `jos_social_friends` where ( `actor_id` = p_source and `target_id` = p_target) OR (`target_id` = p_source and `actor_id` = p_target) and `state` = 1;

    RETURN cnt;

END $$

DELIMITER ;

Can you check with your hosting provider again and see if the db user 'web392' has granted the SUPER privilege? If not, then your db user will need to have this SUPER privilege granted in order to execute create / alter function statement.

Please advise.

Hope this help and have a nice day

Joon-Kyu Park wrote:

I don't like the way of installation. It should be easy without asking hosting providers like previous installation.

Hello,

In new version, we utilise the db stored function to retrieve the stream items. Most of the time you do no need to ask from your hosting provider if your MySQL configured correctly and your db user has granted the SUPER privilege.

Anyway, if you still having issue installing / upgrading your EasySocial, then maybe you can pass me your Joomla backend admin access and your phpMyAdmin access so that I can run some test to see why the creation of stored functions failed.

Please advise.

Hi,

Ok I think I executed everything now. Easysocial seems to be working now. Haven't tested everything yet but at least no error when opening the page. This is what it said after installing:

Executing maintenance scriptsSuccess
2 scripts to execute.
Executed script: Sync cluster access in stream table.
Thread stack overrun: 12344 bytes used of a 131072 byte stack, and 128000 bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack. SQL=update `jos_social_stream` as a inner join `jos_social_stream_item` as b on a.`id` = b.`uid` inner join `jos_social_privacy_items` as c on c.`uid` = b.`uid` and c.`type` = 'story' set a.`access` = c.`value`, a.`privacy_id` = c.`privacy_id`, a.`custom_access` = es_itemcustomaccess(c.`privacy_id`, b.`actor_id`, b.`uid`, b.`context_type`, c.`value`) where a.`privacy_id` = 0
Updated maintenance version.

After that I finished:

Congratulations! EasySocial has been successfully installed on your site and you may start using it.

That executed script was in read font. Is this a problem or not?

Hello Elvira,

I am sorry for the delay of this reply.

Thread stack overrun: 12344 bytes used of a 131072 byte stack, and 128000 bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack. 

It seems like when you execute the maintenance script, the script hit MySQL saying the stack size is not enough

Anyway, I've use another approach to run the maintenance script and everything seem okay now
Please verify again

Hope this help and have a nice day