Membership?

23rd Jul 2006 stk

OKAY ... plugins are starting to circle the airport, looking for a landing on a non-existent runway. What's the best way to handle these? I'd like to bring them out as soon as possible, but don't really think we should, until we have membership in place. I don't want to just concentrate on the "free" ones, because then folks'll only grab those.

We need a method for signing up members.

I think the pay-per-plugin thing can wait. Let's get membership rolling and then we can finish the fluff and start rolling some of these plugins down the runway.

We also need to identify which plugins are going to be free, either because they just make b2evo work "right" or because they incorporate/use GPL code. And for those that are original ... like "display code" and "search highlight", how much should we charge on a one-off basis?

MEMBERSHIP

 
 
 
 

Comments

Anonymous
23rd Jul 2006
ffs - you really did wake up in a grumpy mood huh?

Agreed that we need to get membership up and running as soon as possible. I'll put the hound on hold and see if we can get it sorted this week..... of course, that'll mean that you'll have to pull your finger out and start fluffing all the (huge queue of) plugins we currently have stalled on the starting blocks, but that's your sweat not mine so I can live with that :D

I know we've chatted about this but I suppose it's time to put it in text. If a plugin is "correctional" then I think it should be free (after all, we want everybody to enjoy their evo blog). If a plugin is exceptional then it should be members only (paid/unpaid, however we finally decide [with a pay per plugin if we go for paid membership]), but I'm buggered if I can put a price tag on things cos to me they're all "easy enough to replicate" ..... mind you I am a shit hot programmer :| (say "you are" or I'll shoot you :|).

anyway, I'm meant to be the beauty, yer meant to be the brains (business wise), so make a decision and I'll say "damn mate, great decision" ...... with the same conviction as you say "damn mate, great coding" :|

¥
 
Anonymous
25th Jul 2006
"you are" ;)

(a shit) :P

and no wonder we're floundering ... yer the beauty? :o ffs :|

DAMN MATE ... GREAT CODING!! ;)

Speaking of which ... why aren't the google-spell controls showing up in the post? (I turned JS support "on" in AM_custom_CSS and fixed yer first GoogieSpell function variable ... you had "http://b2evo.astonishme.co.uk//plugins" ... which seemed a tad odd).

Still no go tho (answrd the guys questions as best I could). I haven't tried google-spell in our own v1.8 blog yet.

Cripe ... too much to do and tomorrow is definitely FENCE building day. (We're flying to Vancouver Island on Saturday too, to look for a place to live, so will be out of pocket from Sat thru Thurs).

I DID say this was a crap time for b2evo v1.8 to ship. :p

Did you see my "error" report on the forums? Any idea what's causeing the redirect to send a visitor, after a comment, to comment_post.php? :o

Hopefully ... you'll see the AM-allow-comments plugin on the published side of the fence. ;)



 
Anonymous
25th Jul 2006
Well, stop the presses, because am_allow_comments doesn't work.

Downloaded the zip, installed, exited to blog, left comment (logged in), "moderate".

:(

Checked plugin setting and verified "enabled" for "authors" and "members" ... karma == -100.

:o

What gives?
 
Anonymous
25th Jul 2006
Google Spell ... I get the same problem as that other guy. Download ZIP, upload, install ... no controls. :(

Is the download file still only a CVS v1.8, rather than a v1.8 "summer beta"?

I'm not too astonished :p

( And gee ... I came here to fluff :o )
 
Anonymous
25th Jul 2006
ok, here we go
  1. allow comments
    There seems to be some form of bug (either evo or php5, not sure which and I only have your server to test with). For some reason the "weight" of the plugin (not the karma) gets returned as NULL so it never gets called for a spam karma value.
    The weirder thing is, if you install the basic antispam plugin then the "weight" gets returned correctly and the so it gets asked for a karma value.... go figure.
    Fortunately I'd already decided to change the functionality of the plugin as it didn't quite do what it said on the tin. It now sets the karma value to NULL (no spam karma) for authors/members and sets the status to 'published' irrelevant of any spam karma the post has. The only time it won't work is if the comment collects a karma above the delete threshold.
  2. Googie
    I've updated the zip to correct the user settings bug that it had. As it happens this was only part of what causes it not to appear on your blog. I've uploaded a custom version to your blog which uses rand_gen_name() and now it works ;)
    The googiespell on the demo didn't work because of a clashing onload from another plugin. Cured ;)
  3. Error on forums
    I have seen it but I haven't had time to look into it yet
  4. DAMN MATE, GREAT DECISION ...... urm, did you make a decision? :|
¥
 
 

Recent Comments

     
     

    Archives