Laurent OneChai

I’m on a single site

I just found the option to disable UTF8 but it doesn’t make any difference. With or without this option, all the éèà… etc are broken because of character encoding issue.
This was actually not the case with previous versions of commentluv

Ok, I got around it. This appeared with the latest release because it is using now htmlentities to protect against code injection which is great. The side effect however is for people using special characters in their language, everything gets … funny to say the least.

Using htmlentities is fine but then, the email has to be send not in play text but in html to make it readable.

And htmlentities is applied twice which make things even worst.

So here is my patch:
Line 114, has to specify UTF-8 encoding. So replace

$_POST['scf_message']  = htmlentities(stripslashes(trim($_POST['scf_message'])));

with

$_POST['scf_message']  = htmlentities(stripslashes(trim($_POST['scf_message'])), ENT_QUOTES, 'UTF-8');

line 216, send email in html so replace

$headers  .= "Content-Type: text/plain; charset=\"" . get_option('blog_charset') . "\"";

with

$headers  .= "Content-Type: text/html; charset=\"" . get_option('blog_charset') . "\"";

line 218, htmlentities should no be done twice so replace

$message   = htmlentities($_POST['scf_message']);

with

$message   = $_POST['scf_message'];

line 240, because the email in now in html, has to convert cr into br so replace

$fullmsg = stripslashes(strip_tags(trim($fullmsg)));

with

$fullmsg = nl2br(stripslashes(strip_tags(trim($fullmsg))));

A last note, I’m nothing like an expert in security so I think this code is ok but no garantie. I’ll send this patch to the author and see what he says.

Yep, the amdin plugin page turns in italic with tweetily.
To fix that, in /wp-content/plugins/tweetily-tweet-wordpress-posts-automatically/css/tweet-old-post.css, change the first line, replace
.desc{
by

.toplevel_page_Tweetily .desc{

That would be nice is this could be pushed into the next release

Same here but it works if you add them one by one. For instance, I use FB, twitter, G+ and Pinterest and just add this :

<?php dd_fblike_xfbml_generate('Like Button Count') ?>
<?php dd_google1_generate('Compact (20px)') ?>
<?php dd_twitter_generate('Compact','twitter_username') ?>
<?php dd_pinterest_generate('Compact') ?>

Same issue here. In my case, caching is the issue. It works fine if I don’t cache my pages. But as soon as WP Super Cache is enabled, the box keeps displaying even if you close it.
Great plugin aside that but unfortunately, I can’t really use with this cache issue.

I actually had to temporarily change the permission on wp-content so that it could create the file wp-content/backupsindex.php that didn’t exist before.
Everything is working fine again now.

Ok, thanks I’ll check with YARPP then …

Same issue for me. I can still change the SEO title for the articles published before the update but not for the new ones.

A bit annoyed with this too. I don’t need and I don’t want all the stuff in jetpack. So I’ll stick to the old version of After the deadline I suppose …

I can’t believe that with so many people using NG, I found only your post and another one 4 months older without any answer either talking about this issue. Ending up with images way heavier than their should be is not a minor issue especially for slideshow with big images !!! If I compare the image generated by the NG importer and the original one (same size) that I saved in gimp with jpeg 85% quality, the NG one is 5 times bigger (I mean, the file not the image of course) !! In terms of loading time, it’s a complete waste.
I played quite a bit with the different options to try to understand the issue better.
– When you’re in the image importer, if you uncheck the option “Scale images to max width …” then you end up with exactly the image that you uploaded. That means that if you use any tool before end to resize your image, you just uncheck this option and you’re fine.
– In NG options, in the images tab, you can set the “image quality” option to any value, it doesn’t make any difference, the resulting image has always the same file size. And that seems to be the issue, the jpeg exporter is always set to 100% quality. If you try with another tool (I tried with gimp) to resize your image and save it in jpeg with the maximum quality, you end up with more or less the same image size !!

Did you find any clue on that? I’ve got the very same problem so I ended up not using the nextgen importer but putting the images with the right size directly into the directory and get nextgen to scan this directory for new images.

Did you find any clue on that? I’ve got the very same problem so I ended up not using the nextgen importer but putting the images with the right size directly into the directory and get nextgen to scan this directory for new images.

In the css, for .ngg-gallery-thumbnail-box add a width in %

.ngg-gallery-thumbnail-box {
	float: left;
	width: 20%;
}

This for instance will force to have 5 images (100/5=20%) per row whatever the width of the row.

From Manage Gallery, you’ve choosen a gallery, then click on the “Sort Gallery” button next to the Bulk Action box, drag and drop your thumbs to reorder them and click “Update Sort Order” on the top of the page ?
It works fine for me with WP 3.4.1 and NextGen 1.9.3 without doing anything more than that.