Status: offline

RickW

Forum User
Full Member
Registered: 01/28/04
Posts: 240
I'm using the latest 1.3.9 version.

Because of the all the custom hacks I have been integrating into the code all over the place, it would take me some time to make the same changes if I do a fresh install of 1.3.10.

I do want to upgrade, but it depends on what is going to make it into the next release. Any bugs being worked on right now? Any new features being worked on that will prompt a 1.3.11 release? If so, what timeframe are we looking at?
www.antisource.com

Status: offline

Dirk

Site Admin
Admin
Registered: 01/12/02
Posts: 13073
See the posts entitled "Revised plan of action: Geeklog 1.3.11" here.

bye, Dirk

Status: offline

RickW

Forum User
Full Member
Registered: 01/28/04
Posts: 240
Thank you Dirk.

I also took the liberty of registering for the dev mailing list. Looks like interesting conversation.

There is actually a very simple solution that will solve all of your spam woes. Will I be able to submit a proposal of the solution to this mailing list?

edit: Okay I submitted my proposal to the devtalk list. Basically my idea is to pull out the spamx plugin, and use code verification instead. The only way you'll get comment spam after that is if you have a spammer taking the time to write every comment manually, but whenever I got spammed I knew it was automated.
www.antisource.com

Status: offline

Dirk

Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Quote by RickW: I also took the liberty of registering for the dev mailing list.

Wrong list, sorry. Use geeklog-devtalk, please.

Quote by RickW: There is actually a very simple solution that will solve all of your spam woes.

We have a working solution against the spam problem - it's called the SpamX plugin. That spam post mentioned on the mailing list was automatically detected and discarded.

bye, Dirk