Push things back on 5.5, what happened to the November release???
I know! What happened to "this summer"!!?!?!?
best wishes
Franz Maruna
CEO - concrete5.org
http://about.me/frz
best wishes
Franz Maruna
CEO - concrete5.org
http://about.me/frz
In all seriousness, at this point we've got the dashboard pages properly laid out, we're just doing some style cleanup on things like positioning save buttons etc. We're adding a few UI tweaks to make it easier to jump around in the settings per some of the feedback we've been getting from beta members.
Right now Andrew's pushing new code into a stage of concrete5.org so we can support add-ons & themes targeted for different versions of concrete5. We can't really launch 5.5 until we give 3rd party developers a chance to update their add-ons for it a bit, and we need this infrastructure to do that.
While we're updating this site we're trying to fix the punky email script that sends duplicates. After the battle this morning with some spammer wanting us to all buy fake uggs (which I now call FUGGS) we decided it was time to build in better spam protection. We've had a description of what we intended to do there on the core roadmap section since this spring when members of the community complained that we weren't being transparent enough about how they could help. It never got done, now we need it for our own site, and given the growth we're experiencing already and what I'm expecting after 5.5 - we'd be fools not to solve this problem the right way before it goes live.
I'm sure you know I want 5.5 launched every bit as much as anyone, but given the choice between doing it right or rushing it out for an abstract deadline I pulled out of thin air, I'll go for doing it right as long as at all possible. All I can tell you is we're working hard and good things come to those who wait. ;)
Right now Andrew's pushing new code into a stage of concrete5.org so we can support add-ons & themes targeted for different versions of concrete5. We can't really launch 5.5 until we give 3rd party developers a chance to update their add-ons for it a bit, and we need this infrastructure to do that.
While we're updating this site we're trying to fix the punky email script that sends duplicates. After the battle this morning with some spammer wanting us to all buy fake uggs (which I now call FUGGS) we decided it was time to build in better spam protection. We've had a description of what we intended to do there on the core roadmap section since this spring when members of the community complained that we weren't being transparent enough about how they could help. It never got done, now we need it for our own site, and given the growth we're experiencing already and what I'm expecting after 5.5 - we'd be fools not to solve this problem the right way before it goes live.
I'm sure you know I want 5.5 launched every bit as much as anyone, but given the choice between doing it right or rushing it out for an abstract deadline I pulled out of thin air, I'll go for doing it right as long as at all possible. All I can tell you is we're working hard and good things come to those who wait. ;)
See Attached
I started on antispam here:
https://github.com/12345j/concrete5/commit/704a2ada17fd8e9caf0bace4b...
and here:
https://github.com/12345j/concrete5/commit/26c860a30af869a528cd3c918...
but never got around to designing an interface. sorta lost interest. could be a good starting point tho.
https://github.com/12345j/concrete5/commit/704a2ada17fd8e9caf0bace4b...
and here:
https://github.com/12345j/concrete5/commit/26c860a30af869a528cd3c918...
but never got around to designing an interface. sorta lost interest. could be a good starting point tho.
Franz, Thanks for the update! Have an understanding of your positioning on this and appreciate your drive to get things right out of the gate. Whether an abstract deadline or whatever, sense you are impatient in wanting to deliver the goods, yet have the common sense not to deliver something that is going to result in wasted time and frustration on both ends. With that said, hoping to see it soon! Very Best, Tim
So I wrote a quick validation helper that uses the stopforumspam.com api.
The code is on my github here
https://github.com/mkly/ValidationStopForumSpamHelper...
Let me know if it's useful and I'll flesh it out a little more.
The code is on my github here
https://github.com/mkly/ValidationStopForumSpamHelper...
Let me know if it's useful and I'll flesh it out a little more.
tons of fun, especially if they reply 50 times to a monitored thread ;) (so much EMAIL)
We've been fighting off that spammer all night.. he's got a few Troll badges on different accounts.
It looks like we're gonna have to eat it and build that anti-spam layer we described in our core roadmap ourselves and get it into 5.5. Probably push everything back a bit but it's just a requirement at the scale we're growing.
<sigh>