FYI: rpx_token causing 500 error with All In One Events Calendar | WordPress.org

Resolved takuya
(@takuya)

11 years ago

Janrain Engage (1.1.1) is adding non necessary parameter (rpx_token) to All In One Events Calendar generated pages, causing 500 server errors when those pages are accessed.

http://example.com/events/tag_ids:154/?action=rpx_token

Without the parameter, the site is accessible. I hope both teams work together to fix this problem. I also posted on All In One Event Calendar support discussions.

http://wordpress.org/support/topic/fyi-conflict-with-janrain-engage-plugin?replies=1

http://wordpress.org/extend/plugins/rpx/

Viewing 3 replies - 1 through 3 (of 3 total)

juanm_janrain
(@juanm_janrain)

11 years ago

Hi, wpmubp.org —

I downloaded the All in One Events Calendar plugin (Standard Edition) and I’m unable to replicate the issue you’re seeing in browsing events or tag pages, or logging in and out of Engage through those pages. Which All in One version are you using?

Thread Starter takuya
(@takuya)

11 years ago

I’m using 1.9.5 standard edition, and I found the problem from Google Webmaster Tools. I don’t know how to locate this problem only by using WordPress…

Thread Starter takuya
(@takuya)

11 years ago

I found this entry on my error log.

mod_fcgid: stderr: PHP Fatal error: Call to undefined method Ai1ec_Calendar_Controller::get_rpx_token_view() in /home/user/example.com/public_html/wp-content/plugins/all-in-one-event-calendar/app/controller/class-ai1ec-calendar-controller.php on line 74

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘FYI: rpx_token causing 500 error with All In One Events Calendar’ is closed to new replies.

Tags

conflict

In: Plugins
3 replies
2 participants
Last reply from: takuya
Last activity: 11 years ago
Status: resolved