Public data not shown

The data shown in the cached values clearly changes after the update, here are the previous and after values:

dates previous
a:1:{i:1058893055930;a:5:{s:4:"type";s:8:"birthday";s:10:"visibility";s:8:"unlisted";s:4:"date";s:10:"2013-11-20";s:5:"order";i:0;s:9:"preferred";b:0;}}
dates after
a:1:{s:32:"d48e7b5f0495de9616c62604483ced99";a:6:{s:4:"type";s:8:"birthday";s:10:"visibility";s:8:"unlisted";s:4:"date";s:10:"2013-10-31";s:2:"id";s:3:"434";s:5:"order";i:0;s:9:"preferred";b:0;}}

And pretty much the same with email, phone, addresses.

In the case of a contact that shows the dates correctly (not showing unlisted dates), the serials are:
date previous
a:1:{s:32:"4889aec3304e1d0fa03ecaea16960a1c";a:6:{s:4:"type";s:8:"birthday";s:10:"visibility";s:8:"unlisted";s:4:"date";s:10:"2013-05-21";s:2:"id";s:3:"445";s:5:"order";i:0;s:9:"preferred";b:0;}}
date after
a:1:{s:32:"2c8e778e108d48c298c1157796ca44b9";a:6:{s:4:"type";s:8:"birthday";s:10:"visibility";s:8:"unlisted";s:4:"date";s:10:"2013-05-21";s:2:"id";s:3:"445";s:5:"order";i:0;s:9:"preferred";b:0;}}

So it is quite obvious that the error comes from the way that the serialize has been made: some of the data has been storaged as integer ?!?!
That would explain why the update solves the problem.

We have confirmed that the new values stored (new contact) are done as string, but if we repeat the same process: make a new contact (public with one unlisted date), save it, we get this cached date:
a:1:{s:12:"439828048886";a:5:{s:4:"type";s:8:"birthday";s:10:"visibility";s:8:"unlisted";s:4:"date";s:10:"2013-09-25";s:5:"order";i:0;s:9:"preferred";b:0;}}
It shows perfectly, but if we update again (no modifications) the cached value changes to:
a:1:{s:32:"74469e7a4f9b2c5ece4e79227cd68b72";a:6:{s:4:"type";s:8:"birthday";s:10:"visibility";s:8:"unlisted";s:4:"date";s:10:"2013-09-25";s:2:"id";s:3:"512";s:5:"order";i:0;s:9:"preferred";b:0;}}

If you put one line over the other you can see that a couple of new string datas are added in the update: the strings “id” and “512”, which is the id value in the wp_connections_date table. The frontend works perfectly both previously and afterwards the update, but that change appears. Should it be that way?

We still think that it is related somehow to the upgrade, but anyway this gives us a clear way to solve the problem: do you have any php code for mass updating?

Ok, first your ideas:
– “after you changed the cache flag, did you check while logged out or in?” : Logged out, I usually try to work with Firefox in the backend, while opening the frontend in the damned IE. Even more, the Super Admin role has all the connectiosn permissions turned off, so he doesn’t see the unlisted ones.

– ” which version where you running that worked and which version did you update to where it stopped working?”: I am not sure that is the problem, it is the only thing that has changed that could access the connections tables in the DB, as the changes we have made are for the multilanguage support and how categories are shown. We went from cMap 2.0.10 in connections 0.7.3.1 to cMap 3.0.3 in connections 0.7.6.6 .

As for the bulk update: we are trying this in a local copy of the website, so we do not have the problems you foresaw. Another thing: we have returned to your code, just in case our changes are interfiring in some way that we cannot see.
As we have the 0.7.6.6 version, we changed the code to the following one (correct us if something is wrong):

function cnBulkUpdate() {
global $connections;
	// X == the entry ID to update.
	$results = $connections->retrieve->entries( array( 'id' => 44 ) );

	foreach ( $results as $row ) {
		$entry = new cnEntry();
		$entry->set( $row->id );
		$entry->update();
	}
}
add_action( 'graphene_before_page_content', 'cnBulkUpdate' );

The graphene action is part of the graphene theme, and it is loaded just before the content (obviously, as the name says).

Result after the update:
– in the Frontend: no change, disgracefully. Date is shown, public phones and emails are not shown.
– in the Backend: the unlisted date is duplicated, but with Public visibility. So now the contact has tow dates, exactly the same except for the visibility. And the public visibility is wrong, obviously. Interestingly this problem does not happen in the unlisted phones or emails.

Now, if I click the Update button in the backend everything is solved (except that now the new public date – the wrong duplicated date – appears).

I am trying to see possible differences between the update method and the action of the button, and I do not see any… any ideas?

Trying that I realized that the date shown is the birthday field, not the birthday date (either cached or its own table). In the example of http://connections-pro.com/documentation/template/cmap/option/ you have show_birthday=’false’ , although it is not described below.
I tried both show_birthday=’false’ and show_birthday=false in the code, and doesn’t change.
I commented out the birthday lines (class.entry.php, lines 2570-2582) and dates are not shown anymore. So that’s why cached false does not work!

Anyway, my solution: comment the birthday block and cached FALSE. It finally works!. I must have done something wrong in the process, because I remember trying cached FALSE and phones did not show…

OK, Steven, thank you very much for your attention. You have helped us and sincerely your code is great, your layering is impressive! I hope we do not need to bother you anymore :)