kay9

OK, I just tried making a new htaccess with the code from the sticky as the ONLY thing in it and placing it in my admin directory just like the sticky instructions say to. (I did not need to touch my existing htaccess, which is in another directory.)

It worked: I can now upload images; no more error message. Yay.

I’d tried a few of the other suggestions in the sticky, as I said above; apparently I just stopped too soon, proving yet again that it pays to be persistent and follow directions exactly. ??

amom,

It’s not that I don’t like BB, I just don’t have much experience with it. The one time I did have it installed and activated it did something weird/bad, but honestly, I forget what now. I wasn’t traumatized or anything. Heh. It was a long time ago. I have no idea how SK works; the main reason I’m using it because “it was there.” ?? It seems to work for me, although between my htaccess and settings I’ve chosen up at my hosting server, and of course the privacy settings on WP itself (re: comments, registration, etc.), I don’t even GET spam, so it’s hard to know which of the spam preventatives/killers is actually doing the heavy lifting.

I’ll go ahead and try adding the code to the END of my htaccess. I have anti-hotlinking code there, if memory serves. The worst that can happen is it won’t work and I’ll get a message, in which case I’ll delete it. Worth a try!

Hi amom,

Nope, not using Bad Behavior (and never have). Spam Karma, yes. Maybe I’ll try deactivating it and see if the images will upload without that error message, just for the heck of it.

I haven’t tried the htaccess hack yet, but I do have an extensive custom htaccess file so I was REALLY hoping I wouldn’t have to mess with any of that.

Thanks for your response!

TANKER:

This is exactly the error that I am getting. I use the latest version of FireFox.

So far I’ve tried the Flash Player upgrade (recommended in the sticky), and the clearing cache procedure (also recommended in the sticky). I’ve replaced my includes/link-template.php file too (per the sticky).

Nothing works for me so far; still getting that crunching message followed by “http error, try again later.”

I’ll be very interested to hear a solution for this error message.

Thanks guys.

SOLVED:

IF you are using WP 2.2.3 (sorry, not sure about other versions), this worked for me:

— When installing, put the image-headlines.php file in the wp-content/plugins directory.
— The .ttf file needs to go in the wp-content/image-headlines directory (which you have to manually create).

Be sure to put

the title(’-image-’);

(the function call) in your home.php file AS WELL AS in your index.php and page.php files. Not having it in my home.php file was what was causing the non-rendering for me. I think you can put it into your search.php too, if you need/want image headlines for that part of your site.

While I’m on a roll:

How To Solve the “border around the headline” issue:

Put

h1 a img {
border: none;
}

into your CSS file for the theme you are using.

Worked for me, anyway. Good luck. It’s a great plugin.

I, too, am having trouble getting the Image Headlines plugin to work. Using the latest WP version. Everything else is fine; AND I have used the Image Headlines plugin before (back quite a while ago, with the 1.5 version of WP) and it worked fine.

So I’m at a loss here. I finally got rid of the cache directory error message, and I have put the calls into my templates . . .

But it is still not DISPLAYING the fonts I uploaded for my headlines; i.e., it’s still displaying the regular ole font from my stylesheet displayed on my site. And yet, the new fonts I want to use ARE showing up in the Headlines admin area of my site.

Anyone still reading this thread willing to help? ??

I’d like to see an answer to this one too. Anyone?

Used ‘unofficial’ (1.5.1.3 – 1.5.2). Didn’t disable plugins. No probs during/after. Unofficial, you made sense to me.

Heh. Now I can make my long range plans.

OK, I know, there is NO official release date for WP 1.6. But are there any HINTS?

Like “Yes, in 2005”?

Or “No, NOT in 2005”?

Please, just a hint, if someone in the loop really has a clue. Come on. You know you want to tell us.

Thanks again, both. That is very helpful to know!

Thanks.

What I meant is when I am “asked” about overwriting, would it be by my FTP program or in the running of the upgrade URL given to me by WP.

Is there any way to just skip the upload of the new CONTENT folder and all files within it? If the upgraded bits aren’t in there anywhere, I mean? Why bother uploading that at all, why include it in the upgrade package (if people are upgrading, they may be presumed to already HAVE the CONTENT folder, right?). Yes, I am full of delightful questions, aren’t I?

Thanks very much to both. I will try. I wish there was a way to do this upgrade without showing any visible disruption at all on the site, even for a few minutes. Because if I’m understanding, it sounds like ALL upgrades require at least some amount of time during which the live site is fully “deleted” while all the new files are uploaded to replace them, etc. So visitors coming during this time, or already logged in at this time, see . . . what? Just wondering.

Also, when you say “don’t overwrite the files and directory [content] listed above,” I assume you mean that something, at some point, is going to ask me about overwriting? Would that be a WP-upgrade-(“run”) embedded screen, or is it entirely via my FTP program of choice and thus up to me to watch out not to overwrite? I want to be sure not to miss that part, because my default template is quite customized.

Thanks again.

Apparently you can’t turn off certain plugins (not mentioning the names because I love the plugins!) without making your site show ugly errors even before you try to do the upgrade. I guess it’s the dynamic nature of the plugins . . .

Good news: I’ve backed everything up several times and several ways, in preparation to upgrade straight from 1.5 to 1.5.1.3.

Bad news: I have made changes to wp-admin and wp-includes and a couple of root files. Yes, I know WP gives dire warnings about doing that. Unfortunately, I did not read or know about those warnings in time. My bad. Water under the bridge now, I guess. Hope newcomers may learn from my experience.

So, onward. Does anyone much more experienced that I have any helpful information on “how to pick through the files and delete and replace specific files one by one instead of doing the 1.5 – 1.5.1.3 upgrade like the general instructions say you should, when you’ve made changes to a handful of the core files?”

I’m sure such an ‘upgrade’ method is just terrible form and all, not to mention how it will scramble the heck out of the live site, right? Which is what really worries me.

Or is there a better way? I’m all ears.

I really don’t think my changes are all that severe (in fact, I think a couple of them are worth being permanent changes to WP, and maybe they already are!), it’s just that the upgrade instructions don’t seem to apply precisely to my situation because I’ve made those changes I shouldn’t have made and ruined the simplicity of things.

I’ve made fairly minor changes in one file at ROOT level (wp-login), to 2 WP-ADMIN files (menu.php, quicktags.js), and to 2 WP-INCLUDES files (functions.php, vars.php). I have the original 1.5 files and copies of my current working customized versions.

Also replaced the entire wp-admin templates-function-category.php file per WP’s own security alert, a while back.

At ROOT level, I have (and believe I should not delete in any upgrade process):
My htaccess file (not WP’s, which I guess gets upgraded)
Fantastico files (WP 1.5 was installed via Fantastico)
4 cust error pages
robots.txt file
.ico files
cgi-bin folder

~TIA ~