Bug in timeline

The bug exists in all current 7.x builds I do believe. The bug relates to the wall/timeline. 

If a person enters a long string of text (20+ characters without space) and posts to the wall/timeline, the wall automatically adds breaks through the text string. 

To recreate this bug, log in to any boonex dolphin 7.x site and attempt to post to the timeline a string such as abcdefghijklmnopqrstuvwxyz1234567890 

You will see that after the 20th character a space is added. So instead of the output appearing as abcdefghijklmnopqrstuvwxyz1234567890  it will instead appear as abcdefghijklmnopqrs tuvwxyz1234567890 then after 35 more characters, another break is added. 

This may seem mundane to the average onlooker, but it prevents any sort of regex module from being created - for example to create a hashtag system or to autolink to peoples profiles  when their @name is mentioned on the timeline. 

This is a HUGE issue for me trying to create a custom dolphin site.

Is this a known bug?

Could anyone kindly confirm or deny this bug?

I am not sure if its a true bug or a flaw in my setup somehow (which seems very unlikely). Has anyone a fix if it is a bug? 

The problem I am having and the reason this bug is such a problem to me is that I am trying to setup a method of auto linking. I want it so anytime someone posts a url in the timeline it automatically is an active link that can be clicked. I am also trying to setup a system so when a person named using the @user it automatically links to their profile.

The problem with this bug is it screws up the url linking. For example http://www.google.com becomes http://www.google.c om and then only http://www.google.c becomes an active link... hence the problem - and google is a small url in the grander scheme of links. 

If this isn't a bug then I need to figure out what exactly is causing this on my system, because it seems to exist in every install I have tried.  

 If it is a bug, these topics should be posted in the proper place.

http://www.boonex.com/forums/forum/Dolphin-Bug-Reports-0.htm

That way AlexT might see it.

I realized that after posting here and didn't want to get the "duplicate post" speech. Also I read the forum topic of bugs and it said "for verified bug reports" so I didn't want to post something unverified. 

:)  

My analysis indicates that the actual post data as stored in the database has no spaces in it. Apparently only added when displayed in the block.

So if your performing your regex expression on the actual data as stored in the database, then this display issue should not affect it as the data itself as stored is not affected.

I am still trying to determine where the space gets added before it is displayed, however because it does not exist in the actual stored data it should not matter.

Deano, if I was sing php and writing it to the database (propably the proper way) what you are saying would be correct, but thats not what I am trying to do.

I am trying to use autolinker.js from github which reads the content from the screen. This is also why I have another post where I ask what file has the function where the wall reloaded after submitting content. I need the script to run everytime the wall has content  added to it.

If you do find what is causing that space I would be very appriciated.

Now that it has been verified should I post this in the bugs forum?

So I have been researching what could cause this problem and most of my research says its caused by one of two issues:

Either an fprint statement that adds padding or a wordwrap set to add a space instead of a break.

Looking at the code I couldn't find any fprint statements withing any of the wall module files, however I did find what appears to be a wordwrap, I just am not how to edit it if it is the problem nor where the actual value is being set.

I am looking in the BxWallTemplate.php at the getCommon function

        switch(str_replace($sPrefix, '', $aEvent['type'])) {
            case 'text':
$aVariables = array_merge($aVariables, array('post_content' => WordWrapStr($aVariables['post_content'])));
                break;

Or I could be totally looking at the wrong thing, but I am determined to solve this problem.

Fix:

In /inc/utils.inc.php

I changed:

function strmaxwordlen from 100 to 600

I changed:

function process_text_output from 100 to 600

Problem seems fixed.

This bug has been reported - http://www.boonex.com/trac/dolphin/ticket/3439

The fix - http://www.boonex.com/trac/dolphin/changeset/18418

If you need to fix it in wall only - ignore changes in files related to comments only.