jonathantimar

A big thank you to Piet for continuing with this plugin.

It is a real shame that Samuel decided to go on the attack after making some mis-guided changes to his plugin. His attitude is truly reprehensible.

Cheers.

Why would I try it when it is now completely useless? The entire reason I used the plugin was to avoid installing the bloated Jetpack plugin. Now that I have to install it anyway what is the point? There isn’t one, I can disable Jetpack modules easily enough on my own.

Rather that accept legitimate criticism you are instead choosing to attack and insult your users. Pretty unbelievable.

The one star review stands based on what condescending and arrogant [quack] the plugin author clearly is.

That’s great, thanks. I had traced it to the Javascript but I couldn’t figure out how to fix it myself.

It took me a long time to figure it out, but I finally was able to defeat Google and their sneaky tactics. I have written a comprehensive guide so that you can stop Google image search from stealing your photos.

I disagree with the OP entirely. I upgraded without any problems, and while it DID cause some issues with my (custom bespoke) theme, they were easily fixed with some basic search and replace in my style sheets, all of which was clearly documented.

Using the Google Breakdance plugin. Actually I just took the code and added it to functions.php and htacess. Seems to be working out fine. Don’t know about any server load issues yet.

Something is going to have to be done about Google. The ammount of power they have is just dangerous.

“Trialware is not allowed in the repository. It’s perfectly fine to attempt to upsell the user on other products and features, but a) not in an annoying manner and b) not by disabling functionality after some time period. Similarly, you cannot “cripple” functionality in the plugin and then ask for payment or provide a code to unlock the functionality. All code hosted by www.ads-software.com servers must be free and fully-functional. If you want to sell advanced features for a plugin (such as a “pro” version), then you must sell and serve that code from your own site, we will not host it on our servers.”

“The plugin must not embed external links on the public site (like a “powered by” link) without explicitly asking the user’s permission. Any such options in the plugin must default to NOT show the link.”

Feature was removed without warning. Not very cool. I don’t mind giving credit if it’s optional and I can control where it appears, but this really bothered me.

Anyway, a better option that does not require editing the plugin core (which will be overwritten when the plugin updates) is to add this to your functions.php file in your theme:

// Remove AdRotate Plugin Hi-jacking wp_meta
remove_action(‘wp_meta’, ‘adrotate_meta’);

Hi again,

Obviously I was a bit harsh, and I am sorry for the name calling. It was obviously premature.

I imagine you didn’t consider the possible fallout from your decision. In reality, I didn’t even mind losing some of the advanced functionality, as luckily I had not yet had need for it. The only thing that truly urked me is the fact that displaying the “credit” suddenly became non optional, and broke my site’s layout. That really bothered me. If you’re plugin is good, people will promote it without being forced.

I’ll CC this to your email. Thanks.

I read the changelog each time before updating. That’s all I have time for. As it is you made it inconvenient by not posting it on the repository. Anyway, never saw any warnings in the changelog, never had any reason to suspect I needed to look elsewhere for them.

All irrelevant though. You may not like my tone, but believe it or not I am trying to help you. Can you imagine if WordPress itself suddenly released an update with a bunch of important features missing, pasted links to itself all over peoples websites, and then told them to pay up if they wanted those important features back?

Like I said, it’s your plugin, and your business, so you can do what you want. And I understand your need and desire to make money off your hard work. I support that. I am only saying you have gone about it completely the wrong way.

What you should have done is left the free plugin as it was, and found a way to add value to your paid version. Retroactively removing features is, as I said, showing contempt for your users.

Look buddy,

You can defend your actions all you want. After all, it’s your plugin, and you are under no obligation to provide it to anyone.

But it doesn’t matter what you say, you have shown nothing but contempt for the people who use your plugin. Your actions violate the spirit of WordPress, and aside from that it’s just plain bad business.

Had you acted honourably, I would have purchased your plugin. Unfortunately you did not. Therefore I will not only not purchase your plugin, but I wil actively advise against anyone purchasing your plugin. You have shown yourself to be dishonest and sneaky and pruchasing any mission critical software from you would be ill-advised indeed.

It’s dirty and underhanded. Will switch to another plugin. Will not suppport developers who use bait and switch tactics.

@marcogodles

I think you will find your answer here:
https://codex.www.ads-software.com/Author_Templates

read section on “$curauth”

Well I fixed it by moving the “is_author” if statement up the line to before “is_search” and now everything works perfectly. Obviously there was some kind of conflict.

If someone could explain what the reason for it was, I’d be curious. Otherwise, consider this one closed.

What is truly making me tear my hair out over this one, is that withing author.php I can calls to display the author name, bio, etc., and these work regardless of whether the author has posted, but I can not get this to work in the breadcrumb no matter what I try.

There MUST be an obvious and simple solution, but it’s eluding me.

BTW, to the person who deleted their reply, I don’t want to use the plugin because I am developing this site for a clients, and hate making client websites reliant on them. If down the road the plugin stops working, or the author abandons it, then I end up having to fix a client’s website, often without being paid. I don’t mind fixing my own theme framework if it breaks, but don’t want to waste time with anything else.