JomSocial 3.1 Common Upgrade Issues - Revision history

Sinisakrisan: /* Same Error Having a Gender Value */

2013-12-05T07:58:47Z

‎Same Error Having a Gender Value

2013-12-05T07:58:01Z

‎Same Error Having a Gender Value

2013-12-05T07:47:33Z

‎Failed to parse time string

2013-12-05T03:50:18Z

‎See Also

2013-12-05T03:48:57Z

‎Third issue

2013-12-05T03:48:20Z

‎Second issue

2013-12-05T03:22:13Z

‎Failed to parse time string

2013-12-05T03:21:23Z

‎Failed to parse time string

2013-12-05T02:51:39Z

‎Failed to parse time string

2013-12-05T02:11:54Z

@@ Line 26: / Line 26: @@
 At times, you might experience the same error being unable to parse Gender value
 <syntaxhighlight lang="php">
-this? DateTime::__construct() [datetime.--construct]: Failed to parse time string (Male) at position 0 (M)
+DateTime::__construct() [datetime.--construct]: Failed to parse time string (Male) at position 0 (M)
 </syntaxhighlight>
 <br/>

← Older revision		Revision as of 07:58, 5 December 2013
Line 24:		Line 24:

	===Same Error Having a Gender Value===		===Same Error Having a Gender Value===
		+	At times, you might experience the same error being unable to parse Gender value
		+	<syntaxhighlight lang="php">
		+	this? DateTime::__construct() [datetime.--construct]: Failed to parse time string (Male) at position 0 (M)
		+	</syntaxhighlight>
		+	<br/>
		+	This simply implies that scrip fetched gender value instead Birthdate field value<br />
		+	To correct it, ensure that
		+	#field code for gender field is '''FIELD_GENDER'''
		+	#Field code for birthdate field is '''FIELD_BIRTHDATE'''
		+	:::[[File:Fieldnames.png]]

	==Memberlocation Map Shows Doubled values==		==Memberlocation Map Shows Doubled values==

@@ Line 22: / Line 22: @@
 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.<br />
 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.
 ==Memberlocation Map Shows Doubled values==

← Older revision		Revision as of 03:50, 5 December 2013
Line 38:		Line 38:
	This query will replace all values stored as '''India''' into proper, translatable value and you will get rid of the doubled entries for specific country<br />		This query will replace all values stored as '''India''' into proper, translatable value and you will get rid of the doubled entries for specific country<br />
	You can see the language strings for all countries in ROOT/langauges/en-GB/en-GB.com_community_country.ini file		You can see the language strings for all countries in ROOT/langauges/en-GB/en-GB.com_community_country.ini file
−
−	~~==See Also==~~

@@ Line 38: / Line 38: @@
 This query will replace all values stored as '''India''' into proper, translatable value and you will get rid of the doubled entries for specific country<br />
 You can see the language strings for all countries in ROOT/langauges/en-GB/en-GB.com_community_country.ini file
 ==See Also==

@@ Line 20: / Line 20: @@
 You should see similar result like on the picture bellow
 :::[[File:Phpmyadminseach3.png]]
-You can now either delete the record, or browse it further. Lets just clivk on '''Delete'''. We will leave up to you if you want to browse it further.<br />
+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.<br />
 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.

@@ Line 5: / Line 5: @@
 :::[[File: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'''<br />
-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 can never be an actual date <br />
+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 <br />
 In this case, 1987 is the year, 34 is the month and 54 is the day. Obviously, the date here is wrong.<br />
 It can also happen that you have completely date unrelated value like random string of characters, solution will however, be the same.
@@ Line 12: / Line 12: @@
 First, navigate to your database. You will most likely use phpMyAdmin as a common software to manage your database
 <center>{{alert|'''Note:''' The images shown bellow might differ in various versions of phpMyAdmin. If that is the case, please refer to the [http://www.phpmyadmin.net/home_page/docs.php phpMyAdmin Manual]|alert}}</center>
 ==Second issue==