Not signed in (Sign In)

SkillShare - A place to discuss Web Standards and Web Design topics

Categories

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

Content Management Systems: Wordpress WYSIWYG rewriting / reinterpreting HTML

Bottom of Page

1 to 9 of 9

  1.  
  1.  permalink
    I'm in the process of migrating some content from a flat site into a site powered by Wordpress 2.1. I'm essentially pasting markup from Dreamweaver into the WYSIWYG editor. I've noticed if WP doesn't understand the context of the original HTML, it will rewrite it. The code I'm entering looks like this


    Content goes here.
    </div>
    <div id="pagepic" class="right"><img src="/images/wrapper_work.jpg" /></div>


    But WP rewrites it like this:

    Content goes here.
    <p id="pagepic" class="right"><img src="/images/wrapper_work.jpg" alt="work" /></p>


    Is there a way to force the WYSIWYG editor to interpret my HTML more literally?
  2.  permalink
    I've also noticed that even if you have the 'Code' tab open and paste in raw HTML, the WYSIWYG editor will put in <p> tags wherever it deems necessary, according to its interpretation of whitespace. Anyone found a way around this? The WP forum was of no help.
    • CommentAuthormista3
    • CommentTimeMar 8th 2007
     permalink
    Stupid question, but why do you need to post raw markup into the editor? I don't think there's a way round this without switching off the WYSIWYG editor alltogether.
  4.  permalink
    Stupid question, but why do you need to post raw markup into the editor?

    A million reasons. Plenty of elements need to be wrapped with specific tags and classes that WYSIWYGs don't offer. Not to mention, anyone who is meticulous about their code is going to want to check the markup while designing content and layout, especially if the content isn't rendering correctly in a browser.

    In this particular case, I am migrating content from a flat site to a WP-driven site, and all that content is already marked up. Trouble is, the WYSIWYG keeps rewriting it.

    Sounds like others are having some of the same problems:
    http://blog.taragana.com/index.php/archive/wordpress-wysiwyg-editor-is-a-disaster/
    • CommentAuthormista3
    • CommentTimeMar 8th 2007
     permalink
    That's a tricky one!

    I'm used to only putting <p>'s <h1>'s etc directly into a Wordpress post, the way I see it that's all the markup this part of your template should be handling.

    The only thing I can think is to use an older version of WP until they get the latest release sorted, as the new wysiwyg/code tabs seemed to have caused a lot of problems.

    Maybe they'll patch things up in the next release, or someone will release a plugin to sort it out. Hmm.
  6.  permalink
    As a matter of interest why are you converting the whole site to Wordpress if you want to retain that level of control over the content HTML?

    I ask the question because IMO when you convert a flat site, not written with CMS in mind, to any CMS powered site you have to be prepared to modify the CSS to take into account the of the way in which the content code is generated. Essentially you have to weigh up the cost of the modifications against the need for the conversion.
  7.  permalink
    As a matter of interest why are you converting the whole site to Wordpress if you want to retain that level of control over the content HTML?

    So the client can edit the static pages himself without having to use FTP, know HTML/CSS, and so forth. Also he wants a 'news' section, which is easy to accomplish from Wordpress's inherent blog functionalities. All in all, WP seems like a great solution, I just had not wrangled with the many WYSIWYG issues til now.
    • CommentAuthoraxe_sosharp
    • CommentTimeMar 9th 2007 edited
     permalink
    Unless the client is planning to update the static pages on a regular/daily basis why not just give them a WP News page and persuade them that in the long run it would be more cost effective to pay you a small set monthly fee to cover minor updates on the static pages. Otherwise you will have to rewrite the HTML/CSS to accommodate the Wordpress output.

    If all else fails, if you have PHPadmin installed on your server you can bypass the text editor and change the Wordpress database directly.
  9.  permalink
    For anyone having similar problems, I've found a few more pieces of related feedback on the WP forums:

    http://wordpress.org/support/topic/107916?replies=2
    http://wordpress.org/support/topic/101906?replies=52

1 to 9 of 9

  1.  
Add your comments
    Username Password
  • Format comments as (Help)
 
Back to Discussions Top of Page