Ben Pollock

MelKeh, it looks like you got the slider working on The Fashion Journo. The site looks good.

Would you mind sharing what slider plugin you’re now using? Also, did you format anything special in its settings? Could it work from the setting panels, or did you have to do any code work?

Thanks.

To conclude:
I got my importer to work, finally, first by creating an uploads folder, manually, in wp-content … the WP install did not automatically create an uploads folder for some reason. I used Control Panel-File Manager to create the folder.

Second, in File Manager I changed the permission of wp-content and the new uploads folder to 777. Bingo, all worked smooth and fast.

Third, on a friend’s advice, once all was tested, I returned the permissions of these two folders to 755. At this level I have uploaded individual images.

I got my importer to work, finally, first by creating an uploads folder, manually, in wp-content … the WP install did not automatically create an uploads folder for some reason. I used Control Panel-File Manager to create the folder.

Second, in File Manager I changed the permission of wp-content and the new uploads folder to 777. Bingo, all worked smooth and fast.
Third, on a friend’s advice, once all was tested, I returned the permissions of these two folders to 755. At this level I have uploaded individual images.

Found workable solution:
1) Created an uploads folder in wp-content folder, via Control Panel.
2) Still an “unable to create director” error so I changed the default 755 permission to 777.

Now I could import a WordPress blog then individual media files as I could on other WP sites/

I have narrowed my question above. Or broadened it. When I upload media individually, I get a similar error message.
Unable to create directory /home/…./public_html/wp-content/uploads/2011/07. Is its parent directory writable by the server?

Changing the permission of wp-content to 777 is ill-advised. And it didn’t work.

The default folder already is wp-content/uploads , without a slash before wp-content, as was suggested in other thread topics. I wrote it again, didn’t work, and wrote wp-content/uploads/ with a concluding slash and that didn’t work.

I’m having the same problem uploading media. I look forward to some answers. My upload already was set to 777 but it doesn’t seem to make a difference.

My error message is similar. I’m noting it here (I have a separate thread as well) in case TonyAwards gets a response helpful to me. My “fixes” were similar and did not work, either.

The notice I got:
Before you can upload your import file, you will need to fix the following error:
Unable to create directory /home/longhand/public_html/wp-content/uploads/2011/07. Is its parent directory writable by the server?

Thank you, mrmist. The default permalink naming regimen restores nearly all linking functionality. Links to some but not all category names still come up with a 404, though. However, going back to my preference slug “day and name” is not restoring those to where they’ll link.
I can live with these things though until the upgrade.
Or until I find another problem, then I’ll be rummaging through Forums for a fix.

Ah, thanks, DCThree, the default permalink restores nearly all linking functionality. Links to some but not all category names still come up with a 404, but I can live with that for a while,, waiting for 2.6.1.

DCThree: Questions. Do I need to reset all 400-something of my years of posts to the default SQL style (if that’s what it is)? 2) Should I, because the permalink including the titles is very handy — for readers and me — and then wait for WordPress to fix this in the next day or two or six?

Me, too. I upgraded today, Saturday 19 July 2008, to 2.6 from last month’s 2.5.x, and now every internal link, for example to categories and jumps etc., comes up with a 404. I’ve tried three themes and the same thing happens so it’s not the theme matching up. The 404 message on each of them is worded somewhat differently, but all come up blank except for the blog’s index or home page. I’ve tested this at home and at work, so different servers and browsers.

I did the WordPress upgrade using Fantastico from the Control Panel of Hosting Matters. I’ve never had this problem before, and I’ve been using WordPress, upgraded using Fantastico, for 2.5 years.