Download & Extend

"An HTTP Error 200 Occured" when using Actions 1.x

Project:Flag
Version:6.x-1.0-beta5
Component:Code
Category:bug report
Priority:critical
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

I'm using the template snippet from the other issue thread in my theme, and its showing up just fine. but every time I flag or unflag my test node, I get a popup error saying:

"An HTTP Error 200 Occured" followed by a URL. Here's the flag URL:

http://www.mydomain.com/flag/flag/myflagtype/node/nodeID?destination=%2F...

How do we fix this?

Comments

#1

Status:active» postponed (maintainer needs more info)

An 'http error 200' occurs because of some PHP error on the page. That is the real error. To see the PHP error message, instead of this javascript popup box, either click the flag link when javascript is turned off, or click the link with the right mouse button (and 'open in new window'). Please try this and let me know what happens.

#2

For me the error was a call to undefined function _actions_get_hook_aids() in flag.module line 823. I had an old version (0ct 07) of actions 1.x-dev. I upgraded to 2.5 and all was well.

#3

Status:postponed (maintainer needs more info)» fixed

Andy, thank you for the info.

Fixed.
http://drupal.org/cvs?commit=128026

#4

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

#5

Title:"An HTTP Error 200 Occured"» "An HTTP Error 200 Occured" when using Actions 1.x

#6

Version:5.x-1.0-beta3» 6.x-1.0-beta5
Status:closed (fixed)» active

same issue on d6 when using actions "send to nodequeue" and "redirect to url" on same flag. The node gets sent to the appropriate nodequeue, but the redirect url doesn't work.

Thank you so much for your module, it is wonderful! We really appreciate all the hard work. I did not know if I should update to the latest dev release or not.

#7

g76, the redirect URL doesn't work because the AJAX request is the one that gets redirected (since the user never leaves the page). In order to work with Redirect to URL, you'd need to not use AJAX with the link. Unfortunately this isn't yet an option, but the feature is being worked on here #160519: Allow admin to select Ajax or non-ajax behaviour per Bookmark type. Until then you won't be able to use the Redirect to URL action.

#8

Status:active» fixed

The per-flag link behavior is now in. You can update to the latest dev version to correct the problem with "redirect to URL" actions by switching the link type to "Normal" instead of "JavaScript toggle". There's nothing more we can do to make the action work with AJAX, as we'd need to write an entirely new action that supported AJAX responses.

#9

thanks so much!

#10

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

nobody click here