Deltanic

What? I'm not saying PW is 'failing' on me, I'm saying I don't need both xDebug and PW exception messages. This has nothing to with my code, or how to handle an exception. Interesting. I haven't got any luck so far. As you can see in the picture in the OP, my xDebug messages are all put in a single message, rather than having the callstack. Considering PW does provide the callstack well formatted, my initial thought was to disable PW exceptions and have it all being displayed through xDebug. Still not sure what I could do to get my xDebug messages right, but to me it looks like PW is somewhere having an exception and/or error handler that throws its own error message.

Bumping some more. It really should be possible to disable ProcessWire's exception/error handling..

Recently, I developed something locally after which I had to move files to another place, with another database. Shouldn't be much of an issue, since I also migrated the database. However, I cannot login into the control panel since all it does is display a white page. The site itself works fine though. I do want to resolve this without headless searching for the problem. What could be the cause of this, and what do I do to resolve it?

Bumping due to desperate need.

Is it possible to disable ProcessWire's custom exceptions? I'm building an abstraction layer ontop of ProcessWire and would love to use xDebug. However, as PW currently works, this isn't really going well as seen below: Both messages display and xDebug isn't of any use. So is it possible to disable PW error and exception messages, and if so, how? Thanks in advance.

Unfortunately, deleting the cache did not have any effect. So far I've been unable to find the cause of all this, but since I did manage to get everything working again, I'm not going to bother myself with this issue any longer. Next time I'm gonna be a bit more careful, I guess

I managed to reproduce the problem with steps. Create a module (or use an existing one and skip to step 3) Refresh modules in the controlpanel so PW finds the module. Give the module an error, in my case, an unimplemented abstract method. Refresh the control panel. Get the error message. Fix the error. Refresh again. And witness PW not sending any data. More specifically, my steps, performed in the shopping cart module: Edit PaymentAbstract, add new abstract methods. Forget to update PaymentExample.module. PW notifies me about the issue. Fix the issue. Refresh, and PW stopped working. Code: - Edited PaymentAbstract.php - MollieExtension.php - Mollie can be found here. - Added PaymentIdeal.php (accidentally named it .php instead of .module) - Edited PaymentInvoice.module And again the cache got corrupted. Emptying cache does not solve it, we had to revert to an older cache.

It's clearly the module where things went mad. Adding the first one was fine, the second one caused the problem. The problem was however in the database. The caches table seemed to be corrupted, having empty JSON strings. Yes, we reverted PW as well. But this was just to assure no one else could've edited the core (which would be very stupid). There were no alterations in the core. The templates are never loaded. I deleted the .module files, and the corresponding rows in the database without luck. The error was somewhere in the Modules::load() method, but I don't know exactly what. Even after removing the modules. So it looks like the caches were corrupted. This is strange though, because I also disabled dbCache. This makes me still unsure what caused the issue, and doubtful if I should try adding the module again (and finish what I was doing). Is there a way to ensure I won't get this issue again? Could I have messed up something myself, which I shouldn't do the next time? From the docs: I renamed a module before even installing it (So essentially "removing" for a system that is not aware of filechanges). Could that have been it?

Unfortunately this is not an htaccess issue. None of these steps seemed to help. Well, I was busy with a shopping cart module: http://modules.processwire.com/modules/shopping-cart/ It had to be slightly altered to work with some payment service we use. For this, I added a .module file to extend functionality. This worked fine. After that I basically made a copy of that .module file, and slightly altered it (so no duplicate class/filenames or whatsoever). Thats where things went down. Yes, debug is on. PHP: 5.3.26, MySQL: 5.5.20. Apache logs tell nothing useful. The error log is empty (apart from some 404's from a few days earlier) and the access log has nothing useful either. We just reverted the database to the one of a week old, which seems to work. So it seems to be an issue with the modules. Still curious to know what causes this, to prevent it the next time. Or better yet, how to fix the up to date database. Reverting the database is quite a big deal, considering the work that has been done the past week.

Hello, After working with some modules ProcessWire suddenly stopped working. It's not sending back any data to the browser. No error log, no debug, no PHP errors, nothing. I've been trying to debug the problem, and somewhere in the load() method in wire/core/Modules.php everything goes wrong. I'm unable to find the exact clause though. We have even reverted all code (both from the site and from PW) to a week old, at the time working backup. However, even this does not solve the issue so we suspect there is something wrong in the database. The problem is I don't know where to look. The controlpanel does not work either. We are running ProcessWire 2.5. Is there anything I could to to solve this issue?