#1194 closed defect (fixed)
Extra slashes when deep integrating with WordPress
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 1.0.3 | Priority: | normal |
Severity: | normal | Version: | 1.1-alpha |
Component: | General - Integration | Keywords: | has-patch |
Cc: | mark@… |
Description
The reason is that bb-settings calls bb_global_sanitize regardless of the fact that the input was already sanitized by wordpress.
Suggested solution: put a "if ( !defined( 'ABSPATH' ) )" before the sanitizing calls.
Attachments (1)
Change History (11)
#3
@
11 years ago
- Keywords reporter-feedback added; needs-patch removed
- Resolution set to worksforme
- Status changed from new to closed
#4
@
11 years ago
Me bad, didn't gave enough details.
I was trying to write a bbpress as WP plugin. part of it was loading (as part of WP init) bb-settings which sanitize the input (this is from memory), but the input was already sanitized by WP..... This leads to double slashes.
As far as this report is concerned - I think that it is valid but since it seems to me right now that it is easier to use the new post_type types feature of WP 3.0 to make a simple forum for WP instead of deep integration, I'm no longer really interested in it.
#5
@
11 years ago
- Keywords reporter-feedback removed
- Resolution worksforme deleted
- Status changed from closed to reopened
Reopened as more people are having the same issue - http://bbpress.org/forums/topic/when-i-use-apostrophe
#7
@
11 years ago
- Keywords has-patch needs-testing added
- Summary changed from Extra slashes when deep integrating with wordpress to Extra slashes when deep integrating with WordPress
#9
@
11 years ago
- Version changed from 1.0.2 to 1.1-alpha
Still happens to me on bbPress 1.1-alpha-rev2461 + WP 2.9.2 (I just integrated header and footer adding require wp-load.php
to bb-config.php
), though it doesn't on bbPress 1.0.2 + WP 3.0, neither on bbPress 1.1-alpha-rev2461 + WP 3.0 (in this last case [2448] works perfectly).
Should I just upgrade to WP 3.0?
Tried this on my install, there were no extra slashes. Does this still happen with the latest WordPress version too?