thanks

When my users try to attach more than 3-4 pictures then it just don’t upload them. It gives no error message, can I see error messages somewhere or do you know the solution?

Thanks
Christian

The links provided in the page http://teocomi.com/gd-star-rating-itegrating-comments/
on these sentences “this two tutorials part 1 and part 2″ are dead.

thanks a lot

array(
‘taxonomy’ => ‘post_tag’,
‘field’ => ‘slug’,
‘terms’ => ‘latest,wordpress,video’,
‘relation’ => ‘OR’
),
array(
‘taxonomy’ => ‘category’,
‘field’ => ‘id’,
‘terms’ => 1
)

so which would be your advice?
Manufcaturer and brands are just taxonomis right now used for filtering.

The point is that I have a lot of products, associated to brands, but I have also a custom post type created for those brands where I have a lot of info about them.

If I use now the new manufacturer feature from gdpc I will have conflict with slugs etc.

Any suggestion?

Thanks

The slug is forced to be “manufacturer” and “seller” or can it be modified?

Thanks

Congratulations on the 1.9 framework upgrade!
As an xScape user I certainly appreciate your commitment to further develop the product.
And of course look forward to taking Skyscape for a test run.
Thank you.

Regards,

You made great plugin! Thank you. I found a small problem that you may improve in the next version. When the widget is set to show the most votes, it shows the most votes with high ratings. i.e.:

2 votes, rating 5 then
2 votes, rating 5 then
1 vote, rating 5 then
1 vote, rating 5 …
(So where is 2 votes, rating 3?)

Best regards,
John

All the best,

Jim Blackwell

Good idea, I will add this to the list to implement.

Regards,
Milan

With any query, you need to limit data returned to minimize memory usage. With this table and values in it, it is not that critical, but I know of different cases, where plugins would store large amount of data, resulting in increase memory usage when page loads. And it has not difference if plugin creates one ow for all its settings as array, or hundred rows for individual settings. First solution is better, since it keeps table looking neater since less records are used, and you can see what each plugin uses, and in case when you need to remove plugin, you can find its records easier. And it minimizes the possibility of two plugins using same name for option name.

Milan

SELECT option_name, option_value FROM $wpdb->options WHERE autoload = ‘yes’

(You can find it in wp-includes/options.php )

So it’s just one query. Basically it’s a case of choosing between:

1. Multiple options stored in separate rows – return more rows

2. Serialized options stored in less number of rows – return fewer but larger rows

Does returning more rows vs. larger rows result in higher memory usage? I don’t think so. How could it! I bet the difference is negligible.

OTOH, storing options in separate rows is natural if you are coding in an OOP way. The options framework I coded does that. It also has an autoloader and uses separate class files.

in fact he said it was going to be released in 2010….

God bless you

Will GD Star Rating 2.0 born this year, or we must wait all 2013?

Happy New Year 2013

Jan

Also any idea when the actual 2.0 will be released and will it work with responsive themes?

Zorro…!

It also looks like there is a lot less options to pick in Alpha #3 vs 1.9.21 Prelude. Is made to be more simple or am I missing something.

Zorro..!