We should come up with a better error handling approach.

Currently, CTools ajax throws a javascript alert the says something like "An error occurred while attempting to process /foo/bar". Since we are relying on CTools to do the ajax for us, I'm not sure we can get around that alert.

I do think that we could have a dialog_access_denied() that returns the appropriate access denied dialog, and something similar for 404's. Handling php errors could prove to be trickier, but may not be necessary outside of a development environment.

I'm open to ideas.

Comments

langworthy’s picture

I'm getting this error (An error occurred while attempting to process /en/user/login/ajax) when using the dialog_example.module and trying to login or register after submitting the form with valid data. When logging in, I stay stuck on the popup though after refreshing I am in fact logged in.

I've installed this module on a development site using i18n, open layers, and many other modules. On a stock D6 base with dependencies I do not receive the error. I've spent quite a few hours trying to find out where the problem is with no luck.

Any help would be appreciated.

zroger’s picture

it seems like your problem stems from having a multi-lingual site. I have not tested Dialog yet with locale module, but i definitely should.

Please list all modules you are using for language handling. And one other thing, please start a new issue rather than using this one.

langworthy’s picture

My apologies for not starting a new thread.

It turns out the problem was a custom hook_user() call that was doing a redirect on login.

drewish’s picture

#1048722: Legal Module seems related to this. A module sticks a drupal_goto() into hook_user() and it results in a 301 to a non-AJAX page. In that case I think it'd make sense to note the new, post-redirect URL and just redirect the browser there.

devin carlson’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Dialog 6.x is no longer supported.