By vivalditec on Wednesday, 11 December 2013
Posted in Technical Issues
Replies 31
Likes 0
Views 1.5K
Votes 0
Hello,

we've started experiencing registration errors. We use the user registration with activation email. After a cache purge or Apache restart the user registration works once. On a consecutive attempts the form gets submitted with no warnings but results in a generic page with error "Sorry, but there are some errors in your registration form". The following outputs to Apache log:

[Wed Dec 11 12:48:29 2013] [error] PHP Warning:  Missing argument 3 for SocialDispatcher::trigger(), called in /var/www/plugins/user/easysocial/easysocial.php on line 187 and defined in /var/www/administrator/components/com_easysocial/includes/dispatcher/dispatcher.php on line 80, referer: /administrator/index.php?option=com_easysocial&view=users
[Wed Dec 11 12:50:24 2013] [error] PHP Notice: Undefined index: es-fields-69 in /var/www/media/com_easysocial/apps/fields/user/cover/cover.php on line 76, referer: /unity/registration
[Wed Dec 11 12:50:24 2013] [error] PHP Notice: Undefined index: es-fields-67 in /var/www/media/com_easysocial/apps/fields/user/cover/cover.php on line 76, referer: /unity/registration
[Wed Dec 11 12:50:24 2013] [error] PHP Notice: Undefined index: es-fields-54 in /var/www/media/com_easysocial/apps/fields/user/joomla_timezone/joomla_timezone.php on line 106, referer: /unity/registration
[Wed Dec 11 12:50:24 2013] [error] PHP Notice: Undefined offset: 1 in /var/www/administrator/components/com_easysocial/tables/registration.php on line 162, referer: /unity/registration


Any clue to a solution is greatly appreciated.
Hi,

I can't seem to modify the files in your test server but I've identified the changes.

Replace the file I've attached in /components/com_easysocial/controllers after you've upgraded your production site to the latest version.
·
Saturday, 25 January 2014 13:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

Hm after logging into the FTP, I don't see which folder is your root Joomla folder. Can you please advise?
·
Wednesday, 11 December 2013 23:34
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

thanks for getting back to us. It is in /var/www/ directory.
·
Wednesday, 11 December 2013 23:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

The FTP access that you've provided does not have the permission to modify files due to file folder permission issue. (The file's user/group does not correspond to the user/group that you've provided, and the file is set to 644, which only allows the original user of the file to modify).

Also, after a few tries, it seems like I can no longer access as it is returning me this error now. (Refer screenshot)
·
Thursday, 12 December 2013 16:12
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

I have added the vivaldi user to the www-data group and change the permission to 755 on all , just while you troubleshoot it. This should be enough , just ping if you need something else
·
Thursday, 12 December 2013 18:31
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

Just wondering if there has been any progress on this registration problem we are having ?
·
Friday, 13 December 2013 18:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Sorry that I missed out this post.

I still can't write the files because even though you've added the user to the group, but the files permission is set to 644, which means only the user have the permission to write it.

Anyway, we are preparing the next minor release, in which I've included all of the fixes in the error that you've provided.
·
Friday, 13 December 2013 19:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

I have tested it myself and I can edit everything in the /var/www folder with that user , all permission are set to 775 which gives the group www-data full access , We had to delay our launch , because of these registration problems we are having. So if you can fix it for us , without us waiting for the next minor release we would be very thankful

best regards
Vivaldi
·
Friday, 13 December 2013 19:54
·
0 Likes
·
0 Votes
·
0 Comments
·
We have update to EasySocial v1.1.3 now , and we still have an registration issue , now there is no error that appears on the site , just goes to the frontpage . In the apache errorlog , we have only gotten this error .

" [error] [client 89.160.172.106] PHP Notice: Undefined offset: 3 in /var/www/administrator/components/com_config/controller/application/save.php on line 112, referer: https://vivaldi.net/administrator/index.php?option=com_config";

which points to :

// Set the redirect based on the task.
switch ($this->options[3])
{
case 'apply':
$this->app->redirect(JRoute::_('index.php?option=com_config', false));
break;

case 'save':
default:
$this->app->redirect(JRoute::_('index.php', false));
break;
}
·
Sunday, 15 December 2013 19:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

The error message seems like it is sourcing from com_config -> save, which is an action that is only carried if you are saving a configuration from Joomla's backend -> Global Configuration. EasySocial does not utilise com_config.

As for the registration issue, I tested it on your site and I am able to register with the test username "estest". Refer to screenshot http://d.pr/i/u8TU
·
Monday, 16 December 2013 11:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

