dwest
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Run existing html site while testing WP in root??I understand. I’ll simply rebuild the site in WP in a subdirectory then move it when done.
Thanks!
Forum: Fixing WordPress
In reply to: Run existing html site while testing WP in root??OK. Thanks! I’ll do that. I’ve done it that way before but I thought I’d give it a shot this way since the original site is straight HTML.
Why does WP not just ignore the old site? Just curious.
Forum: Fixing WordPress
In reply to: Blog Screwed up in FirefoxThis is no doubt a CSS interpretation problem between IE and Firefox. Buy a good book on CSS. Then the “shit” will disappear.
Forum: Fixing WordPress
In reply to: WYSIWYG editor messing up div tags in 2.1Otto42,
And disagree I will.What sort of “crisis” is created if one does not adhere 100% to XHTML/CSS?
When a standard gets in the way of common sense, the standard is no longer a standardization tool but rather a usage control.
When a tool forces a user to comply to standards that a user should be free to adjust at will, then the tool becomes a usage control rather than a tool.
If one has to go through an HTML and CSS exercise to simply insert an extra line…well friend, that is ludicrous and precisely why I have little respect for standards.
Tell a client who is editing their own content–a client who does not know what CSS is or will EVER care–that they can’t insert a blank line. Ask them if they think that is intelligent design. They won’t. And they would be correct in their thinking. Non-programmers are keenly intelligent. They live and think in the real world.
BTW, even with my lack of respect for standards, I STILL have hundreds of happy clients with websites that bring them business. So please don’t feed me the “importance” of strict adherence to standards. Standards have their place but there is no place for tools that force strict adherence at the expense of usability.
The above is a wordy way of saying “drop the XHTML/CSS puritanism and give us a 100% flexible tool so we and our clients can make our own decisions about using it as we see fit.”
Forum: Fixing WordPress
In reply to: WYSIWYG editor messing up div tags in 2.1WordPress Team? Can we get this incessant visual Rich Text Editor problem working properly???
-Deleted div tags whenever they are inserted
-Can’t enter repeated blank lines. Going to code view and back to RTE deletes them.I have clients beating me up over this as do many other developers who advocate WordPress to their clients.
If RTE can’t be fixed then get rid of it completely.
Right now is sucks.
Forum: Fixing WordPress
In reply to: Editor removes tags! Is this a bug?bump.
Any experiences with this?Forum: Fixing WordPress
In reply to: line breaksmattymo
How?Forum: Fixing WordPress
In reply to: line breaksSame problem here! Obviously a bug. This is a big problem.
WordPress support please chip in on a fix ASAP.
Forum: Fixing WordPress
In reply to: SEO and wordpress … in regard of the H1-H6 tags ..So create a div with a class that styles the h1 the way you want and always put your SEO poop inside that div. Then any H1 inside that div will look as you wish.
Forum: Fixing WordPress
In reply to: server overloading with 2.1Tell your dedicated server admin that he is simply going to have to provide you with more details. How does he know the blog is the problem? What do the server logs say etc. You’re paying for them to support you, not play dumb ?? They need to help you troubleshoot the problem.
Forum: Fixing WordPress
In reply to: SEO and wordpress … in regard of the H1-H6 tags ..Why not?
Forum: Fixing WordPress
In reply to: Saving a new post makes wordpress stop dead in its tracks…What version are you using?
Forum: Fixing WordPress
In reply to: WordPress 2.1, How do I get multiple spaces in the editor?Sorry to bump but surely someone else is having this problem?
Forum: Fixing WordPress
In reply to: Custom Contact FormYou can’t put php code directly in the page in WP.
Install PHPexec plugin. That should remedy your problem.Forum: Fixing WordPress
In reply to: Changing default font tags in visual rich editorTiny MCE as configured in WordPress 2.1 wipes away divs and replaces them with p tags.
This can be fixed by doing the following:
1-Open your TinyMCE config file in an editor. The file is located at:
wp-includes/js/tinymce/plugins/tiny_mce_config.php2-Replace Line 25 with the following but on a single line:
$valid_elements = ‘#p[*],-div[*],-strong/-b[*],-em/-i[*],-font[*],-ul[*],-ol[*],-li[*],*[*]’;
3-Save the file back to your active WordPress installation, overwriting the existing tiny_mce_config.php file.
4-In WordPress admin, the editor will now allow divs.
You may have to refresh your editor page.
As always, copy your original tiny_mce_config.php file to a safe place for backup before editing the original.