Facebook has a silly bug which messes up Phorum URLs. In a nutshell, Facebook has to encode URLs submitted to their Graph, but when it comes time to decode that URL back into its working form, they forget to decode commas, leaving %2C in places that Phorum expects to see commas. Here is some chatter about this: [www.phorum.org] Probably Facebook will fix their bug. In the meantime, why wait? Here is a simple module that works around it, based on Maurice's idea in the above thread, and the very fortunate foresight of the Phorum team to place a parse_request hook just before query strings are parsed. Enjoy, -phil. Change log: August 3, 2011 - skip decoding when Phorum's redirect.php is the executing script https://www.phorum.org/support/read.php?62,146932,146932#msg-146932 Tue, 13 Oct 2026 04:32:48 -0500 Phorum 6.0.4 https://www.phorum.org/support/read.php?62,146932,151125#msg-151125 https://www.phorum.org/support/read.php?62,146932,151125#msg-151125 Should just use the case insensitive versions like so:

[code="php"]

if(strtolower($self[count($self)-1]) !== 'redirect.php' && stripos($_SERVER['QUERY_STRING'], '%2C') !== false) {
// Override the query string.
global $PHORUM_CUSTOM_QUERY_STRING;
$PHORUM_CUSTOM_QUERY_STRING = str_ireplace('%2C',',',$_SERVER['QUERY_STRING']); # Facebook cap, Hotmail lower
$PHORUM_CUSTOM_QUERY_STRING = str_ireplace('%3D','=',$PHORUM_CUSTOM_QUERY_STRING);
}
[/code]]]> Skye N. v5/v6 Modules/Add-Ons Sat, 31 Mar 2012 14:40:31 -0500 https://www.phorum.org/support/read.php?62,146932,150934#msg-150934 https://www.phorum.org/support/read.php?62,146932,150934#msg-150934 Anyway, easy to patch your code to handle that too, just add a replacement and chage strpos to stripos

[code="php"]
if(strtolower($self[count($self)-1]) !== 'redirect.php' && stripos($_SERVER['QUERY_STRING'], '%2C') !== false) {
// Override the query string.
global $PHORUM_CUSTOM_QUERY_STRING;
$PHORUM_CUSTOM_QUERY_STRING = str_replace('%2C',',',$_SERVER['QUERY_STRING']); # Facebook
$PHORUM_CUSTOM_QUERY_STRING = str_replace('%2c',',',$_SERVER['QUERY_STRING']); # Hotmail
$PHORUM_CUSTOM_QUERY_STRING = str_replace('%3D','=',$PHORUM_CUSTOM_QUERY_STRING);
}
[/code]]]> Skye N. v5/v6 Modules/Add-Ons Wed, 08 Feb 2012 18:52:38 -0600 https://www.phorum.org/support/read.php?62,146932,150703#msg-150703 https://www.phorum.org/support/read.php?62,146932,150703#msg-150703
[bugs.developers.facebook.net]]]> Skye N. v5/v6 Modules/Add-Ons Thu, 22 Dec 2011 14:52:19 -0600 https://www.phorum.org/support/read.php?62,146932,149331#msg-149331 https://www.phorum.org/support/read.php?62,146932,149331#msg-149331 Phil Connolly v5/v6 Modules/Add-Ons Wed, 03 Aug 2011 13:24:16 -0500 https://www.phorum.org/support/read.php?62,146932,149325#msg-149325 https://www.phorum.org/support/read.php?62,146932,149325#msg-149325
When redirect_after_post = 'read', I can see Phorum is trying to do what you want, jump to the last message of the thread, and its full URL contains an anchor (#). Phorum has some twiddling it does in the case it must redirect to an anchor from a POSTed page (such as replying to a post), mainly to overcome an Internet Explorer bug which strips the anchor, and in this case Phorum wraps the redirect in a special case script (no surprise, it is named redirect.php) which sends the browser to the correct URL, including the anchor. The destination URL is first encoded by Phorum and then decoded by redirect.php, but my little module didn't know all that so goes ahead and decodes the URL itself, thereby messing up redirect.php, and leaving Phorum with a bogus URL which it defaults to the forum list page.

I wrote that summary not expecting you would care one way or the other of the technical issue, may be you do, but mainly so any Phorum experts can provide a tip to workaround this. My initial thought is to just test if redirect.php is the page being accessed and if so skip the facebook-fixing decoding. That would be easy, but maybe there are other cases similar to this I should be aware of?

I'll make a change based on what I know tomorrow.

-phil.]]> Phil Connolly v5/v6 Modules/Add-Ons Wed, 03 Aug 2011 00:26:23 -0500 https://www.phorum.org/support/read.php?62,146932,149324#msg-149324 https://www.phorum.org/support/read.php?62,146932,149324#msg-149324
In our General Forum Settings, we can specify whether after submitting a post, the user is redirected to the list page or the newly posted message itself on the read page. I personally have selected the latter, so users see their post after submitting it.

When this module is activated, new topic will redirect to the message as it should, but all replies to topics get redirected to the list page. In other words, the setting to redirect to the read page instead of the list page seems to be ignore when replying to posts and having this module activated.]]> Robert Angle v5/v6 Modules/Add-Ons Tue, 02 Aug 2011 22:10:50 -0500 https://www.phorum.org/support/read.php?62,146932,146932#msg-146932 https://www.phorum.org/support/read.php?62,146932,146932#msg-146932 www.phorum.org]

Probably Facebook will fix their bug. In the meantime, why wait? Here is a simple module that works around it, based on Maurice's idea in the above thread, and the very fortunate foresight of the Phorum team to place a parse_request hook just before query strings are parsed.

Enjoy,

-phil.

Change log:
August 3, 2011 - skip decoding when Phorum's redirect.php is the executing script]]> Phil Connolly v5/v6 Modules/Add-Ons Mon, 22 Nov 2010 11:10:55 -0600