Reedyseth
commented
8 years ago I'm uncertain whether the magical 99999999 page id is a reliable way to detect whether a page is being generated by StCR. It seems very hacky.
Actually you shouldn't use that, because you will limit your permalink structure to id.
Perhaps there is a reliable global flag or instance variable I can check if StCR is actively generating a virtual page?
There is an option that store the Virtual Management Page status, so you might add this to your code:
function mdwp_MarkdownPost($text) {
/* DSHACK */
global $post, $wp_subscribe_reloaded;
$virtual_page_flag = isset( $wp_subscribe_reloaded ) ? get_option( 'subscribe_reloaded_manager_page_enabled' ) : false;
// Do what you need with the $virtual_page_flag
$slug = get_post( $post )->post_name;
if ($slug=='http://davidseah.com/?page_id=9999999') return $text;
/* END DSHACK */
// ... rest of function continues...Regards.!!
daveseah
This is specific to my website's use of the "classic" Wordpress plugin PHP Markdown Extra and its interaction with StCR's management page generation. I have worked around the problem on my blog but am reporting it here in case other people have similar problems, or if there is a better workaround available.
THE ISSUE
Users who tried to engage the subscription management page were presented with a code listing containing the form markup instead of it being rendered as a form. This prevented them from unsubscribing to comments.
I tracked the issue down to the way that StCR injects its form html and how Markdown interprets it. In Markdown, text that is indented by a 4 space or a tab is interpreted as a preformated code block. Line 52 of
templates/user.phpin commit 08d56de uses such an indent, and therefore gets rendered wrapped with<pre><code>blocks. Markdown allows for inline HTML with the caveat that it is wrapped by non-indented tags, and this is the case in most (but not all) of the HTML snippets that StCR emits.MY WORKAROUND
I originally added some wrapper
<div>to theuser.phpto see if this was the case, but updating the files of a well-maintained plugin meant I'd have to do it every single time I updated. I don't think StCR is doing anything wrong either in this case; it's my use of using a PROCESS EVERYTHING Markdown plugin (it is necessary in my case) that is the culprit.Since PHP Markdown Extra is no longer maintained anyway, I modified my own copy's
mdwp_MarkdownPost()function, which is called to filter content text, to check whether the current page seemed to be generated by StCR and return unprocessed text:I'm uncertain whether the magical 99999999 page id is a reliable way to detect whether a page is being generated by StCR. It seems very hacky. Perhaps there is a reliable global flag or instance variable I can check if StCR is actively generating a virtual page?