Saving State Through Page Reloads (like form submissions)
Caleb G - August 28, 2008 - 19:18
| Project: | Drupal For Firebug |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | populist |
| Status: | active |
Jump to:
Description
Wow - great module! I've had a lot of fun playing with it today.
One of the things I'm really excited about is the potential for placing permanent debug messages in various thing with something like this:
if (module_exists('drupalforfirebug')) {
firep($myvariable);
}If the person viewing the page has the module installed and proper permission, they will always be able to view the output within the "General" tab. This is much handier than having to comment in, and then comment out a print_r statement for instance (something that will show output to all users, of course). This worked great in all instance I tried it except for form submissions. I'm sure this has something to do with a relationship between js/php and persistence between page loads.
Any ideas/comments?
#1
The ability to have permanent debugging messages should be no problem regardless of process, but there may be some issues with how the information is being saved across form submissions. Renaming the issue around that.
#2
The only way I know to solve this is by storing information in the user session ("this" being the issue of persisting data between form submissions). I'm know how to do this in general, but not in the context of firbugfordrupal (since I'm not very familiar with the code). Can take a look at doing that, or likewise if anyone else has any ideas to discuss and/or if you want to take a swing at it because you're more familiar with the code base.
#3
This issue is similar to #434398: firep() Not Sending to General Log During Form Validation which I think we can create a global solution for both.