Using '&#160' not rendering in WP 4.0

  • I’ve upgraded to 4.0 on my local desktop used for testing and am finding that my use of the html characters for creating additional spaces between words or other, &#160, is not rendering now. I’m confused why upgrading to 4.0 would affect this, but have disabled all plugins and get the same result.

Viewing 8 replies - 1 through 8 (of 8 total)

  • Do you mean to write:

    (LOL the strip out & # 1 6 0 ; here!)

    With the semi-colon at the end?

    Also see about using $nbsp; for a non-breaking space.

    https://www.w3schools.com/html/html_entities.asp

    Thread Starter ShallowVee

    (@shallowvee)

    Thanks Pioneer. Apparently I’ve always done it wrong and omitted the semicolon at the end, and since WordPress still created a space, I continued to use it. However WordPress 4.0 doesn’t accept it without the semi-colon. I’ll have to go through my pages and find these errors before updating to 4.0. Thanks again.

    The check for invalid XHTML is still on? Try toggling it? Just a thought…

    Admin Dashboard>Settings>Formatting>WordPress should correct invalidly nested XHTML automatically

    ??

    https://codex.www.ads-software.com/Settings_Writing_Screen#Writing_Settings

    Thread Starter ShallowVee

    (@shallowvee)

    This “WordPress should correct invalidly nested XHTML automatically” preference is unchecked in both 3.91, where it accepts it without the ending semicolon, and 4.0, where it doesn’t accept it without the semicolon. Toggling it doesn’t seem to affect the results of this issue in either version. Aside from wordpress versions, all else is the same as well, as the desktop local server is a direct copy of the live site, updated as recently as this afternoon.

    Thread Starter ShallowVee

    (@shallowvee)

    I think all else is the same, however it may not be, if installing 4.0 overwrote the or updated default settings for 3.91 when updating.

    Next thought: Does ‘whatever’ runs the XHTML check run server-side only and require same ‘module’ etc on local?

    I assume you are noting now that 3.9.1 is on local machine setup and 4.0 on remote server? Are all other configs the same? PHP Version, etc..,etc…and then may strip certain content also???

    Aside from wordpress versions, all else is the same as well, as the desktop local server is a direct copy of the live site

    There are often valid reasons why ‘something’ works locally and not remotely…might want to pursue that.

    Can you share the source code above <head> from each install (if not exactly the same)?

    If you run a phpinfo.php file on each do they match?

    What about php.ini files and any host constraints for such?

    Thread Starter ShallowVee

    (@shallowvee)

    Thanks, Pioneer, that’s very insightful (and reasonable, as most likely there are difference in php versions and or other configs.) But investigating these potential differences involves a more intense effort than I’m interested in putting into it to understand the cause of these differences. I’ll cover my tracks and correct the html where I’ve incorrectly used this syntax (which probably should be done regardless), and then update the remote server to WP 4.0 and move on for now.

    That is a good game plan! Often I find just getting to work and ‘fixing’ it is better than spending time researching!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Using '&#160' not rendering in WP 4.0’ is closed to new replies.