Unable to save in the Administrapage builder: Classes/BxDolSession.php

Everytime we go into the page builder, we get this error:

Warning: Cannot modify header information - headers already sent by (output started at /home/site/public_html/inc/classes/BxDolPageViewAdmin.php:79) in/home/site/public_html/inc/classes/BxDolSession.php on line 44

We're unable able to save any data in the page builder. 

Any help would be greatly appreciated. Thanks.

are you running a custom template? is this behavior the same with uni?

have you hacked at this file with any editor? --> /BxDolPageViewAdmin.php

check that file, at the end and see if there are no extra CRLF's after the closing ?> tag

Ok, that's just horsepucky!

I found an extra CR at the end of mine in townation and it's exactly the same as the bsdolpageviewadmin.php file in ALL my other sites!

I removed the space as it called for and there was no change. In fact, I systematically wen through ALL the pages listed in the error as well as the index.php files and the problem still exists.

What's the real reason for the error? Everything I can find tells me that the extra CR should have absolutely NO EFFECT WHATSOEVER!

I have been looking at this nonsensical error for MONTHS and it's really starting to tick me off. I don't want to attack the symptom, i would very much like to find the real problem. Is anybody on this site up to the task? It's starting to look like no one is....

I have another question. How cone NONE of the bxdolcache***.php files have a closing php tag?

I had recently learned that closing PHP tags are apparently optional.

The closing tag of a PHP block at the end of a file is optional, and in some cases omitting it is helpful when using include() or require(), so unwanted whitespace will not occur at the end of files, and you will still be able to add headers to the response later. It is also handy if you use output buffering, and would not like to see added unwanted whitespace at the end of the parts generated by the included files.

However i just consider things such as short open tags and leaving out the closing tag bad programming. But thats just me. According to a SitePoint poll, a third of PHP developers did not use a closing tag, a third considered that bad practice, and third didn’t realize it could be omitted.

In almost all cases it does have no effect whatsoever.

I write mods. And take deanos tools for example which is used on hundreds of sites.

Believe it or not i had extra lines in several of the files when it was first released and it ran fine on most sites. On other it would fail with that stupid error. So who the hell knows. Specific version of PHP. Perhaps a slight difference in how PHP is compiled on the server, who knows. But i could not come up with a reason it would run with the white space on most sites but in others it would not.

Anyhow. Usually this means that there has been some kind of output sent to the browser before PHP was able to send the browser the headers.

Now in most cases the whitespace issue is the cause. But it is not the only possible cause. There could be an installed mod that is interfering with the output to the browser. Perhaps one of dolphins events.

But i would start with the editor your using to remove the white space.

Does your editor show single spaced or double spaced lines when viewing the file.

Is your editor configured to save the file in Unix or DOS format. In other words. A CR-LF at the end of a line instead of just a LF

Is the editor configured to save the file in ASCII or UTF8 format. If UTF8 is it saving a BOM marker at the end of the file.

There could be a number of reasons for the error.

So giving you an answer to the question what is the real reason for the error is really not possible.

Well. You are the only one that tried. Kudos for that.

I just use the code editor in cpanel mostly. I was concerned there might have been an issue so I even tried it using the straight up text editor. Same results.

My index page is pretty heavily changed. I have a promo block mod and a few other things but I don't see how they could cause this. This is my 7.06 site. None of my 7.08's have this issue at all