zhonglyor

Hi Marcel,

Here is the Russian translation for 1.4.9: https://yadi.sk/d/eJmLAS7RiyeMg

Thank you for making new captcha to be able to work with renamed wp-content directory. Now it works fine.

Hi Marcel,

Here is the Russian translation for 1.4.9: https://yadi.sk/d/eJmLAS7RiyeMg

Thank you for making new captcha to be able to work with renamed wp-content directory. Now it works fine.

I have a couple of wishes. They aren’t essential but may be they won’t be difficult for you.

1) Could you give the reCAPTCHA back so the admin could choose between reCAPTCHA and Really Simple CAPTCHA?

2) I have WP Super Cache installed. As I can see, only main page of the guestbook is cached. Something like this: https://wpsite.com/guestbook/. All pages with numbers are not cached. Their address looks like this one: https://wpsite.com/guestbook/?pageNum=3. I guess the reason may be in the address format. What if it would look like https://wpsite.com/guestbook/page3 or https://wpsite.com/guestbook/all (when “show all entries” option is enabled)? Is it possible to make the numeric pages to be cached?

Russian translation for 1.4.3: https://yadi.sk/d/zGYuu7pKhwzhS

I’ve noticed the title “Donate to the EFF.” (in the main page of the plugin) has stopped being translated (though the translation is still present in the .po file).

Russian translation for 1.3.7: https://yadi.sk/d/hAm4x7KLh63PC

Russian translation for 1.3.5: https://yadi.sk/d/WZ3gNacjgnwYW

Russian translation for 1.3.3: https://yadi.sk/d/4kXn7Cm2gcBCx

Hello Marcel,

Here is yet another updated Russian translation: https://yadi.sk/d/f43CQruMg9UbE

Hello Marcel,

Here is the updated Russian translation: https://yadi.sk/d/ZFevZFqGfYQAe

Hello Marcel,

Custom anti-spam question works with Russian well now, thank you. As to forced moderation of suspicious messages, your idea was brilliant indeed. This is even better than the thing I asked initially.

When I was checking all of this stuff I noticed a little typo in my Russian translation. Only one symbol was mistyped. Nevertheless, you can find the corrected translation here: https://yadi.sk/d/a7WFbsQ_fRYC6

What a shame, I’m not a PHP-programmer and I’ve been able to understand nothing of this piece of code ??

What place should I paste it and what string should I replace “$entry[‘date’] = current_time( ‘timestamp’ );” with?

OK, I don’t dare to insist ??

I’m just working on a new site which’s content is expected to cause quite live reaction. And some percent of readers are expected to be “haters”. So they might want to seek ways to do damage ??

As to premoderation, it could work, of course. However, as I mentioned above, quite active interest is expected. So in case of big number of new Guestbook entries, premoderation would become too time-consuming.

Hello Marcel, thank you for flash-like response.

As some new features appeared in the plugin, I have updated my Russian translation. Please find it here: https://yadi.sk/d/Djp2vnwRfM4xJ

My server configuration is following:

Apache version 2.2.29
PHP version 5.3.29
MySQL version 5.5.32-cll-lve
Architecture x86_64
Operating system linux

It still can’t show russian anti-spam custom question normally.

As to limiting the length of Guestbook entries. You have just limited the number of words that are to be displayed in the Guestbook. However

1) The real size of entries is still unlimited and they still can burden MySQL database.

2) It is very easy to outwit the word-count limit by simply typing a single very long word. So a malicious visitor still can spoil the entire Guesbook by entering (for example) one thousand “A” symbols continously without any gap. This leads to very ugly result with the line running out of the screen (though depends on theme). Try it yourself.

3) And the same is with the Gwolle Guestbook widget.

4) And the same is with the “visitor name” field both for the Guestbook and for the widget. Just try to enter username of 1000 continous symbols and look at the result.

All of this allows a malicious visitor to perform a sort of DoS attack (As you probably have already guessed, I am very concerned of security issues. Please accept my apologies about this ?? )

So, what solution seems to be right…

1) To limit the size of entries being entered rather than the size being displayed.

2) To limit the size of entries by character count rather than by word count.

3) To limit the size of “username”.

Workarounded by merging “&nopaging=true” to the querry string.
I.e. the shortcode used is [archivist query=”author=author_user_ID_here&nopaging=true”].