gilvancn

Okay, thank you so much for the help.

Hi,
Thanks for your support and fantastic plugin.
I understand that nginx does not recognize the .htaccess.
My question is whether after some changes to the settings, they should reflect the .htaccess (to be read by the plugin and not by nginx)?
Another question: From what I see, the plugin works well in nginx. Is there any incompatibility of “All In One WP Security & Firewall” with nginx server or can use normally?

• This reply was modified 8 years, 4 months ago by gilvancn.
• This reply was modified 8 years, 4 months ago by gilvancn.

Hi,
Thanks for answering.
True, I know that.
But the plugin reads the .htaccess? Or not?
I ask this because I realized that only a part of the plugin settings are saved in the .htaccess.

• This reply was modified 8 years, 4 months ago by gilvancn.

The first problem was solved. It is due to the fact are logged in as admin. Not logged in is blocking the button “copy” and “paste”. ??

I continue with the second problem.

• This reply was modified 8 years, 4 months ago by gilvancn.
• This reply was modified 8 years, 4 months ago by gilvancn.

Sorry, it’s all right now.

There was renaming the “wp-postratings-master” folder to “wp-postratings”.

So I was having problems. Now everything is working, thank you.

I got it, grateful for your response.

I wonder only because vers?o 1.84 is not allowing to new reviews in posts?

Also exclude from the server the previous version 1.83.2 which is disabled, is giving 404 error in the plugin management page: mysite.com/wp-admin/admin.php?page=wp-postratings/postratings-manager.php

One more question: You can send the new version link again? Why not launch this new version in the repository WP yet?

Thanks for the support and excuse me for questions! ??

Hi @lester Chan,

You suggested here to download an unofficial update (version 1.84) and I downloaded and ran formal without presenting the mistakes I mentioned here in this topic.

But now I was no longer doing the evaluations.

I had to go back to version 1.83.2 and consequently returned the same mistakes previously mentioned here.

Any alternatives?

Okay @lester Chan,

Thank you for your explanations.
I will follow the instructions. ??

Hi @lester Chan,

Thank you for your fast answer.

More Rich Snippets “image” is still with the error only use the code in functions.php provided by you.

An alternative for zero errors is to define a “featured image” in the post.

However, I see some problems in these approaches:

1. Using the featured image schema takes the smaller image (150×150). It would be interesting to set a larger image?

2. The code in functions leave the field “url” in question (in eschema) standard for all other pages that have rich snippets. This is the best practice?

Truth. Confirmed now that really this is the incompatibility.

The problem is that I need at least 1.3.2 version for other things work. ??

Grateful for his return! ??

I did a test running only Icegram and no other plugin.
The Icegram continued without work in theme.

The version of jquery used in theme is 1.4.3.

This is the theme:
https://www.mediafire.com/download/ijctodb5134o4kr/example11.zip

Solved problem. Grateful to Chouby.
If anyone has the same problem, see more details at: https://github.com/polylang/polylang/issues/8#issuecomment-222366869

Okay, ready created, thank you.
https://github.com/polylang/polylang/issues/8

Open an issue in the Github reporting the same error that reported here?

Hi sanjayidhatiya,
Thanks for that alternative.

But it did not work for me.
Moreover it is not advisable to edit the plugin for an update all changes are lost.

Another detail is that the plugin “Page Restrict” is outdated.