schamane

What are you using now instead?

Screenshot made with a white-on-black O/S theme:
https://666kb.com/i/deeigln4yyc2ladfm.png — all fine

Screenshot made with a black-on-white O/S theme:
https://666kb.com/i/deeih1sg2r8vhzkhu.png — input field backgrounds are dark

I tried to dig deeper but I fail to understand what is actually going on. And I made a mistake in my original post: body has a background color set, and it is white.

I guess this is because of special handling of form inputs by Firefox.

I suppose by “other themes” you mean WordPress themes. I tried the preview of https://www.ads-software.com/themes/twentysixteen/ . There all is fine. Looking at the CSS I see that also has
background-image: -webkit-linear-gradient(rgba(255, 255, 255, 0), rgba(255, 255, 255, 0));
(I really wonder why), however, there is also background: #f7f7f7;. So, it works.

• This reply was modified 8 years ago by schamane. Reason: cosmetics

In regard of accessibility this is indeed critical: Bold i is difficult to distinguish from l. This can be clearly seen when bold i is compared to normal i and e.g. i in HTML anchors (see menu). The latter are easy to read compared to bold i in the text.

Checked with Firefox 49.2 on a 1400×1050 TFT monitor. Font according to FF is LibreFranklin-ExtraBold.

Screenshot: https://666kb.com/i/dee0yqouacqq439mq.png

That explains why not even the preview works!? A pity. The thumbnail looks promising.

It should have been fixed already but there was a bug in the fixes: https://core.trac.www.ads-software.com/ticket/26781
It will be fixed in 3.8.1. If 3.8.1 is published before February, you are fine if you manually fix permissions of the 2014/01 directory (and all old files with wrong permissions).

It’s a bug. I haven’t yet found the precise error but the code of function wp_mkdir_p in wp-includes/functions.php was changed in 3.7. This breaks permissions of newly created upload directories (e.g. 2013/12). The permissions of files are inherited from the directory. So, the fact that they are wrong is just a consequence.
Unfortunately, it seems, nobody has reported this bug yet ??

TMM, you are affected by the problem with permissions that came with 3.7.0 or 3.7.1. This means that all permissions are correct accept those of wp-content/uploads/2013/11 and very likely all files in this directory. So, as WPyogi suggested, check the permissions of these items.

How to do this depends on your setup/provider/tools/etc.. If you need help give us more details. If you know FTP, that’s the an easy way. Very often right-clicking the directory (here the one called ’11’) allows you to change permissions. It should be 755 (or in words, read+execute for others/everyone).

The files in the directory should have 644 (readable for others/everyone).

HTH ??

Please note that several cases of problems with image uploads in 3.7.1 have been reported in the forum. As a workaround fixing permissions is recommended. Cf. e.g https://www.ads-software.com/support/topic/images-uploaded-to-371-all-broken-wont-display-at-all though this is not limited to featured images.

You are using 3.7.x? Did you check if the permissions of uploaded files/images are correct? See WordPress ? Support ? Images uploaded to 3.7.1 all broken won’t display at all for a resolution of this case.

@willartist: By setting permissions of directory “11” to 0755 you make it world-readable. That’s relatively safe because basically you want the uploads to be readable.

However, it might make the directory index/listing and otherwise “hidden” (unpublished) uploads visible, too. On your blog that is the case, see https://www.willbeck.com/artblog/wp-content/uploads/2013/11/ but it is also the case for older directories.

To disable directory indices see e.g. https://wiki.apache.org/httpd/DirectoryListings or simply create an empty file index.htm(l) in the directory.

I just had the same/similar/related problem. I skipped 3.7 and updated to 3.7.1 directly. Image uploads were broken due to wrong permissions (0600).

It seems that WP 3.7 still chooses to inherit file permissions from the permissions of the directory (BTW, I strongly disagree with this approach).

My WP is set to upload into wp-content/uploads/YYYY/MM, that’s …/2013/11 for now. Yesterday, directory “11” was freshly created with permisssions 0700 even though “2013” is 0755. Hence, all uploads ended up as 0600 and were unreadable on the web. Changing permissions of “11” to 0755 fixed it for new uploads.

However, it seems there’s once again a bug in handling permissions :/

I agree that in some areas colors are not providing enough contrast. However, the color of the menu is a feature, not a bug. Menus appear on mouse-over.
Pages are working fine here.

Apparently, iBlog2 has been removed and has superseded by iBlog, though even this is outdated. Updated versions I only found at the authors webpage.

iBlog2 is gone again. What’s going on here? Has it been superseded by https://www.ads-software.com/extend/themes/iblog ?

P.S.: 3.1.5/3.1.8 is also available from the authors at https://www.pagelines.com/free-themes/iBlog.zip

iBlog2 is up again at https://www.ads-software.com/extend/themes/iblog2
Thanks everyone!