kay9

Thanks macmanx! I was thinking I remembered reading something a loooong time ago about deleting config-sample.php after installation being very important, so I thought, hmm, put it back just for an upgrade, really? Also nice to know what it is for (template for wp-config, aha). Was also a bit confused about “the two htaccess” files (one is mine, one is WP’s).

I have my own htaccess file in the root, and also 2 Fantastico files (host said don’t delete; used during cpanel installation of 1.5 a while back), and want to try to do the upgrade from 1.5 to 1.5.1.3 myself because of customizations I’ve made. I.e., can’t do upgrade via Fantastico because of customizations I’ve made.

(I have a list of a few changes I made to things in wp-admin and wp-includes that I will put back after I upgrade. Hopefully.)

Question: can I leave MY htaccess file and the Fantastico stuff there during upgrade?

Also, noticed that the 1.5.1.3 folder has a file called config-sample.php. The site’s file is called wp-config.php, though. Just curious: what relation, what changes, between these two files in upgrade? Or is my installation already messed up because these two files don’t match?

TIA.

Any way to erase this? I really shouldn’t have started this thread. Coupla people are missing my point. Feedback. Just feedback. Turns out it is quite useless. Hence my request for deletion. Feedback only. Not a request for more Codex links. Thanks anyway. See my very first thread-starting post (above).

Wow, feedback on my feedback. ??

Like I said, my problem (not criticism, not anything but a little weird feedback) is that I don’t understand what some of the stuff means, exactly. And, call me overly cautious, but I’d prefer to be sure I know what each step means, exactly, BEFORE I begin trying to do the steps (upgrade steps).

I really like WP. As far as the idea of my editing the Codex upgrade instructions, that kinda made me chuckle. I *am* the blind, so I don’t think I can *lead* the blind. Scary thought, eh?

Um, a sidenote. Just because I “know” enough to point out what parts of the instructions I don’t understand does NOT mean I ‘understand’ enough to upgrade. A monkey can point to fire and “understand” it’s hot and even go ahead and stick his hand in it (start the upgrade) without understanding anything about what he will suffer and how to fix the third degree burns after he gets burned because he went ahead without understanding that indeed, fire turned out to be not only hot, but capable of inflicting burn wounds. (To torture an analogy, which is my special gift.)

Thanks for the feedback. Best wishes to all. ??

PS What is the difference between feedback and whining?

If I understood what it was trying to say, I would! ??

Thanks again. Did I mention that I LOVE this plugin?????

Nevermind! ?? Aborted.

Hiya ColdForged, in case you check back here: it worked and it is fantastic!!! Most excellent plugin, EVER.

One small question, if you get a sec:

On the config page, at first I got a fatal (oh my!) error:

FATAL: The directory you specified to cache the image files is not writeable from the Apache task. Either select a different directory or make the directory you specified writable by the Apache task (chmod 755 the directory).

It was already at 755. I swear. So I was stumped, which of course is my natural state.

Anyway, I then chmod’d my entire “blogname/wp-content/image-headline” directory to 777. It worked. No more fatal error. BUT . . . is that OK, security-wise, I mean, to have it at 777 forever, or should I change it back to 755 after I get the font I want up there? Or?

Thanks again for the great plugin. ??

ColdForged, thank you SO much for your reply! I really appreciate it. I can’t wait to try your plugin. It looks SO cool. Just what I have always wanted for blog design: more of my OWN typography. ??

I will try to find the ZIP file you mention, and then go about installing it to my plugins directory and then activating. I will then try uploading the font as you said. I have tons of neat fonts. Wish me luck. Cross fingers, etc. And THANK you again!

Would anyone else have a solution for this (as explained in my first post, above)? Thx.

Ha! I detect frustration.

Great rant.

Tried changing the permissions to 777 for the entire wp-content/plugin_manager directory. Still getting the same error when I log in with my FTP name and PW, after pressing the “temporary” button.

The “owner” of the directory is me. Which is correct, right? The image files for the plugin belong to “99.”

(“If you choose ‘temporary’, permissions will be restored between each use and you will be prompted for your ftp password each time you want to perform a one-click install.” This is the one I want to use.)

Wow, thanks for the fast reply. ??

I just checked the folder called “wp-content/plugin_manager” (assumed that was the one you meant?) and the permissions are 755. For the entire folder.

Are you saying I should have that be 777 instead? And leave it that way, forever? Is that safe, from a security standpoint? Sorry I don’t understand all this. I think I’m VERY close to having it all work, just that ONE little error line! Frustrating.

Thanks again!

Howdy. I installed this as directed (I think) but I am getting this:

Warning: fopen(wp-content/plugin_manager/params): failed to open stream: Permission denied in /mysite.com/wp-plugin-mgr.php on line 1271

The line in question (1271), in wp-plugin-mgr.php, reads like this:

if ($file = fopen ($location, "w"))

No idea what could be “wrong” with that line; it’s the default file I downloaded. Thus it must be something about the way my stuff is setup or something about the way things are interacting. This is where I get lost.

Other facts: The error occurs at launch of WPPM 1.7 itself (“click here”) from within admin area, under plugins. I assume WPPM should be “activated” there as well, but have tried it both ways, with the same error result. I do get the screenfull of plugin listings, but the error message is in there as well.

My host has NOT turned off ‘allow_url_fopen’.

I’m using the “temporary” option on the configuration screen.

No other permissions problems at this time. Just the one error (above).

I’ve tried changing from ‘use CURL’ to ‘don’t use CURL’ (line 23 modification, as instructed) and I get same error.

I have not tried to install any plugin(s) using the one-click feature yet.

I’ve never used any version of WPPM before. This is my first attempt to install it.

Don’t know if this is relevant, but I did change something a while back so my admin emails would not come from “Nobody” on my most excellent host’s Apache server. It was some easy piece of code found here somewhere. Sorry I don’t recall what/where more specifically.

Thanks in advance for any clues.

Now THAT is a sense of humor.