Enhancements
1) Ad positions now corresponds to each page - v1.0.3
Bugs fixed
1) Display User Ad % option in the ACP can now be used - v1.0.3
Would it be possible to somehow add some kind of a glaf/option setting that indicates wheter the ad displayed b elongs to a user or not?
<xen:if is="{$displayAdUser}">
<span style="float: left;font-size: 11px;height:12px;" class="muted">
Ad User: {$pub_user}
</span>
</xen:if>
<div style ="width: {$google_ad_width}px;margin: 0px auto;padding-top: 10px;padding-bottom: 2px;
<xen:if is="{$displayAdUser}">
border: 3px solid green;
</xen:if>
">
<script type="text/javascript"><!--
google_ad_client = "{$google_ad_client}";
/* {$google_ad_comment} */
google_ad_slot = "{$google_ad_slot}";
google_ad_width = {$google_ad_width};
google_ad_height = {$google_ad_height};
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</div>
Enhancements
- Different % share for different usergroups
% Share is no longer set in the options, but can be set for each usergroup in the usergroup permisions
Yes, thats a good idea and fairly easy to implement.This keeps getting better! Maybe an option to select which forums ads will/will not appear?
Yes, thats a good idea and fairly easy to implement.
Although, for those forum that are not selected as "AdShare Forums" should they
1) Show the default Ad
or
2)Show no Ads
(maybe I should have this as an option too)
I think the option for both would be great.
Enhancements
1) An option in the ACP to select which forums AdShare is Active
2) For non active forums, 2 options are available in the ACP:
i) Display no Adsense
ii) Display the default forum Adsense
I would love it the users could only enter their adsense publisher ID, instead of all the code.
This way admin could choose the code for which Ad Size to use and xenadshare just insert the publisherID of the user.
But the user is given a warning if they paste the wrong type of adsense code inchoose the code for which Ad Size to use
<script type="text/javascript"><!--
google_ad_client = "{InSERT_PUBLISHER_ID}";
/* 160x600, created 12/9/09 */
google_ad_width = 160;
google_ad_height = 600;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
Fixed a bug related to Ads on in posts, where the thread creator is an unregistered user
Regarding the Pub ID, I also recommend allowing the user to enter it vs the entire Adsense code. It's become standard practice across many revenue sharing sites over the last several years. I understand Google's "written" policies, but the internet changes quite rapidly, and there's something to be said for the "spirit" of a rule. In this case, we are simply expediting the process for the end user. It's possible some of my older users may get confused if they have to copy and paste Adsense code (seriously).
Some of my users are better at replying to posts versus starting new threads. Their contributions are valuable nonetheless.
Can you add a feature to also display Adsense for the user who submits the last post? If the thread spans several paginations, then the user who submits the last post for those pages respectively would get credit.
Therefore, the breakdown for ad share would be split three ways:
- Forum owner
- Thread creator
- Last post creator (respectively per page)
can be done.. will look into itRegarding ad positions. two additional spots would be helpful:
- Above Thread Messages
- Below Thread Messages
Finally, what if you added self serve ad booking, where advertisers can submit and pay for a banner or text link ad? The user who created the thread would get a portion of the ad revenue as well, which can be paid out in Paypal. All submitted ads would have to be approved before they go live. There could be a link somewhere that says, "Your ad here". Forum owners can set the ad rates to differ for each forum/subforum.
Overall, these implementations could really shake things up and add an interesting dynamic to how users behave knowing that they will be rewarded in a multitude of ways.
We use essential cookies to make this site work, and optional cookies to enhance your experience.