Installing a new 6.14 Drupal and editing the content type Story and changing nothing but saving anyways, provides the following text:
A story, similar in form to a page, is ideal for creating and displaying content that informs or engages website visitors. Press releases, site announcements, and informal blog-like entries may all be created with a story entry. By default, a story entry is automatically featured on the site\'s initial home page, and provides the ability to post comments.
Doing this another time:
A story, similar in form to a page, is ideal for creating and displaying content that informs or engages website visitors. Press releases, site announcements, and informal blog-like entries may all be created with a story entry. By default, a story entry is automatically featured on the site\\\'s initial home page, and provides the ability to post comments.
Each time I get more "\" escape characters.
Why is that?
kind regards, martin
Comments
Comment #1
fourstone commentedSystem Information:
Drupal 6.14
Access to update.php Protected
Configuration file Protected
Cron maintenance tasks Last run 1 sec ago
You can run cron manually.
Database updates Up to date
Drupal core update status Up to date
File system Writable (public download method)
GD library bundled (2.0.34 compatible)
MySQL database 5.0.51a
PHP 5.2.9-1nmm1
PHP memory limit 64M
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Update notifications Enabled
Web server Apache
Comment #2
fourstone commentedError has impact on all URLs, smileys etc which are entered in any text field in Drupal, therefore raising priority.
Comment #3
fourstone commentedComment #4
fourstone commentedAfter commenting out the following line (3times, once for each php/apache combination) from the default .htaccess file the effect vanished:
php_value magic_quotes_gpc 0
-->
# php_value magic_quotes_gpc 0
Why is it this entry is there and sometimes it leads to this issue? It appears to have something to do with the provider setup?
any insights would be great!
Comment #5
dpearcefl commentedIs this issue still occurring in the current version of Drupal v6?
Comment #6
dpearcefl commentedComment #7
damien tournoud commentedThis is a classic bug in some environments that uses the htscanner PECL module. If you bump into that type of issue, just change host.