JomSocial 3.1 Common Upgrade Issues

Revision as of 03:22, 5 December 2013 by Sinisakrisan (Talk | contribs)

Note: The explanations in this article only apply to sites that are being upgraded to JomSocial 3.1 from earlier versions.
If you are starting from a fresh sites, you'll most likely never experience issues explained here

Failed to parse time string

Timestring.png

This is a very common error, specially for the sites which have old database (several years old sites) or those with a lot of dirty data
It looks like the error does not tell us anything special, but if you take a closer look, the error actually said that is failing to parse date string 1987-34-58 23:59:59 which is true, because 1987-34-58 23:59:59 can never be an actual date
In this case, 1987 is the year, 34 is the month and 54 is the day. Obviously, the date here is wrong.
It can also happen that you have completely date unrelated value like random string of characters, solution will however, be the same.

Warning: Before you proceed, please backup your entire site and whole database

First, navigate to your database. You will most likely use phpMyAdmin as a common software to manage your database

Note: The images shown bellow might differ in various versions of phpMyAdmin. If that is the case, please refer to the phpMyAdmin Manual

Once database have been selected, navigate to Search tab

Phpmyadminseach.png

Insert the word you want to search for. In our case, it would be 1987-34-58 23:59:59'
Select to find exact phrase - This is particularly important as 1987 is a valid year and it could find more records if we don't set this option
Select All tables to be searched and click on Go button

Phpmyadminseach2.png

You should see similar result like on the picture bellow

Phpmyadminseach3.png

You can now either delete the record, or browse it further. Lets just click on Delete. We will leave up to you if you want to browse it further.
Now refresh your JomSocial dashboard. If error is gone, good, if other error is thrown (most likely on a large and dirty databases) just repeat the same process.

Second issue

Third issue

See Also