Hello,

I detected that I don't recieve any mail notification and when I go to manual Cron it shows the following message:

Null primary key not allowed.

I'm using Jomsocial 3.2.05 and this is the URL for my cron: www.durbet.com/index.php?option=com_community&task=cron

Many thanks,

Your issue caused by 3rd party plugin, I suggest you contact to the Joomla forum for fixing this, because this issue related with Joomla plugin and not Jomsocial itself..

Anyway, please you update your Jomsocial to version 3.1.0.1

After many weeks working on this error, I recoated it is not of any third party plugin. The problem with this error is any inconsistency with some tables Jomsocial my database. I'd say well before the mistake is someone else's problem, the tech support were some serious our problems, and that therefore we lost a lot of time.

I attached two tables as soon as I install phpmyadmin through the described error appears.

Thank you very much,

Hi Gerard,

Your sql cant be imported, I get this :

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1

also if possible can you give me screenshoot and some words to explain this issue? so if this is valid bug I can tell to the dev for how to replicate this issue and describe the detail of this issue.

note : please you upgrade your Jomsocial to the latest version

thank you

Hello Dimas,

My problem happens when I tried to execute cronjob system. It appears the following message error:

This page contains the following errors:

error on line 2 at column 1: Extra content at the end of the document
Below is a rendering of the page up to the first error.

In attached image. I don't know what happens this error because I'm not using any other third party pluggin or component.

Many thanks,

Hi,

Well, this is another issue, the error is like this :

<br />
<b>Warning</b>:  set_time_limit() has been disabled for security reasons in <b>/home/furlamsq/public_html/durbet.com/components/com_community/libraries/cron.php</b> on line <b>22</b><br />

Hi Dimas,

Thanks for this support. It happened because I change my php.ini file to a default php.ini file. Now it seems that Cronjob works, but the problem appears when I import the last tables. What are there that can cause its error?

Many thanks,

Hi,

Have you updated your Jomsocial to the latest version 3.2.0.5? please you update it first and back it to me if this issue still happens in the latest version.

note : I cant access your backend anymore, so I cant check the current Jomsocial version on your site

thank you

Hi dimas,

I'm using Joomla 3.3.0 and Jomsocial 3.2.0.5. Now I uploaded dbt_community_photos.sql and the error on Cronjob reappeared and it says:

Null primary key not allowed. (attached in image).

When I clear datatable content on dbt_community_photos.sql, the Cronjob continues working correctly. I don't know what characters or data contains this tables, that cause the Cronjob broken.

EDIT: I updated data access details on the first post.

Many thanks,

why did you upload that .sql where did you get it?

This .sql file was from my old Jomsocial installation (that was jomsocial 3.1.1), because you said me that must be a problem with some third party pluggin, I installed a Joomla installation by default, with last version of Jomsocial and late, I uploaded .sql tables trought my phpmyadmin system, and it is the result.

After many verifications I detected that when I upload:

dbt_community_photos.sql
dbt_community_groups.sql

It appears its Cronjob error.

Many thanks,

I think this issue caused by that, which not very compatible with the newest system... how about if you do not export that table, do you still get the same error or not? just let me know how it goes

Hi dimas,

In fact I said you that the problem with Cronjob is caused by this tables. The problems is that I need to import both of them because it have many activity content of my community, such as photos and groups.

Many thanks,

Hi Gerard,

After upgrading the photo and groups wont be deleted, the old data is still exist, so you dont need re-apply the sql structure from old database.