Removed the word “hell” from the captcha dictionary
LOL- that one cracked us up too- but it was a good point.
LOL - First time I’ve seen that in a Change Log…*snicker* :lol:
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
April 15, 2010 6:44pm
Subscribe [15]#16 / Apr 16, 2010 4:25pm
Removed the word “hell” from the captcha dictionary
LOL- that one cracked us up too- but it was a good point.
LOL - First time I’ve seen that in a Change Log…*snicker* :lol:
#17 / Apr 16, 2010 6:45pm
We’re working on an update, keep en eye on our twitter feed for it’s release. Thanks to EllisLab for the early heads up!
#18 / Apr 19, 2010 8:33am
The performance improvements in 2.0.2 are very noticeable and extremely welcome. EE2 was feeling a little sluggish up to this point, but now it’s positively snappy. Thanks!
#19 / Apr 21, 2010 2:41pm
Glad to see the updates, but wondering why new blog posts are no longer on the front page?
#20 / Apr 23, 2010 3:55am
It’s on the block, leeaston, but we wanted to get our current changes out there.
The release post said:
If you want to use ExpressionEngine 2.0 PB for live projects (which the entire point of a Public Beta) you can upgrade a EE 1.x license for as little as $50. Our support staff and development team have set aside dedicated time to make sure the Public Beta goes as smooth as humanly possible. We’re here for you.
Just my take on it, but leaving a bug like this for 3 months and releasing updates very infrequently dosen’t really add up to smooth as humanly possible, nor does it aid using the beta on live projects. It’s especially disappointing as this feature did work and then an update broke it.
Looking forward to the next release - fingers and toes crossed for it being sooner rather than the usual pattern.
Gods speed
Lee
#21 / May 02, 2010 12:39pm
Wow, EL Team is working really hard cos again a lot of fixes come out (30.04.2010). I’m getting exited over here for some odd reason 😝 Nice…
#22 / May 07, 2010 12:01pm
I’m using a Module that was affected by the 1.6.9 changes—Navigator—and I think the original dev is no longer maintaining it. How would I go about figuring out what changed so I can attempt to bring it up to snuff?
#23 / May 07, 2010 12:08pm
I’m using a Module that was affected by the 1.6.9 changes—Navigator—and I think the original dev is no longer maintaining it. How would I go about figuring out what changed so I can attempt to bring it up to snuff?
If you’re comfortable with PHP, you can find references in the code to the site_pages array, and use the details in the version update notes for 1.6.9 as a guide as to how to alter the way it’s accessing that array.
#24 / May 07, 2010 1:24pm
Thanks for pointing that out Derek. If anyone’s interested in a 1.6.9 compatible version of Navigator, take a look here: http://github.com/wesbaker/wb.navigator.ee_addon
#25 / May 28, 2010 1:26pm
Any idea when we’re going to get a working SAEF, it’s been bust for months and months now?
Thanks
Lee
#26 / May 28, 2010 1:31pm
What do you mean “busted”, Lee?
#27 / May 28, 2010 1:35pm
HI Derek, from what I can see there a new and confirmed bug in the tracker.
#28 / May 28, 2010 1:39pm
Is there a specific bug you’re referring to, Lee? Saying that it’s been busted “for months” just doesn’t ring as accurate to me. In fact, two major changes were made in this last release.
http://expressionengine.com/public_beta/docs/changelog.html#v202pb
Fixed a bug (#12216) where PHP errors could occur after submitting the Stand Alone Entry Form.
Fixed a bug (#11244) where the Stand Alone Entry Form’s file upload was not functional.
#29 / May 28, 2010 1:47pm
Apologies for the exaggeration, I wasn’t meaning to be putting you guys down - you do great work for us. What I should have asked is, is the SAEF 100% working and bug free and if not will it be soon?
Cheers
Lee
#30 / May 28, 2010 1:52pm
Well, code will always have bugs - to think otherwise is not being realistic. But anything impeding functionality, major bugs, quirks, etc. will be eradicated prior to the launch of 2.1. If you are experiencing bugs with the SAEF that are not already reported and being worked on in the bug tracker, please let us know.