ed73

Well, I’ve found a solution. If you’re using pages and you’ve want a static home page then try the following to get the 404 working anything like normal.

1. Create a page called DO NOT DELETE and publish it.
2. Make a note of the ID of the DO NOT DELETE page.
3. Go to DESIGN / THEME EDITOR / SIDEBAR.
4. Find wp_list_pages and add the parameter “exclude=11”
5. In my instance the ID was 11 but change yours to the ID noted in step 2.
6. Go to SETTINGS / READING and select STATIC PAGE.
7. Set FRONT PAGE to ‘home’.
8. Set POSTS PAGE to the DO NOT DELETE page.

This should now allow you to have pages only, set a static home page and have the 404.php page show up faithfully on error. Because of step 4 above the DO NOT DELETE page will not show up in the navigation system so your visitors will be unaware of it.

I know it seems convoluted but it works.

The problem with that though Mellco is the post page you select will then fail and turn into a 404 so it appears you have little choice but to forfeit the 404 in order to have a working website.

It clearly needs to be revised.

Try this thread Nitallica. It solved my 404 problem.

I’m having exactly the same problem.

If you go to Settings / Reading then play with the combination of static page selections you’ll see you switch between 404 working but home page not, then vice versa.

I currently don’t have any posts, just pages and with static pages set, front page is set to ‘home’ and posts page is set to nothing. This means 404 won’t work. When I select ‘home’ in the posts page part of the static page selection then 404’s DO work but my home page fails and lists multiple entries.

Manually amending the .htaccess file has made no difference either. If someone does manage to solve this please post in these forums and help us out.

Thanks.

I too have over 1000 categories and WordPress just can’t handle it. It’s obviously doing too much work looping when loading categories in the admin interface for it to list more than a couple of hundred.

I think the answer to this is: WordPress can’t handle loads of pages or categories, only posts.

A quick update.

Changing:

wp_get_attachment_link(0, 'medium', false);

to:

wp_get_attachment_link(0, 'medium', true);

changes the link url from the raw file to the permalink of the attachment which is an improvement but I’d still like to remove the link altogether.

I’m assuming the clue is in the function name wp_get_attachment_link and that there is some alternative function that will achieve my goal but documentation regarding this is thin on the ground.

Thanks for reading and any help appreciated.

I too receive the error “specified file failed upload test”.

In IE7
I receive this error and the picture will not show despite the image successfully being listed in the media gallery. However when trying to load the image to place it into a post nothing happens and I just receive a script error.

In Firefox
Despite still receiving the “upload test” error, this works as it should and allows me to insert an image into the post.

I’ve tried both the .htaccess solution and made the changes outlined in the bug tracker but to no avail, the problem persists.

Unfortunately I can’t add anything more to it than that and desparately await a fix.

Found it. It was called Sunrise [Link].

Bad! The particular theme was a gooden too. I thought it was called Sunset **** or other but nothing turned up on search. If anyone can think of it, please post as someone has their heart set on that particular theme.

Thanks,
Ed.

You’ll need to hand code your posts if you want to validate with a Strict Doctype. Another point is it doesn’t output HTML, only XHTML which doesn’t suit me either as I write HTML Strict only.

I have solved this problem. After an upgrade, the host defaults to read only and I had to create a tmp folder in the root. As part of the host control panel, there is an option to set this new tmp folder as “upload_tmp_dir” in the PHP config settings.

This solved the upload problem in my case and I’m wondering if this is something that other hosts are doing. If you completely run out of options with the upload problem, get in touch with the host and ask them about “upload_tmp_dir”.

I’m having the same problem (https://www.ads-software.com/support/topic/107994) and it appears many others are too. The ‘solution’ is to ensure you have write permissions on the directory that WordPress aims to upload the image. In my case, I do have write permissions and still get the error. It does seem strange that the folders are created right down to month level yet the image will not be written to the server. If there were permission issues then surely the folders wouldn’t have been able to be created?

I hope you discover the problem and resolve the issue. If/when you do, please post the answer!

Since this post exactly describes my problem I’ll add my woes.

I teach businesses about the web and have setup around 100 various incarnations of WordPress installations on our server, all without fail. Lately though I have setup 5 all showing the same problem which is:

The uploaded file could not be moved to /home/**domain**/public_html/wp-content/uploads.
Warning: Cannot modify header information – headers already sent by (output started at /home/**domain**/public_html/wp-admin/admin-functions.php:1879) in /home/**domain**/public_html/wp-includes/functions.php on line 1219

Looking at the various posts on this matter it looks like certain FTP software isn’t persisting the settings and what we think is CHMOD777 really isn’t. I’ve tried 2 different FTP applications and also used the hosting control panel to set CHMOD but to no avail. The error persists. Strangely I don’t receive this error on my host but I do on another.

How much of this is down to the hosting server rather than the FTP software? I’ve combed this forum and tried every trick in the book. Fundamentally, it has to be permissions since it’s a ‘write’ action but it’s certainly stubborn and presenting all sorts of problems for me so despite all the posted threads above, the trouble continues.

Another note…

The aim is to have a permalink structure such as:

• https://www.website.com/1867/03/25/

Even better would be:

• https://www.website.com/1867/March/25/

The aim is to create a really usable, intuitive and navigable site but since we looked at the categorisation it would mean:

1867
– January
– February
– March
– – 01
– – 02
– – 03
– April

This would become massively unwieldly very quickly, both in the administrative panel and the public listings (although clever CSS/JScript can help).