Jan van Dank

Well, I do understand that there are a lot of questions, bug reports and suggestions posted here so the author can’t reply to everything. However a quick note would help a lot.

All in all the plugin is ok but the support is horrible…

Custom editor buttons don’t work anymore with the latest WordPress (3.4.1) and qTranslate (2.5.31) version?!

The buttons are displayed but clicking on it will do nothing. Does anyone know a fix for this issue?

Hi Julio, thank you for adding this feature!

I’ll test it out soon and see if it does what I need…

Best regards,
Jan

Copying the style.css from the main theme to the child theme wouldn’t work because there already are two style.css files. (The child theme obviously overwrites styles of the main theme.)
Those two css files are the only ones which are not minimized by W3TC. Also gzipping them doesn’t work either!
I believe this might even be a bug because all other CSS files from the main theme are automatically minified/zipped without problems.

Right now there’s nothing I can do about it which is really bad because about 60KB are wasted due to this problem.

Thanks for trying to help though!

Yes, I’m using the automatic mode. I just changed to “manual” but unfortunately the help wizard doesn’t display any files to import. Maybe it’s because of the child theme or whatever…

The problem is that when I switch to manual mode I have to manage the javascript files as well, however W3TC does a great job here!
It really seems like a lot of work (7 CSS and 14 javascript files) just because W3TC doesn’t merge those other 2 CSS files into the large one.

If I could only point W3TC into right direction without having to manage all by hand…

I’m interested in this as well. Would you mind sharing what you’ve found out?

Currently I have the problem that W3TC minifies all CSS of plugins etc. However it does not minify the theme and child theme CSS files.
At the end 3 CSS files are loaded – and 2 of them ain’t even minifed! – which could be combined into just 1 I guess.

Any ideas?

Hi Mark, thanks for your detailed answer. Much appreciated!

@scottnelle
Now back to your plugin! ??

@esmi, @mark

Wow, I didn’t know that you guys at WordPress are that responsive. That’s really great!
Now only his website still needs to go away… ??

Idea: Why don’t you allow certain plugin classifications which the author (and users) can use, like:

• “shareware” – If a commercial version is available, which the authors often try to hide on the download page.
• “adware” – Advertisments are displayed. Some users seem to have no problem with that, don’t know if that’s OK with WordPress’ license though.
• “reduced adware” – Not sure about that, but some very popular plugins include commercial services by third-parties.
• “reduced adware 2” – Not sure about that one either, but some plugins display more or less unobtrusive notes on the created website like “Created with XYZ Plugin.”
• “donationware” – well, that’s optional as nearly all plugins have a donate button and that’s cool as long as it’s unobtrusive, optional and doesn’t hide any functionality.

Other classifications or special tags that could be used as well:
“phones home”, includes third-party services, commercial upgrade available etc. – You get the idea.

Of course the wording is up to you! Anyway, that would be some pretty good information you should add to the plugin download pages.

Regards,
Jan

Yes, seems that a WordPress moderator deleted that plugin. Great!
Unfortunately that developer still has some other plugins which don’t look that good either… In his development log you can see that he’s always changing advertisment links in his plugins, like “Thailand Real Estate” and stuff. ??

Because performance is really important to me I’m going to check out one of the “htaccess redirection” plugins than. Lets see if any is as straight-forward and easy as yours. Anyway, thanks for your explanation though!

I had to do the same to make it work:
https://www.ads-software.com/support/topic/fatal-error-tb-testimonialsphp-on-line-881-when-force_ssl_admin-is-true#post-2485681

OK further investigated in this issue and found the solution… Sometimes it’s so obvious that you simply don’t see it!
In the code it says “order_by” which is wrong. It should be “orderby“. By the way: This is also wrong in line 367 (displaying all testimonials); Also line 385 has “‘showposts’ => ‘-1’” and after it “‘showposts’ => 1“, I guess the first one can be removed?!

Anyway, here is the correct code which will enable you to not only choose a category and the limit but also the order direction:

$defaults = array(
	'cat'=>'',
	'limit'=>'-1',
	'order'=>'rand'
);
$args = wp_parse_args( str_replace('#038;','&',$id), $defaults );

$q = new WP_Query( array( 'post_type'=>'testimonial','post_status'=>'publish','showposts'=>$args['limit'],'orderby'=>$args['order'],'testimonial_category'=>$args['cat']));

Just use the code of ccgjosh and replace line 3-8 with the above one.
Example of usage: [testimonial id=’cat=Company&limit=4&order=rand’]
(more ordering options: here)

I just needed the same functionality – This should really be added to the next release of TB Testimonials!

Anyway, thank you ccgjosh. I tried your code and it seems to work fine. However, I also tried modifying it a little so that the order can be set as well:

$defaults = array(
	'cat'=>'',
	'limit'=>'-1',
	'order'=>'rand'
);
$args = wp_parse_args( str_replace('#038;','&',$id), $defaults );
$q = new WP_Query( array( 'post_type'=>'testimonial','post_status'=>'publish','showposts'=>$args['limit'],'order_by'=>$args['order'],'testimonial_category'=>$args['cat']));

Unfortunately the order of the testimonials doesn’t change. Any ideas how to fix this?

@mike Challis
Thank you for looking into this again! Well, you could call it “[x] Make compatible to qTranslate (experimental)“. ??

I’m having trouble as well:

Disabling the loop fixed. This isn’t an acceptable solution though…

@phdsigns
I’m glad that I was able to help you. ??

Still waiting for a “official” solution from the plugin developer though…
Maybe you can add something like a compatible mode option?
-> “[x] Make compatible to qTranslate”

Regards,
Jan