linewbie

Yep, big problem here, actually I couldn’t even update the plugin successfully due to large file size. I am disappoint ??

You have to check the source code, if the ad code is there (which appears to me it is), then there’s no problem with the plugin. Google controls whether or not displaying an ad to you, if you visited the same page too many times, google may decide to no longer display the ad to you, and just display a blank instead. Nothing to do with browser cache etc.. I believe it is IP based.

The page/post mixup is fixed now.

I will look into the post/page problem. The noadsense tag, sorry my instruction was wrong, it is actually two dashes instead of one, like this: <!–noadsense–> I will update the instruction.

Hello, thanks for your interest, currently I do not have such an option for additional donation. But I can try to add such function for next version.

yes, sorry about that, during development it was easier to develop using my native language. I will eventually translate everything to English, though I think I missed a few places. I will update it soon.

what is the problem you encounter? ad not displayed?

@jcbradley, take a look at the setting page, in the area of the donation, did I or did I not state what you just said clearly in plaintext? how is this “sneaky” or “forced”? You CAN choose what amount to donate, and 0 is an option. Why did you set other settings correctly to display your google ad, but miss this setting?

@flapane, I do not reply to threads anywhere else except here. As I have stated numerous times, if you set it to 0, then it’s 0. I find it funny that in the url you gave, the poster used a “test’ channel, instead of just reading the plugin source code and understand how the logic really works. Since everything on wordpress is open source, I don’t quite understand why he had to do a “test” instead of reading the code and the code will clearly tell him that setting to 0 is 0. His “test” is either setup wrong or he’s lying, since I see another person already said:

DireStraits 03-17-2011, 08:28 AM
“Well, I can honestly say, David, that I changed the PHP code for my plugin to utilise my own AdSense Publisher ID and a custom channel and, with the percentage box (in the plugin configuration panel) set to 0%, I’ve never seen any impressions or clicks show up on that channel over the last few months.

So I’m not entirely convinced there ever was anything underhand/sneaky going on with this plugin. Just be sure to put a “0” in the appropriate box within the plugin’s configuration panel, and you should be a-okay. ”

@iceq, Thanks for your kind support. Let me know what is the problem you are encountering, I’m always happy to hear about and fix problems with the plugin.

thanks fellow coder, I think ??

But please don’t give it a “1” rating, it’s the worst rating. If you like it give it a “5”

You can add a paragraph break yourself, there is a field called “code after the ad” in the settings. Just put some linebreaks there, I think that should fix it.

guitarjosh, that thread is from two years ago, and what did I lie about? Back then when the very first version of this plugin came out, I put the disclaimer directly in the code as a comment, you had to read the code to see it, and there were no option in the frontend, that’s all.

I admit it was a bad design, I assumed the wordpress plugin users were advanced enough to read/modify code, and apparently I was wrong, users didn’t like it. So in all subsequent versions I put the disclaimer and option in the frontend where everyone is able to see clearly. I’m not sure where was I “proven dishonest”? Plus, in the two year old thread you mentioned, people provided source code from the plugin to support their claim, you provided nothing, just empty accusation. Also you have just admitted you did not read the plugin source code, so how do you even know your accusation is true? I’m quite puzzled.

Again, if you are so sure, guitarjosh, I’d like to see you paste me the source code from the plugin that would substantiate your accusation. Thanks.

contact form now updated, should work properly now