The response to the 1.0 release has been fantastic. Digg provided some
excitement and we had a lot of new visitors to #cakephp on IRC, where there
are regularly 70+ users. So, to thank everyone for getting in some good
tickets, we have CakePHP 1.1.2.2955

This release fixes some bugs found in the 1.0 release. We also made some
changes to the coding standards in this release. The major changes were the
removal of newlines for the first bracket of a function definition and the
if/else statements, and we changed from spaces to tabs. By changing the
style we were able to reduce the overall footprint by a couple of KB.

We will continue to actively fix the bugs on the 1.0 line of code, but ask
that everyone be very diligent in how they submit the tickets. Several
tickets were marked for 2.0 because that is the default on the new ticket
form. Please, go through the form thoroughly when submitting a ticket. We
like to fix bugs, but do not like having to sift through missed categorized
tickets. If you have a feature or enhancement request those are marked for
2.0. If you are using 1.0 and have a problem mark those for 1.0, but be sure
to try the latest nightly before submitting a ticket. If you need some help
from the docs team you can submit tickets for the 1.0 Manual.

Thanks to everyone who is using CakePHP. We have a one of the best
communities around, which continues to make CakePHP the best rapid
development framework for PHP.

If you are so compelled, please think about contributing to the cause at
http://cakefoundation.org/pages/contribute

1.1.2.2955:
Download: http://cakeforge.org/frs/?group_id=23&release_id=96
Change log: http://cakeforge.org/frs/shownotes.php?release_id=96

Complete list of closed tickets: https://trac.cakephp.org/milestone/1.0.0.x
Complete list of change sets since last release:
https://trac.cakephp.org/timeline?from=05%2F26%2F06&daysback=23&chang...

Happy Baking.
Cake Software Foundation, Inc.

--
/**
* @author Larry E. Masters
* @var string $userName
* @param string $realName
* @returns string aka PhpNut
* @access  public
*/

Hey y'all,

Just wanted to make a follow-up comment about something that happened
this release.  Actually, it's more of a confession: We did it again.
We started adding new features.

One thing people kept asking about was how to update multiple page
elements in a single Ajax request, and up till now, we had no way of
doing that.  Not only that, but doing Ajax updates now takes less view
code, thanks to AjaxHelper::div( ) and AjaxHelper::divEnd( ).  Take a
look:

// test.thtml
<code>
<?=$ajax->link('Update 2 Div\'s', '/controller/test', array('update' =>
array('first', 'second'))); ?>

<?=$ajax->div('first'); ?>
        This is the first div, it has the current time:
        <?=strtotime('now'); ?>
<?=$ajax->divEnd('first'); ?>

<?=$ajax->div('second'); ?>
        This is the second div, it shows server variables:
        <? pr($_SERVER); ?>
<?=$ajax->divEnd('second'); ?>
</code>

One thing in this release is: all of Your helpers has to extend class
'Helper' (or some child of it), or You will fight error messages like:

Fatal error: Call to undefined method TestHelper::afterRender() in
/..../cake/libs/view/view.php on line 586

Nate, how do you set up the returned information from the ajax->link to fill
the two divs?

On 5/26/06, nate <nate.ab...@gmail.com> wrote:

100rk, that's impossible unless you upgraded wrong.  The afterRender( )
method is defined in the Helper base class, so as long as your helper
extends it properly, you should have no errors.

@Sam:

Mostly just clever output buffering to capture the content between the
div tags.  I implemented a new callback in Helper, which AjaxHelper
uses to write out the content, and then exit.  It packages it as a JSON
object, with an extra little snippet of code that gets evaluated on the
client side.  It iterates thru the elements in the object, and assigns
the content to the proper div element.

Thanks nate, but this wasn't my problem - it was issue of 2 people on
IRC today - they has helpers which aren't extend Helper class and after
upgrade to latest release they ends with above errr message.

Nate
have you the controller's method going with this ? I'm probably thinking
too quickly but I don't
get how this method will return 2 things at once.

Great work as always :)

Keep up the awesome work!

Marcelo.

On 5/26/06, Olivier percebois-Garve <perceb...@gmail.com> wrote:

Great stuff Nate, and all of the Cake team!

Helpers:
Some of the helpers defined on the wiki (such as
http://wiki.cakephp.org/docs:helpers:custom:pagination) don't extend
anything and therefore suffer from this problem. Well they will when
you read this message but that's the magic of community spirit ;).

Cheers,

AD7six

@AD7six: Thanks for keeping that up-to-date.  Hopefully that'll be less
of a problem when we have the Bakery set up, with a proper peer-review
system.

And thanks for all the time you've put in answering questions on the
list.  That helps out a lot.

Olivier,

A new release has been announced, download it and the problem should be
gone.

--
/**
* @author Larry E. Masters
* @var string $userName
* @param string $realName
* @returns string aka PhpNut
* @access  public
*/

On 5/26/06, Olivier percebois-Garve <perceb...@gmail.com> wrote:

@Olivier: The controller method is empty (so I didn't bother posting
it).  I the view just outputs some dummy data as a proof of concept.

It's the least I can do; I would prefer to see new features earlier by
taking some of the load of you chaps ;). And I learn from reading the
q's that are out of my current scope ( I cached some of my views for
the first time today).

Cheers,

AD7six
Off topic, chipped in for comment:
There are some snippets which also use orphan helpers and a number
which seem to be either obsolete (integrated or duplicated in Cake now)
or need enhancing to be useful. The drawback of an active community
seems to be policing their efforts :)

Here, just to save people from the trouble of digging, it what a
response looks like (spacing added):

<script type="text/javascript">
var __ajaxUpdater__ = {

first:"%09This%20is%20the%20first%20div%2C%20it%20has%20the%20current%20tim e%3A%0A%091148669377"

for (n in __ajaxUpdater__) {
    if (typeof __ajaxUpdater__[n] == "string" && $(n))
        Element.update($(n), unescape(__ajaxUpdater__[n]));
</script>

Thanks Nut but for once I did not had any problem. Just wondering how
Nate's snippet should be functioning.

Larry E. Masters aka PhpNut wrote:

I try to update my cake from 0.10.8.2047_rc5 to 1.1.3.2967,
Then I found I can't use $controllername->modelname->findAll,
What can I do ?

Hi leinchu,

Why you can´t use? You are being too vague... please, tell us more about
your problem, don´t just say "I can´t get this working..."

Marcelo.

On 5/27/06, lein...@hotmail.com <lein...@hotmail.com> wrote:

Hi Marcelo de Moraes Serpa :
Thanks first.
I have resolved it.
I used cake (version 0.10...),when found there was a new cake
version,so I decided to update my cake,but I found such codes in
controller would not work in the new version 1.1:
$userdata=$this->users->read();

I have to  use :
$userdata=$this->Users->read();
instead;
--------------------------------------------------------------------------- ---------------------------------------------------
That means the first letter of model's name must be a uppercase when
you try to execute a model funciotn(such as find,findall or read) in
controller with cake 1.1.
--------------------------------------------------------------------------- ---------------------------------------------------