Thank you for your reply , but it seems very random , and we are not seeing the same errors in the logs anymore. However just try to register a couple of users and you will see that very likely the second one will fail.

No error on the page or the logs , it just doesn't go to step 2 in the registration process , simply falls back to the front page again.
·
Monday, 16 December 2013 18:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Our test users are complaining about not being able to register and yet some can. Seems really random , can you please give advice us what to do. It seems like it is a easysocial problem , cause we have tried jomsocial now on our dev server , and with the same environment (restored) , we are not seeing this registration issue there.

This registration issue just seemed to pop up either after the upgrade or just shortly before it , it might have been the 1.09 upgrade.

Sadly we are getting quite desperate And having almost no error messages to go on makes it even harder
·
Tuesday, 17 December 2013 00:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

Hm, this is strange. Are you using the link https://82.221.99.165/unity/registration to register on your site?
·
Tuesday, 17 December 2013 01:07
·
0 Likes
·
0 Votes
·
0 Comments
·
hey we have synced up with cloudflare cdn , so https://vivaldi.net/unity/registration can point 82.221.99.165 , 190.93.242.176 or 190.93.243.176 f.ex.

but we have tested going directly on 82.221.99.165 , and it randomly fails there as well ofc.
·
Tuesday, 17 December 2013 01:30
·
0 Likes
·
0 Votes
·
0 Comments
·
I tested the site which worked for the first registration. The second time I got an error as seen in the attached screen shot. I ought to test this on my own site.
·
Tuesday, 17 December 2013 05:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

It seems like this is cache related where sessions are not created properly on 2nd registration onwards.

I've applied a small patch on your site. Can you give it a try again and see if it is working properly now? If it is I will apply this fix in our release.
·
Tuesday, 17 December 2013 12:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you we will test away and let you know
·
Tuesday, 17 December 2013 16:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks, let us know how this goes
·
Tuesday, 17 December 2013 17:13
·
0 Likes
·
0 Votes
·
0 Comments
·
This looks like it solved the issue , we have had a bunch of people testing this from all over and all seems to have gone through the registration process

thanks guys .... rock on
·
Tuesday, 17 December 2013 20:01
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

You're welcome.
·
Tuesday, 17 December 2013 21:05
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey
It looks we will have to open this ticket again , since we just tested upgrading to easysocial 1.1.4 on our test system identical to our production system , and we got the registration errors again !! , We did the following tried upgrading only easysocial to 1.1.4 and got the registration error , reverted the test environment back to production state , tried updating to joomla 3.2.1 first and then easysocial to 1.1.4 and got the registration errors again.

reverted back and upgrading only joomla to 3.2.1 and everything works , so safe to say it is the easysocial upgrade that is causing this. Reopening this ticket since it might be that you manually edited some files to fix the first registration errors that we need to edit back for the upgrade to work ??
·
Tuesday, 14 January 2014 23:42
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Sorry for the late reply.

Is your site currently on the reverted one (including the patch I've made) or it is on the latest 1.1.4? (Hopefully I can trace back what patch I did on your site)
·
Wednesday, 15 January 2014 11:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi production site is on the 1.1.3 with the patch you applied to fix the registration error.

We have a test environment that is identical to the production system , we are testing upgrades on before applying it to production
·
Wednesday, 15 January 2014 20:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Could you provide me both access?
·
Thursday, 16 January 2014 10:57
·
0 Likes
·
0 Votes
·
0 Comments
·
have added the url to the test site were we have updated from 1.1.5 and joomla 3.2.1 , and we have the registration issue there after the easysocial upgrade. the production site is very active at the moment so would rather not be testing anything on that .
·
Wednesday, 22 January 2014 23:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Oh no worries I won't be doing any test on your production site. I just need to cross check what changes I've made on your production site.
·
Thursday, 23 January 2014 10:00
·
0 Likes
·
0 Votes
·
0 Comments
·
any update ? there is a bunch of fixes that we are waiting for , which is resolved in the 1.1.5 fix
·
Friday, 24 January 2014 00:42
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

I am not sure if the credentials that you've provided is the test site or the production site.

As mentioned before, I will need credentials to both sites, only I am able to trace what changes I've made.
·
Friday, 24 January 2014 09:41
·
0 Likes
·
0 Votes
·
0 Comments
·
I supplied both , created the user on both of them , xx.xxx.xx.175 is the test site xx.xxx.xx.165 is production
·
Friday, 24 January 2014 18:04
·
0 Likes
·
0 Votes
·
0 Comments
·
thank you this worked for us
·
Thursday, 30 January 2014 07:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating, glad that your issues are resolved now.
·
Thursday, 30 January 2014 15:33
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post