luffer

That doesn’t help when you’re writing a new post. Navigating away from the post to check tags is slower and far less convenient than just having the most used tags listed right there to click on.

It’s like saying “we removed the speedometer from your cars dashboard, but if you need to know how fast you were going, just look under the hood as we’ve got a record of your speed stored in there.”

In my view this is a classic case of form over function. Make something look clean, sleek and tidy at the expense of the functionality. Whereas, given that this is a CMS it should be that functionality takes precedence over appearance.

When it comes to content consumption, I’d agree that removing clutter and being minimalist is advantageous. But we are taking about content creation here, where speed and accuracy should take priority. This current interface allows me down AND causes inconsistency with tags.

This is especially true with multiple authors who may use different, but similar tags when they should be using the same one from the list which is now hidden to the author.

Unfortunately this topic got derailed by @krauch and the people who develop WordPress have just ignored the issue. Pretty much what I’ve become accustomed to with WordPress now, it’s sad, but I just give up trying.

Yes, I realise that, but the old editor used to have a list of “most used tags” that catered for most of the posts I made and I could just click on them. Now I have to type them out each time, which leads to errors with typo’s creeping in.

It seems like a far less efficient method now.

I care for other users who I want to warn about you and your business practises! I don’t care what happens to this plugin.

Honestly don’t care any more. I removed your plugin, I have no faith or trust in you despite having made donations to you in the past. Hopefully someone will use your GNU code to release a new version and we can all migrate to that. You’ll never get anything from me!

Reply from the support team:

I’ve checked your website’s home page and it looks like Photon is currently disabled.

From the screenshots at the thread, it looks like they maybe taken from a Retina display? Photon extension brings in double sized images, on high resolution screens.

To make sure the image dimensions are always followed, same as set in your widget settings, can you please add following CSS code at bottom of your child theme’s “style.css” file:

.home-middle .featured-content .entry .entry-image {
max-width: 360px;
}

.home-bottom .featured-content .entry .entry-image {
max-width: 150px;
}

Once you’ve added the code clear your browser’s and plugin cache and check with Photon extension again.

I hope this helps! Please let us know how it goes and if you have any further information or questions.

I wasn’t using a retina display, it was just several screenshots stitched together to form a single image that showed everything at once. But is it correct that Photon loads “double sized images, on high resolution screens”? I don’t upload high resolution images to begin with, so unless you’re up-scaling I’m not sure that’s correct?

Anyway, I’ve not tried their fix yet, but does it sound right? I guess I’ll give it a go anyway because I’ve nothing to lose and can easily take it out again!

I’ve raised a support ticket with StudioPress, just have to wait and hope for them to respond I guess.

It runs on Genesis child theme, which you’ve probably heard of it? It’s a commercial theme so I can’t really send you a link to download it.

that’s the thing; it’s the exact same form submit … could you have some software (mod_security or something similar) that is checking incoming requests and blocking in some cases?

I use Theme My Login which blocks access to wp-login.php but nothing else that I know of.

and did you have the inline&defer problem on 2.0.2 as well?

Yes

I only get a 404 error when I try to save with the “inline & defer” option enabled. I never get a 404 on my frontend, it’s just in the admin area.

Where do you redirect users to when they hit the “save” button that’s different with the “inline and defer” option enabled?

This is an upgrade, but a fairly recent install. Only been using it about a week.

Well it does give a 404 error when I try and use Inline and Defer CSS.. so is it?

I’ve had to use the “Inline all CSS” option which may be causing a large cache?

I wanted to use the “Inline and Defer CSS” option, but when I enabled that option and entered my above the fold CSS the site would fail and return a 404 error when I saved.

Redirection based on role would be a great idea!

I never actually disabled it, because by the time I got the 404 issue resolved Publicize was working for me again. I probably will remove it though because I’m not using any of its features, it’s just a legacy thing.