WordPress.org

Make WordPress Core

#48917 closed defect (bug) (invalid)

Backslash issue

Reported by: rex.rony Owned by:
Milestone: Priority: normal
Severity: critical Version: 5.3
Component: General Keywords: has-screenshots
Focuses: administration, multisite Cc:

Description

Hello,
By profession, I am a web developer,
I am facing an issue with new WORDPRESS Update, This Issue I am facing not on single site
but two of the site Which I am working on them, every time I update post or edit PHP file from file editor, it add Backslash (\) before quote (").
First I thought maybe it is plugin issue with first site, but recently I updated my second website and trying to make changes in PHP file, and I face same issue you can check 2nd snapshot
below are snapshot
1) https://paste.pics/434165297f6a1d456b3cbd67e73ca545 (backslashes are adding up, on post update, it is breaking WPbakery Shortcode)
2) https://paste.pics/7GKC4

Attachments (2)

double quotes.png (47.4 KB) - added by rex.rony 20 months ago.
snap2.png (68.6 KB) - added by rex.rony 20 months ago.

Download all attachments as: .zip

Change History (4)

@rex.rony
20 months ago

#1 @dkarfa
20 months ago

Hi @rexrony ,
Welcome to WordPress Trac! Thanks for the ticket. I'm sorry to hear you are having issues with WordPress.

Please note that this Trac is used for enhancements and bug reporting for the WordPress core software, not for general support or plugin issue.

As noted above, please try the support forums to get help with your site: https://wordpress.org/support/forums/

Thank you,

#2 @garrett-eclipse
20 months ago

  • Keywords dev-feedback post-update-issue removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

As @dkarfa mentioned the support forums are your best avenue for this. That being said just wanted to point out you don't need to escape the single quotes inside PHP calls as they get rendered before your HTML so hopefully the following illustrates that;
<meta charset="<?php bloginfo( 'charset' ); ?>">
*This should avoid your error, and you can just update the rest of your PHP calls as they won't need to have their single quotes escaped.

Note: See TracTickets for help on using tickets.