othermichael

How sad that Blogger actually allows you publish non-screwed HTML, but WordPress makes you install a plugin to stop it from screwing it up.

Please note that “hotlinking” is usually frowned upon–every time your page with that image loads, you are loading the image from their server & using that site’s bandwidth.
You should probably save a copy locally, then use the “upload” feature. That should automatically generate the code that you need to include in the post.

It sounds like Poons wants to test a template, not just CSS.
I’d reccommend making a backup of the template. If you’re working directly in the WP-admin environment, copy & paste into a text editor, & save locally.
Fiddle with your new template for a while. If it’s a hopeless mess (oh, how familiar that is!), copy & paste your local copy back into the template screen.
Backups are nice to have around, no matter what….
—-
But that doesn’t solve the “without having to take down my current blog” condition, does it?
In which case, I’d go with Sushubh’s suggestion of uploading it as an alternate name & only being able to look at main page.

There are so many different kinds of support, that the support pge should be directing towards all of them, first.
Wiki, FAQ, Forums, etc. are all subsets of Support.

Okay; got it. It seems Dreamweaver was massively rewriting some items in a bizarre fashion. I had to edit the file in notepad to get it right.
Hrm. It shouldn’t have been rewriting _anything_.
Ah, well. Thank you. It works most excellently!

Oh, great. Now that I’ve reverted to the original code, I get that error no matter what. I’ve even uploaded a completely unmodified-ever copy from a separate installation.
The same error every time?!???
I’m going back to teletypes, I swear….

It’s been a while since this was proffered, but I finally tried it out.
Sadly, I get this result:
Parse error: parse error, unexpected T_ELSE in /[...]/htdocs/scp/wp-login.php on line 303
I’ve tried replace the first, the second, and both instances of “wp-admin/” wiht wp-admin/edit.php and the result in the above error in all three instances.
One note: I have the replacements appearing on lines 261 and 304

I get bizarre time-outs when I (often, but not always) move a post from “draft” to “publish” and publish it… the whole system will “lock up” for long periods of time…
https://www.xradiograph.com/scp/
odd thing is, I can access the blog’s front page through a redirected subdomain: https://scp.xradiograph.com

Maybe this thread is germane?

Hrm. Why does WordPress add stuff to our posts? There has got to be a way to shut this off. And I’m not talking plug-ins.
Even Blogger allows you to do this.
Software that auto-munges my code is bad software….

Gosh, I’m a whiner! Sorry.

Whoah. Why should I have to add something to WordPress to make it stop adding things nobody asked for?
I mean, why would those break-tags be there, anyway? I’m formatting my posts correctly, everything is happy…I have extra spaces in them so I can read and parse it visually (becuase I ma not a browser). Almost every browser in the world ignores spaces and line breaks. So why does WP add them in? This is not a feature–it is an extremely annoying bug.
Is there any more documentation on that plug-in? His one-sentence description doesn’t exactly do it for me.

I have no answer to the added break tags, either. I could have sworn I saw one once, though. :::sigh::: Why the heck would it add the stupid things, anyway? If I wanted WYSIWYG I ask for WYSIWYG….

Stupid program keeps adding in
tags when there is a carriage return in the text. Where is the switch to turn this abominable behavior off? If I didn’t put it into my post, don’t *!@&#!@ add it for me!
ahem.

Lookin’ good. Coherent design, coherent use. At times I think the color-scheme is darker than I’d like, but everything stays readable.