ehouben

@rhand No problem. I just installed pro quiz to check it myself (actualy need the solution myself and not that satisfied with mtouch lately).

Seems that it will work. Just check the “Activate graduation” box and add your achievement redeem code to the passing % text (in theory you could even make multiple achievements for a single quiz, based on the score achieved (i.e. Scored 8/10 on quiz X), although this would be quite a bit of work if you have a lot of quizes (like i do).

Of course, this solution is not optimal, as it requires an aditional step of the user (enter the redeem code they aquired). Still, at the moment I do not see another way to achieve the same result.

As a sidenote, Paul (achievement author) says he is looking into integration for one quiz plugin (but he has not yet decided which one).

Not sure if this will work for pro quiz. Mtouch quiz allows a custom end screen for each quiz when passed (does pro quiz do this?) If so, why not use the redeem function in achievements 3.2? That way every achievement is linked to a specific quiz.

1. In the achievements plugin options create a new achievement. Choose a redeem code on the right side of the screen.

2. Now create a new quiz in mtouch. When presented with the after quiz screen options, alter it to say something like; congratulations, you have passed. Redeem your achievement with the following code; *yourcode*

No technical knowledge needed.

For mtouch you can specify the text a user sees when they pass the test. If you include a redeem code for achievement you have a working solution until Paul integrates it. For reading posts i use three control questions using the quiz..otherwise students could just click trough pages without actualy reading them. Hope this helps.

No problem at all, I shouldn’t have left my reply open for negative interpretation. I cannot think of any other functions i really miss. The group-specific achievements were a core requirement for my project, because i am designing it for an educational purpose (so i needed to reward based on engaging in specific subjects (groups), instead of engaging on the site in general). That’s why i sorely missed them come 3.0 ??

Digs? I fear you misunderstood. I’ve been a big fan of your plugin for a long time. The main reason for this was the group specific achievements. When 3.0 released i was disappointed to see the option was gone, but saw the overall improvement to the plugin. From that perspective, I’m truly looking forward to the day that the (now superior) plugin will once again have the function that drew me to it in the first place.

I’m sorry if my reply implied anything else, although I do hope that you understand that for older users, 3.2 does not offer the FULL buddypress integration they had gotten used to.

Well, thanks for clearing that up. Back to 2.4 we go. Will be looking forward to the day that the 3.X versions truly offer the full buddypress integration of it’s predecessor.

@martin: As far as i know it should function fine without buddypress after the 3.0 update (or rather rebuild)

Thanks for the quick response. That solved the issue with activation of 3.2. I was hoping that the improved buddypress options would include the group-specific achievements (for me this is the core function i need). Are you still planning to implement this again?

Hi there, sorry for the late reply. I have just updated to 3.2 and tried out the new option. It is not working for me, most likely because i’m reloading the iframe from within the iframed page. Not a big deal realy, i’m sure it works great on first load (which i think most people will use it for).

Ok, just let me know when the new version is uploaded and i will test it.

Yes, I do have this ‘problem’. It’s not realy a big problem, since it’s rather logical that a not-yet-loaded page is white. However, it would look a lot better if the page color was used.

If you are using your demo-page as the test page i think you will not see the problem (unless i’m mistaken your background colour is white). My pages use a dark background (2e2e2e) so the contrast is rather sharp.

I also read a few posts that mentioned the problem occurs in specific browsers (i can confirm chrome)

Banner is looking great. Hope it draws in some more traffic for you. I was thinking that you could (perhaps) include a small bit of text (or even a call-to-action button) in the plugin admin screen. Something like;

If you like this plugin, please consider leaving a review. It will only take a minute and mean a great deal.

(I know, making the user feel important is a marketing trick. But if it works, why not?)

I respect your choice to keep your plugin free by going down the paid support route. Hope it works out for you. I’ll keep an eye out for the new-version notice.

Whoaaa, someone jumped in quickly ?? But yes, i did mean CodeCanyon.

1. Conversion is low because most people simply do not want to pay if they do not have to. Those that do want to send you some money don’t want it to be troublesome (most people don’t have paypal accounts, and will not make one just for a donation).

Let’s say you sold your plugin (say at Envato), and the downloads would have been 1/10th of what they are now (because it’s paid). You would have sold 3000 copies. Now let’s say you ask a reasonable price (say $10). You would have made $30.000 or around 13.000 euro’s

Point being, your plugin does something none of the other free plugins do (and you are willing to support it). People will pay a small amount to get the needed functions, if they do not have a choice.

2. Your repository text seems to assume some pre-knowledge, and lacks a clear sales-pitch. Instead of listing all functions, you could try to determine what functions set you appart from the crowd (for me, that would be the ability to do things with buddypress that it cannot do by iteself. For others it might be the ability to hide certain divs. etc.)

When you have a clear view of those unique sales-points, you exploit them through clear writing. Instead of just listing them, elobarate a bit…not on the technical details, but on how the plugin will empower the user (e.g. YOU decide what to show, and what to hide). Lame example, but i hope you see where i’m going with this.

I understand your point of view. Please allow me comment on it to some extend;

1. Donations on free plugins have always been a troubling issue. It has caused the end of some great projects. A huge discussion on this point erupted when the author of buddypress privacy component quit his project for this very reason.

I truly believe this has to do with human nature. If something is offered free, you take it and don’t look back. I don’t think many people (with the exeption of branche collegues) appreciate the work a developer puts into the product. With wordpress plugins this is even more of an issue because the main platform is free itself.

If money is an issue for you, i don’t think you have many options other then changing AI into a paid plugin.

2. Votes follow the same reasoning. They don’t cost the user anything, but why would they come back to the repository page if the plugin was installed succesfuly, and is working for them? Perhaps a small notice (plea) in the plugin admin screen could help this out a bit, but again…most people are a bit selfish.

3. The first two points were rather general. To go into the “marketing” of your specific plugin, I believe your repository page (and to some extend the plugins backend) is rather daunting to the avarage wordpress user (who knows little to nothing about code and less about iframes). Just because your plugin is free doesn’t mean it cannot benefit from a bit of sales text. A list of functions most visitors don’t understand may not do the trick, and might even scare some away.

To illustrate this, if i type the following into google; ‘advanced if’

Autofill gives me these suggestions;

1. Advanced Iframe
2. …..(not relevant here)
3. Advanced Iframe tutorial

Well, just my two cents. Please understand that i only offered them because i sincerely hope that they will help, and that your plugin (which i love) will become as succesful as you want it to be.

My offer to test 3.2 can be considered an open offer. When/If you ever decide to build it, i will test it if you want me to.