Double-escaping quotes: problem not solved?
-
I recently deployed a site that made use of UAM for user access management. When configuring the plugin, I was surprised to find that the settings page appears to double-escape quotation marks, rendering it impossible to use HTML in the “Post content” and “Page content” fields.
In researching the issue, I found this page, which lists four locations in the source code that needed to be patched to use stripslashes() in order to prevent this. I modified the four lines and now the plugin seems to work correctly.
However, I’m concerned that the next time an update to UAM comes out, my patched files will be overwritten by new, “clean” versions of the files downloaded straight from the Plugin Repository, which will bring the problem right back again.
Since the page I listed above indicates that this has been a known issue since at least UAM version 1.2.4.3, it seems like by now the patch should have made its way into the distributed version of the plugin. But I was using the latest version, 1.2.6.0, and it wasn’t in there.
Is there an ETA on when we can expect UAM to handle these input fields correctly without manual patching? As it stands I have to tell my client to not update UAM at all, which I’m uncomfortable with as it can lead to security problems down the road. But if an update is going to re-introduce a bug that I patched out, that’s no good either.
- The topic ‘Double-escaping quotes: problem not solved?’ is closed to new replies.
