Hey Tony,

I am sorry for the delay of this reply,

It seems like that registration and reset password also working correctly, you can refer on my attached screenshot below.

What I noticed is when the user completed their registration, then it will redirect to your homepage, I have help you set that after registration then redirect to Easysocial page.

And I also noticed you haven't setup your cronjob in your server yet, because I still see your pending email from backend > Easysocial > email activity page.

Cronjob Documentation link : http://stackideas.com/docs/easysocial/administrators/cronjobs

Thank you for the help with the user. As for the cronjobs, I'm really not familiar with how that works, but I did review your documentation. I use Siteground, and I do have three questions:

1. In the Setup Email part, does it matter what email I use? For example, can I just use the email for my admin address, or do I even really need to put an email here? I don't want to be inundated with emails from whatever cronjob is.

2. Is there a recommended setting for the "Step 1. Configure the interval at which you wish to run the cron job." I have no idea what to set for seconds, minutes, etc.

3. Do I simply copy the code you have in "Step 2. In the Command to run field, type the command you wish the system to run.

Example:

/bin/wget -O /dev/null "http://stackideas.com/index.php?option=com_easysocial&cron=1";

You can have cron send an email everytime it runs a command. If you do not want an email to be sent for an individual cron job you can redirect the command's output to:

/dev/null like this: mycommand >/dev/null 2>&1"

Hi Tony,

The email address are used to notify the full output of the cronjob result so it will be easier to know if there are something wrong with the cron setup. Once you have configured your cronjob correctly, you can safely empty the email field fron the cronjob settings.

2. Is there a recommended setting for the "Step 1. Configure the interval at which you wish to run the cron job." I have no idea what to set for seconds, minutes, etc.

You can put any interval that is you think is the best for your site. We recommend you to put at least 5 minutes interval so that the user can get the notification faster and lesser load on your server.

3. Do I simply copy the code you have in "Step 2. In the Command to run field, type the command you wish the system to run.

You must add the following cron command in order for the cron to work correctly:

** Important note : change 'yoursite.com' with your site name.

/bin/wget -O /dev/null "http://yoursite.com/index.php?option=com_easysocial&cron=1"

The rest of the command is optional and does not need to be included in the cron command.

Hope these help.

Okay, I followed the instructions, and I received the following email message:

/bin/sh: /bin/wget: No such file or directory

Can you provide us with your Cpanel access which you setup this cron command?

Before you provide us that Cpanel access, can you try following cron command and see how it goes?

/usr/bin/wget -O /dev/null "http://yoursite.com/index.php?option=com_easysocial&cron=1"

Okay, I got this new email message after updating with the information you provided.

--2016-04-06 23:30:01-- http://impliedmagazine.com/index.php?option=com_easysocial&cron=1
Resolving impliedmagazine.com (impliedmagazine.com)... 181.224.147.207
Connecting to impliedmagazine.com (impliedmagazine.com)|181.224.147.207|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/x-json]
Saving to: '/dev/null'

0K . 126M=0s

2016-04-06 23:30:02 (126 MB/s) - '/dev/null' saved [1474]

Yes, finally configured correctly, can you give it a check from your backend component mail activity page, is it processing all the pending email now?

Yes, it did, thank you!

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.