RPX, WordPress, & Social Widget

3 views
Skip to first unread message

VizWorld

unread,
Mar 11, 2010, 4:36:39 PM3/11/10
to RPX Developers
HI all. I run www.VizWorld.com on WordPRess and I've been using RPX
for about a year. Works great.

Last night I decided to drop the $100 and integrate Social Widget
features, so I wanted to share my discoveries in case anyone else runs
into the same problem.

First off, a problem I've had for almost a year now is that the "Login
Via" buttons do not appear on the standard install. I have the
"automaticaly insert" _unchecked_, as I have manually added
'rpx_comment_hint(true)' in my theme in the appropriate spot. It
inserts the necessary code, but the style="display:none" hides it, and
it's never made visible. I simply hacked the PHP to remove the style
spec, and it works great. Not sure why this is an issue for me. Has
anyone else run into this?

So, onto Social.

I installed the Development version of the plugin as instructed by
JanRain support and enabled it. Unfortunately, it didn't work. After
some investigation, I found that the 'Antispam Bee' plugin was the
issue, as it renames the 'comment' textarea with an md5 hash to
prevent spam-bots (Fantastic plugin, if you've never used it). In the
PHP, it moves the $_POST['comment-xxxx'] to $_POST['comment'], so that
further plugins works, however the RPX plugin checks $_REQUEST, not
$_POST. Modifying the rpx.php code (around line 133) to use $_POST
instead, and changing the action priority (line 128) to 11 instead of
1 (to ensure that it ran after the Antispam plugin) fixed it..

The next problem I found was that as an admin, everything worked just
great. However, as an actual user it didn't. This wound up being
related to the 'W3 Total Cache' plugin (I think). FireBug showed that
the code wasn't executing due to a syntax error. The comments in the
JavaScript footer added by RPX.PHP (around like 363 I think) were
being mangled by W3's insertion of CDATA tags (to increase standards
compliance). Simply removing the JS comments (nothing more than a
begin/end pair anyway), fixed it. (It worked as Admin because I have
it configured not to do that as Admin, to aid in debugging).

All that said, it's all apparently working great. Feel free to stop by
www.VizWorld.com and check it out, and I'll answer whatever questions
I can about it.

Reply all
Reply to author
Forward
0 new messages