GD Rating System

Yes. POT file is provided as a base for translation in the root folder for each plugin. Translation files should go into languages directory, and WordPress must be set to your language to load the file. As an alternative, translation file can go into wp-content/languages/plugins directory.

The file name for translated and compiled MO file must be the same as POT file with the addition of language code: {plugin-name}-{language-code}.mo.

You can check out this for translating plugins using POEdit program:
support.dev4press.com/kb/article/translating-plugins-or-themes-using-poedit

Yes. Each site in the network can activate and use the plugin.

No. GD Rating System is completely new and different plugin, that has nothing in common with old GD Star Rating plugin.

Yes. GD Rating System supports import of rating data from:

• GD Star Rating
• WP PostRatings
• Yet Another Stars Rating

Yes. Plugin includes Dynamic Load addon that will load rating blocks through AJAX. This addon is disabled by default, and if you use cache plugins, just enable this addon from plugin Settings -> Extensions panel.

GD Rating System is adding a fully functional and standardized rich snippet for rating or review, and you can test all your posts to confirm that the rating snippet is correct. But, there is no way to influence Google to show the snippet inside search results. There is no way to know how, why and when Google displays rich snippets and even big websites like IMDb or Amazon very often don’t have the rich snippets displayed.

Check out this user guide about setting up the rating rich snippets.

[gdkob_user_guide user_guide=”51422″ bgcolor=”#f4f4f4″ /]

If you don’t see stars, but instead there are letters S, this means that font with icons used by the plugin is not loaded by the browsers. The reason for this is that most likely your website is loading a font from CDN and some browsers are enforcing CORS policy. To get more information about it, and the solution on how to fix it, check out this article: Loading fonts from CDN.

Alignment for complex HTML elements can be a very tricky issue, and it largely depends on the container and styling it has. The plugin has options to add alignment classes to the rating block, but, these classes don’t include actual styling and they are meant to be styled individually for the theme used.

To center element, that element should have the width set. But, if you set width for the rating block, that block will no longer be responsive. The plugin automatically makes stars smaller for the rating block to fit the current screen with. Having fixed width set for the rating block will prevent the plugin from making it responsive.

You can use CSS for responsive breakpoints to set different widths, but that too depends on the theme (themes usually have different breakpoints and different grid systems), and it is best to style rating block alignment for each individual theme to make sure alignment works for your theme. Also, depending on the theme and the grid system use, there might be some other way to center elements.

Plugin alignment feature is only placeholder class name, styling must be defined for theme.

When new plugin version is released, it usually contains changes to CSS and JavaScript. If you use some sort of cache (plugin for cache, server side cache, CDN), and depending on your system configuration, CSS and JS files can be cached, and even with new version of the plugin installed, old files can be served from cache.

Whenever you update the plugin, make sure to clear all cached data from cache plugin, server-side cache, CDN and finally browser cache.

This is always the issue with the page cache. The plugin supports the use of cache plugins, but in that case, it needs to get current ratings through AJAX to avoid showing old cached page. The plugin includes Dynamic Load addon that will load rating blocks through AJAX. This addon is disabled by default, and if you use cache plugins, just enable this addon from plugin Settings -> Extensions panel.

All Dev4Press plugins and addons require jQuery. But, they will work only if the jQuery is loaded with the WordPress proper Enqueue method. If you are replacing jQuery that comes with WordPress with some other version loaded from other location, my plugins will not function properly, and that goes the same for most of the other WordPress plugins that depend on the proper way for loading jQuery.

This can happen if you are using GD Rating System Pro additional addons (like Multi Ratings or User Reviews addon). If that happens, make sure to disable GD Rating System Pro and all addons for it, and upgrade main plugin and all its addons, and reactivate them after the upgrade is done.

In few instances reported so far, the Thumbs Rating values have become invalid, showing million or billion high ratings. So far, we were unable to find the cause of the problem, but it was caused by something in the early 3.x versions of the plugin. To fix this issue, you need to recalculate the Thumbs Rating, and the ratings will be fixed.

To do that, open the Rating System plugin admin menu, go to Tools and open Recalculate Data tool. Make sure to read all the provided information there. Find the Thumbs Rating box, and enable recalculation for it. Click the Recalculate button, and wait for the process to run, you will see the progress information. Once it is done, check the posts that had invalid ratings to confirm that the problem has been solved.

Also, it is recommended to update plugin to the latest available version before doing this.

All the shortcodes can be generated using the Shortcodes Builder menu in the GD Rating System admin side menu, and you can simply select the values you need, and the builder will prepare the shortcode you can copy and use where you need them.

All Dev4Press free and lite plugins can be translated via WordPress.org and their translation services. Each plugin on WordPress.org has support for translation, and you can get to it through the plugin Developer panel. To translate plugins on WordPress.org, you need a WordPress.org account. But, if you want to handle translations on your own, each plugin has a POT file with the list of all translation strings