1 user_11055 Mar 17, 2009 20:05
3 user_11055 Mar 17, 2009 21:53
Hi Walter
Thanks for getting back to me.
Walter wrote:
Great, I've never seen a so long browser name!
You can change the lenght of user_browser on database... or you can edit the file blogs/inc/sessions/model/_hit.class.php and change
return $this->user_agent;
(
in line 707 in function get_user_agentto
return substr($this->user_agent,0,200);
Not really tested ;)
I tried changing the column length to 250 by setting VARCHAR[250], but I would get an error in doing so.
I will give the substr option a whirl.
What does the team think would be the longer term architectural solution? Since I am on the ground floor, I don't want to make a change that will give problems with future upgrades to the product.
Karl
4 waltercruz Mar 17, 2009 21:54
I'm talking with blueyed right now, will bring that issue to the team.
5 afwas Mar 18, 2009 01:02
Hi karlgo,
use VARCHAR(255) not [255] if you change th DB from commandline. Else use a tool like PhpMyAdmin.
I wonder why it picked up so much detail. Either some devver has changed the code to do so and forgot the change in DB to store it or PHP has changed through the years and picked up this detail.
Do watch out, this table tends to grow huge over time if you don't prune it in time. From a structural standpoint I'd say store only what's useful so strip the info before it's stored (browser, platform).
The substr should work also.
Good luck
6 user_11055 Mar 18, 2009 18:56
Thanks all for getting back with me.
Since I need to get things up and running, I chose to change the column length to 255 and all is well.
I'll be watching for what the long term solution is.
Thanks,
Karl
Great, I've never seen a so long browser name!
You can change the lenght of user_browser on database... or you can edit the file blogs/inc/sessions/model/_hit.class.php and change
(
in line 707 in function get_user_agent
to
Not really tested ;)