[Phpmyadmin-devel] "Cannot modify header information" and strange character anomalies.
Hey all, I'm having a couple issues that I can't quite pin down. They aren't show-stoppers by any stretch of the imagination, but they're still something I need to work out before the end of the summer. I created a notification panel that displays the various structures created or altered on import. To accomplish this I used the PMA_Message::notice class to build a string of html, and then ->display() it, as should be done, I believe. When this panel is displayed, there are several warnings regarding not being able to modify header information, header info. already sent, etc. I know what this means and mostly understand how PHP handles headers, but I'm not entire sure why it is throwing these errors. Upon a successful import, there is a PMA_Message::success element displayed under the navigation buttons that tells how many queries were executed, etc., and that doesn't cause header problems. I imagine this is cropping up because of how I am using PMA_Message, although I'm using it in ways demonstrated elsewhere. Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure. Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg If anyone has some insight into these issues, I would greatly appreciate any direction you could give. -Derek
Derek Schaefer a écrit :
Hey all,
I'm having a couple issues that I can't quite pin down. They aren't show-stoppers by any stretch of the imagination, but they're still something I need to work out before the end of the summer.
I created a notification panel that displays the various structures created or altered on import. To accomplish this I used the PMA_Message::notice class to build a string of html, and then ->display() it, as should be done, I believe. When this panel is displayed, there are several warnings regarding not being able to modify header information, header info. already sent, etc. I know what this means and mostly understand how PHP handles headers, but I'm not entire sure why it is throwing these errors. Upon a successful import, there is a PMA_Message::success element displayed under the navigation buttons that tells how many queries were executed, etc., and that doesn't cause header problems. I imagine this is cropping up because of how I am using PMA_Message, although I'm using it in ways demonstrated elsewhere.
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
-Derek
Are you sure there is not caused by some "echo" debugging statement you left in the code, or some misplaced blank line outside of the PHP tags? Also, if you comment out the calling of PMA_Message, you get rid of the warnings? The strange characters will disappear when your warnings disappear. Finally, does your code in branch/gsoc/derek produce this behavior? -- Marc Delisle http://infomarc.info
On Tue, Jul 14, 2009 at 3:10 PM, Marc Delisle<marc@infomarc.info> wrote:
Derek Schaefer a écrit :
Hey all,
I'm having a couple issues that I can't quite pin down. They aren't show-stoppers by any stretch of the imagination, but they're still something I need to work out before the end of the summer.
I created a notification panel that displays the various structures created or altered on import. To accomplish this I used the PMA_Message::notice class to build a string of html, and then ->display() it, as should be done, I believe. When this panel is displayed, there are several warnings regarding not being able to modify header information, header info. already sent, etc. I know what this means and mostly understand how PHP handles headers, but I'm not entire sure why it is throwing these errors. Upon a successful import, there is a PMA_Message::success element displayed under the navigation buttons that tells how many queries were executed, etc., and that doesn't cause header problems. I imagine this is cropping up because of how I am using PMA_Message, although I'm using it in ways demonstrated elsewhere.
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
-Derek
Are you sure there is not caused by some "echo" debugging statement you left in the code, or some misplaced blank line outside of the PHP tags? Also, if you comment out the calling of PMA_Message, you get rid of the warnings?
That was my first though, as I had left some around before I had created the notification panel and they caused this same problem, but I've searched for echo's, print_r's, printf's, etc. etc., and have found nothing. No extra lines out side PHP tags. If I comment out the message section the problem goes away. (The message section is in import.lib.php) Even if I just comment out the display() call on the message the problem goes away.
The strange characters will disappear when your warnings disappear.
Finally, does your code in branch/gsoc/derek produce this behavior?
Yes, it does, as it is an exact replica of my working copy.
-- Marc Delisle http://infomarc.info
------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Derek Schaefer a écrit :
On Tue, Jul 14, 2009 at 3:10 PM, Marc Delisle<marc@infomarc.info> wrote:
Derek Schaefer a écrit :
Hey all,
I'm having a couple issues that I can't quite pin down. They aren't show-stoppers by any stretch of the imagination, but they're still something I need to work out before the end of the summer.
I created a notification panel that displays the various structures created or altered on import. To accomplish this I used the PMA_Message::notice class to build a string of html, and then ->display() it, as should be done, I believe. When this panel is displayed, there are several warnings regarding not being able to modify header information, header info. already sent, etc. I know what this means and mostly understand how PHP handles headers, but I'm not entire sure why it is throwing these errors. Upon a successful import, there is a PMA_Message::success element displayed under the navigation buttons that tells how many queries were executed, etc., and that doesn't cause header problems. I imagine this is cropping up because of how I am using PMA_Message, although I'm using it in ways demonstrated elsewhere.
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
-Derek Are you sure there is not caused by some "echo" debugging statement you left in the code, or some misplaced blank line outside of the PHP tags? Also, if you comment out the calling of PMA_Message, you get rid of the warnings?
That was my first though, as I had left some around before I had created the notification panel and they caused this same problem, but I've searched for echo's, print_r's, printf's, etc. etc., and have found nothing.
No extra lines out side PHP tags.
If I comment out the message section the problem goes away. (The message section is in import.lib.php) Even if I just comment out the display() call on the message the problem goes away.
The strange characters will disappear when your warnings disappear.
Finally, does your code in branch/gsoc/derek produce this behavior?
Yes, it does, as it is an exact replica of my working copy.
-- Marc Delisle
Tried with your branch on my test machine to replicate the error message by clicking on Import (at the server level) and importing a short .sql file containing a USE statement and a create table definition. I could not see the warnings. Please describe the step-by-step. Marc -- Marc Delisle http://infomarc.info
Marc Delisle a écrit :
Derek Schaefer a écrit :
On Tue, Jul 14, 2009 at 3:10 PM, Marc Delisle<marc@infomarc.info> wrote:
Derek Schaefer a écrit :
Hey all,
I'm having a couple issues that I can't quite pin down. They aren't show-stoppers by any stretch of the imagination, but they're still something I need to work out before the end of the summer.
I created a notification panel that displays the various structures created or altered on import. To accomplish this I used the PMA_Message::notice class to build a string of html, and then ->display() it, as should be done, I believe. When this panel is displayed, there are several warnings regarding not being able to modify header information, header info. already sent, etc. I know what this means and mostly understand how PHP handles headers, but I'm not entire sure why it is throwing these errors. Upon a successful import, there is a PMA_Message::success element displayed under the navigation buttons that tells how many queries were executed, etc., and that doesn't cause header problems. I imagine this is cropping up because of how I am using PMA_Message, although I'm using it in ways demonstrated elsewhere.
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
-Derek Are you sure there is not caused by some "echo" debugging statement you left in the code, or some misplaced blank line outside of the PHP tags? Also, if you comment out the calling of PMA_Message, you get rid of the warnings? That was my first though, as I had left some around before I had created the notification panel and they caused this same problem, but I've searched for echo's, print_r's, printf's, etc. etc., and have found nothing.
No extra lines out side PHP tags.
If I comment out the message section the problem goes away. (The message section is in import.lib.php) Even if I just comment out the display() call on the message the problem goes away.
The strange characters will disappear when your warnings disappear.
Finally, does your code in branch/gsoc/derek produce this behavior? Yes, it does, as it is an exact replica of my working copy.
-- Marc Delisle
Tried with your branch on my test machine to replicate the error message by clicking on Import (at the server level) and importing a short .sql file containing a USE statement and a create table definition. I could not see the warnings. Please describe the step-by-step.
Marc
Ok, I guess I need to import XML, for example :) -- Marc Delisle http://infomarc.info
Derek Schaefer a écrit :
Hey all,
I'm having a couple issues that I can't quite pin down. They aren't show-stoppers by any stretch of the imagination, but they're still something I need to work out before the end of the summer.
I created a notification panel that displays the various structures created or altered on import. To accomplish this I used the PMA_Message::notice class to build a string of html, and then ->display() it, as should be done, I believe. When this panel is displayed, there are several warnings regarding not being able to modify header information, header info. already sent, etc. I know what this means and mostly understand how PHP handles headers, but I'm not entire sure why it is throwing these errors. Upon a successful import, there is a PMA_Message::success element displayed under the navigation buttons that tells how many queries were executed, etc., and that doesn't cause header problems. I imagine this is cropping up because of how I am using PMA_Message, although I'm using it in ways demonstrated elsewhere.
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
-Derek
Derek, I don't think that putting direct HTML tags in your messages is supported by this function. See the valid syntax in Message.class.php, in the decodeBB function. -- Marc Delisle http://infomarc.info
On Tue, Jul 14, 2009 at 5:04 PM, Marc Delisle<marc@infomarc.info> wrote:
Derek Schaefer a écrit :
Hey all,
I'm having a couple issues that I can't quite pin down. They aren't show-stoppers by any stretch of the imagination, but they're still something I need to work out before the end of the summer.
I created a notification panel that displays the various structures created or altered on import. To accomplish this I used the PMA_Message::notice class to build a string of html, and then ->display() it, as should be done, I believe. When this panel is displayed, there are several warnings regarding not being able to modify header information, header info. already sent, etc. I know what this means and mostly understand how PHP handles headers, but I'm not entire sure why it is throwing these errors. Upon a successful import, there is a PMA_Message::success element displayed under the navigation buttons that tells how many queries were executed, etc., and that doesn't cause header problems. I imagine this is cropping up because of how I am using PMA_Message, although I'm using it in ways demonstrated elsewhere.
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
-Derek
Derek, I don't think that putting direct HTML tags in your messages is supported by this function. See the valid syntax in Message.class.php, in the decodeBB function.
Well, I gave it a shot to no avail. I even tried something as simple as: PMA_Message::notice('Test')->display(); ... and it still produced the same problem. I'm thinking PMA just doesn't react well to functions printing anything to screen that deep in the include tree, or at least that's my guess at this point. If that's the case I'll need to find a work around. I'll look into this some more tomorrow. -Derek
-- Marc Delisle http://infomarc.info
------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Derek Schaefer a écrit :
On Tue, Jul 14, 2009 at 5:04 PM, Marc Delisle<marc@infomarc.info> wrote:
Derek Schaefer a écrit :
Hey all,
I'm having a couple issues that I can't quite pin down. They aren't show-stoppers by any stretch of the imagination, but they're still something I need to work out before the end of the summer.
I created a notification panel that displays the various structures created or altered on import. To accomplish this I used the PMA_Message::notice class to build a string of html, and then ->display() it, as should be done, I believe. When this panel is displayed, there are several warnings regarding not being able to modify header information, header info. already sent, etc. I know what this means and mostly understand how PHP handles headers, but I'm not entire sure why it is throwing these errors. Upon a successful import, there is a PMA_Message::success element displayed under the navigation buttons that tells how many queries were executed, etc., and that doesn't cause header problems. I imagine this is cropping up because of how I am using PMA_Message, although I'm using it in ways demonstrated elsewhere.
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
-Derek Derek, I don't think that putting direct HTML tags in your messages is supported by this function. See the valid syntax in Message.class.php, in the decodeBB function.
Well, I gave it a shot to no avail. I even tried something as simple as:
PMA_Message::notice('Test')->display();
... and it still produced the same problem.
I'm thinking PMA just doesn't react well to functions printing anything to screen that deep in the include tree, or at least that's my guess at this point. If that's the case I'll need to find a work around.
I'll look into this some more tomorrow.
Try adding this before you call the display method: require_once "./libraries/header.inc.php"; but the output will look curious, just over the server links. And you'll need to follow my previous advice about using proper codes, for example [i] instead of <i>. -- Marc Delisle http://infomarc.info
Hi Dne Tue, 14 Jul 2009 14:45:10 -0500 Derek Schaefer <derek.schaefer@gmail.com> napsal(a):
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
You show message too early, you should do it after showing links (at least this is where we show all messages, so you should keep the consistency). The strange chars are from gzip compression. -- Michal Čihař | http://cihar.com | http://phpmyadmin.cz
Michal Čihař a écrit :
Hi
Dne Tue, 14 Jul 2009 14:45:10 -0500 Derek Schaefer <derek.schaefer@gmail.com> napsal(a):
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
You show message too early, you should do it after showing links (at least this is where we show all messages, so you should keep the consistency).
Yes. Instead of displaying it in your lower function, try to pass $message to a higher function, then let PMA_showMessage() which is defined in common.lib.php do its job. -- Marc Delisle http://infomarc.info
Thank you both, Marc and Michal, for your help in tracking this down. With those modifications it no longer throws any back traces or causes any character anomalies. Now that I look at it, it does strike me as having rather awkward placement (above the horizontal links bar, etc.). What I'm thinking of doing instead is to roll it into the existing "successful import" message, so like the following: http://downloads.moonlapse.org/pma/import_interface2.jpg ... and normal imports not aided by my library extensions will still be displayed normally: http://downloads.moonlapse.org/pma/import_interface1.jpg I believe it just makes more sense this way. Let me know what you think. -Derek On Wed, Jul 15, 2009 at 3:05 AM, Marc Delisle<marc@infomarc.info> wrote:
Michal Čihař a écrit :
Hi
Dne Tue, 14 Jul 2009 14:45:10 -0500 Derek Schaefer <derek.schaefer@gmail.com> napsal(a):
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give.
You show message too early, you should do it after showing links (at least this is where we show all messages, so you should keep the consistency).
Yes. Instead of displaying it in your lower function, try to pass $message to a higher function, then let PMA_showMessage() which is defined in common.lib.php do its job.
-- Marc Delisle http://infomarc.info
------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Derek Schaefer a écrit :
Thank you both, Marc and Michal, for your help in tracking this down. With those modifications it no longer throws any back traces or causes any character anomalies.
Now that I look at it, it does strike me as having rather awkward placement (above the horizontal links bar, etc.). What I'm thinking of doing instead is to roll it into the existing "successful import" message, so like the following:
Your screenshot looks fine.
... and normal imports not aided by my library extensions will still be displayed normally:
http://downloads.moonlapse.org/pma/import_interface1.jpg
I believe it just makes more sense this way. Let me know what you think.
-Derek
On Wed, Jul 15, 2009 at 3:05 AM, Marc Delisle<marc@infomarc.info> wrote:
Michal Čihař a écrit :
Hi
Dne Tue, 14 Jul 2009 14:45:10 -0500 Derek Schaefer <derek.schaefer@gmail.com> napsal(a):
Also, whenever the aforementioned notification panel is displayed, strange character anomalies appear at the very bottom of the import page. They change every time, but always take the form ",�<��Y". My best guess is that it is related the the header issues, but until I can get rid of them I can't know for sure.
Here is a screenshot of the character anomaly and a couple of the header backtraces: http://downloads.moonlapse.org/pma/import_issues.jpg
If anyone has some insight into these issues, I would greatly appreciate any direction you could give. You show message too early, you should do it after showing links (at least this is where we show all messages, so you should keep the consistency).
Yes. Instead of displaying it in your lower function, try to pass $message to a higher function, then let PMA_showMessage() which is defined in common.lib.php do its job.
-- Marc Delisle http://infomarc.info
-- Marc Delisle http://infomarc.info
Hi Dne Wed, 15 Jul 2009 12:55:53 -0500 Derek Schaefer <derek.schaefer@gmail.com> napsal(a):
Thank you both, Marc and Michal, for your help in tracking this down. With those modifications it no longer throws any back traces or causes any character anomalies.
Now that I look at it, it does strike me as having rather awkward placement (above the horizontal links bar, etc.). What I'm thinking of doing instead is to roll it into the existing "successful import" message, so like the following:
Yes, this looks good. -- Michal Čihař | http://cihar.com | http://phpmyadmin.cz
participants (3)
-
Derek Schaefer -
Marc Delisle -
Michal Čihař