saymonz

Everything is fine again! Thanks a lot!

It’s public, on saymonz.net. My theme is JC One Lite. I cant’t figure where the problem is.

Great, thanks!

Probably not related but now the fallback redirection is always executed, with Firefox and Chrome.

Apparently, that’s this test who cause the problem :
if (newCommentForm.length == 0) return wpac_fallback();

My comment form have the default #commentform id, so I left the option empty and the default value is correctly reported in my page header. I don’t know JavaScript well enough to fix it.

Yay, no more issue in YARPP! Thanks!

However, I still have this long posting issue. I already have a posting time about ~10s without your plugin, but when it’s activated I have seen as much as 26s (recorded with the Google Chrome inspector)!

Again, I don’t blame your plugin for that, I have a really cheap web hosting (that is widely sufficient for my needs though), it just would be great to have the “Posting comment” message box on screen (no timeout) until another message (confirmation or error) appears. That could be done easily by replacing the line 22 in wp-ajaxify-comments.js with:

timeout: (type == "loading") ? 0 : 3000,0

I applied this with success on my blog, but I have to do this modification on each update unless you integrate this directly out of the box ??

— saymonz

Hi!

Great for scrolling and address bar change.

For thhe long posting issue, I simply have a shitty web host I think. Si keeping the posting message on screen until the comment is effectively posted cannot be a bad idea.

Also, I noticed that whenever your plugin is activated, the YARPP admin page is all messed up (mouseover help texts showed inline and stuff). This is no big deal (YARPP still usable), but would be great to have this fixed.

— saymonz

It would also be great to change the URL showed in the browser address bar to the direct URL of the just posted comment (with correct anchor). A smooth scrolling to that anchor would be great to.

That’s fine. Maybe I’ll get a look into the code myself, but I always get lost in WordPress-related code (though I’m actually not a beginner in PHP coding).

Thanks for your help anyway!

Nothing changed with that version. Keywords are always weird with wp-Typography hyphenation function turned on.

Here is wp-Typography on WordPress plugin directory. I use the latest version (2.0.4).

Here’s an example of keywords selected by YARPP for one of my posts without wp-Typography :
“cest quon the souvenirs jai clip version audio pages blowing justine1991 orphelin 2011 pourra seront lecteur choses survirais mêmes gouffre “

And with wp-Typography enabled :
“qu ver per sonne the ai ve pages aurais der sion lec audio clip rais nirs ter jus rable orphelin “

As you can see, YARPP selects half-words as keyboard, probably because of the hyphenation feature of wp-Typography (I use it with default settings except for the hyphenation rules language wich is set to french).

wp-Typography remove all default wptexturize filters and add its own.

EDIT : I confirm that hyphenation causes that. I’m not a WordPress developper but if you have a simple way to bypass text filters and just get the content as it’s in database, that would solve the problem.

Yeah, looked directly in database via phpMyAdmin. Keywords selection totally changed after deactivating wp-Typography.

That’s strange, wp-Typography aplly its modifications to the page just before it’s sent to the client, so it shouldn’t affect the data that YARPP gather from database.

Good. Be aware that I transformed the list from the link I gave without checking if every words are pertinent… I hope it is (and as I can see on my own blog, that’s better than using the english list on french texts anyway) but that sure could be better.

What about the problem with wp-Typography?

WTF! Simply replace line 2 685 in /wp-includes/functions.php
$wp_smiliessearch .= preg_quote($rest);
by
$wp_smiliessearch .= preg_quote($rest,'/');
and it works!

Is there any way to use the slash in smilies code ? The “:/” smiley is popular enough to justify that, and other PHP softwares handles it just fine…