модель:

    public function rules()
    {
        return array(
            'email' => array(
                array('not_empty'),
                array('min_length', array(':value', 6)),
                array('max_length', array(':value', 127)),
                array('email'),
                array(array($this, 'unique'), array('email', ':value')),
            ),
            'password' => array(
                array('not_empty'),
                array('min_length', array(':value', 5)),
            ),
        );
    }
    
    public function filters()
    {
        return array(
            'email' => array(
                array('trim'),
                array('strtolower'),
            ),
            'password' => array(
                array('trim'),
                array(array(Auth::instance(), 'hash')),
            )
        );
    }
    
    public function register(array $data)
    {
        $extra = Model_User::get_password_validation($data)->rule('password', 'not_empty');
        
        $this->values(array(
            'email'    => $data['email'],
            'password' => $data['password'],
            'created'  => time(),
        ))->create($extra);
        
        $this->add('roles', ORM::factory('role', array('name' => 'login')));
        
        return $this;
    }

Вообще с паролями какой то костыль получается, зачем например правила для пароля надо указывать дважды? В методе rules() и потом еще при отдельной проверке (а нормально все равно не работает). Короче это сильно запутывает и озадачивает новичка.

Так же прошу обьяснить по поводу правил валидации, есть к примеру следующие правила в модели:

    public function rules()
    {
        return array(
            'url' => array(
                // ...
            ),
            'name' => array(
                // ...
            ),
            'description' => array(
                // ...
            ),
        );
    }

Как вы делаете если например нужно изменить только url? То есть отправляете форму в которой только поле url, валидация ведь тогда будет ругаться что не указаны name и description. Создавать для этого отдельный метод в котором снова правило для url прописывать?

I have only one route in my application which is Route::set('default', '(< controller >((/< action >)/< id >))') and then i specify the default controller and the default action.

On the development machine when i try to rewach my kohana application i type localhost/application/controller/action/id and everything is fine.

On my production machine the address is http://example.com/subsitename/otherfolder/controller/action/id substename and otherfolder are two existing directories and my application works fine only when i omit controller action and id.

someone can explain me how can i do?

Thanks in advance Marco

To start of, here's the diagram of tables:

http://dl.dropbox.com/u/1246624/members_topics_articles.jpg

Here's my ORM definitions:

MEMBERS has many TOPICS through MEMBERS_TOPICS

ARTICLES has many TOPICS though ARTICLES_TOPICS

TOPICS has many MEMBERS though MEMBERS_TOPICS

TOPICS has many ARTICLES though ARTICLES_TOPICS

Think of it as a mailing list where you have members that has chosen topics of articles in which topics are also assigned to particular topics.

I couldn't figure out how to make a single query so I can return joined results and send an email to individual members with articles they only chose through the topics they've chosen.

I hope to receive wisdom with mysql/kohana ninjas around. :D

-Arnold

APPPATH/classes/controller/contact.php [ 49 ]

44         $view = View::factory('pages/contact')
45             ->bind('validator', $validator)
46             ->bind('errors', $errors)
47             ->bind('recent_contacts', $recent_contacts);
48 
49         if (Request::$method == "POST") {
50             //added the arr::extract() method here to pull the keys that we want
51             //to stop the user from adding their own post data
52             $validator = $contact_model->validate_contact(arr::extract($_POST,array('email','subject','payload')));
53             if ($validator->check()) {
54                 //validation passed, add to the db

How should one debug this type of error? Thanks, Danté

When using the ORM to generate an array, I understand that a "foreach" method can be used to print out all the data in this array. However, is there a way to allow the array to be loaded by the primary ID?

For example, it'd be nice if I could load $table->1234 instead of being forced to do $table->0->1234

i already put this code on my application/bootstrap.php

if ($path = Kohana::find_file('vendor', 'Zend/Loader'))
{
    ini_set('include_path',
    ini_get('include_path').PATH_SEPARATOR.dirname(dirname($path)));

    require_once 'Zend/Loader/Autoloader.php';
    Zend_Loader_Autoloader::getInstance();
}

then on my model i put this just checking if it found the zend library

$mailer = new Zend_Mail;

i get an error

class Zend_Mail not found

did i do something wrong?? please help

i already put zend in my application/vendor/zend

    $path_normal = APPPATH.'/views/assets/images/photos/main/Normal';
$path_large = APPPATH.'/views/assets/images/photos/main/Normal';
$dir_normal = '/assets/images/photos/main/Normal';
$dir_large = '/assets/images/photos/main/Normal';

$normal_pix = array();
$large_pix  = array();

$normal_pix = Kohana::list_files($path_normal);
$large_pix  = Kohana::list_files($path_large);

$normal_pix = scandir($path_normal);
$large_pix  = scandir($path_large);

Thanks

Сейчас занят конструированием сайта, остановился на валидации в методе /register/.

Версия Коханы 3,2.Обшарил уже что только мог , мб кто знает что где "подкрутить".

Сам метод:

public function action_register() {   
    if (isset($_POST['register'])){
        $data = Arr::extract($_POST, array('username', 'password', 'telefon', 'fio', 'password_confirm', 'email'));
        $users = ORM::factory('user');
        try {
            $users->create_user($_POST, array(
                'username',
                'fio',
                'telefon',
                'password',
                'email',
            ));

            $role = ORM::factory('role')->where('name', '=', 'login')->find();
            $users->add('roles', $role);;
            $this->request->redirect();
        }
        catch(ORM_Validation_Exception $e)
        {
            $errors = $e->errors('auth');
        }
    }

    $auth_register = View::factory('index/auth/v_auth_register')
            ->bind('errors', $errors)
            ->bind('data', $data);
    // Вывод в шаблон
    $this->template->page_title = 'Регистрация';
    $this->template->block_center = array($auth_register);

}

public function action_logout() {

}
}

Модель:

class Model_User extends Model_Auth_User { public function labels() { return array(

        'username' => 'Логин',

        'email' => 'E-mail',

        'fio' => 'ФИО',

        'telefon' => 'Телефон',

        'password' => 'Пароль',

        'password_confirm' => 'Повторить пароль',

    );
}
public function rules()
{
    return array(
                    'username' => array(
            array('not_empty'),
            array('max_length', array(':value', 32)),
            array(array($this, 'unique'), array('username', ':value')),
        ),
                   'password' => array(
            array('not_empty'),
        ),
        'email' => array(
            array('not_empty'),
            array('email'),
            array(array($this, 'unique'), array('email', ':value')),
        ),
        'fio' => array(
            array('not_empty'),
        ),
        'telefon' => array(
            array('not_empty'),
        ),
    );
}
    }

Валидация ну стандарт и вот что дописал:

application\messages\auth\user.php

return array(
    'unique' => 'Поле ":field" уже существует',
    'no_user' => 'Неверный логин или пароль',
 ); 

В application\messages\auth\user\

Создал _external.php тут пусто.

HTML Code(блок вывода ошибок, дальше там все стандарт):

 <?if(isset($errors)):?> 
 <div id="site_errors" style="padding: 20px 10px 10px 0px;">
 <div id="site_errors_top"></div>
 <div id="site_errors_cent" align="left">
 <p>Найдены следующие ошибки:</p>
 <?foreach($errors as $error):?>
 <p style="padding-bottom:5px;"><font style="color:red;font-size:12px;"><?=$error?></font></p>
 <?endforeach?>
 <?foreach($errors['_external'] as $er):?>
 <p style="padding-bottom:5px;"><font style="color:red;font-size:12px;"><?=$er?></font></p>
 <?endforeach?>
 </div>
 <div id="site_errors_bottom"></div>
 </div>
 <?endif?>

Ну и сам результат работы выглядит примерно так:

http://s018.radikal.ru/i528/1201/bb/0bf59a0b5933.png

Проблема в выводящимся Array.

Enjoy :)

https://github.com/designofseven/kohana_less

Recent Messages:

<?php echo $message; ?>

<?php endforeach; ?> I get this error ErrorException [ Notice ]: Undefined variable: messages

APPPATH\views\profile\messages.php [ 3 ]

1 Public Profile for <?php //echo $username; ?>
2 Recent Messages:
3 <?php foreach ($messages as $message) : ?>

please move if I posted this in wrong section. thanks.

protected function redirect (Model_Comment $comment) { $r = Request::instance(); $r->redirect($r->uri); }

Please help and thanks so much

In my latest project I want to build a web frontend with a RESTful API on the backend. In my previous projects I had controllers using the models for both api actions and web actions resulting in a lot of duplicated code. I would use two separate "template" controllers for the API and web. My question, is there a smarter and cleaner way to do this with Kohana? It would be nice if all data handling goes through the API and only the API uses the models and validates the data. For all AJAX requests on the web frontend I would use the API, but how should the web controllers be structured? I would still need to have web controllers and views to support the website. Can I use HMVC for this? I was planning on using oAuth 2 to authorize when using the API. Any ideas on how to implement oAuth 2 as 2 legged auth on the web frontend?

Any ideas or pointers?

Thanks!

I'm using native sessions (I believe), and edited my session config at APPPATH/config/session.php

   return array(
     'native' => array(
       'lifetime' => 259200,
     ),
   );

It doesn't seem to be effective.

Am I missing something?

first: I've opted for a solution with just one URL, that is the mobile and the desktop version has the same URL, there isn't subdomains like m.mysite.com, or mysite.com/mobile/ or differents routes, I think this is the cleaner solution, is better for SEO, and you can share links without pain. If you have an argument against that I'll be happy to read it :)

1) Create a different View_Model for every View_Model of your desktop version, then you end with something like: View_Product and View_Mobile_Product (I think is better View_Product_Mobile but due to the autoload I will end with a lot of "mobile.php" files and inside a new folder "product", and that's not nice).
View_Mobile_Product extends from View_Product.
Then I'm using a session value for reading if it's a mobile request or not (if the session doesn't exist then I'm using the user_agent for detecting it). And passing that value to the View_Model Factory. The factory creates the right View_Model using always the name of the "desktop" view_model (I think this give us more freedom and is more secure than just concatening Mobile_ before using the View_Model factory (for example we could use a list of exlusions in our factory for using the desktop VM if they are equal and then avoid DRY, also we can change in a future the name convention of our VM_mobiles and we need to change only the factory, and finally we can't make a mistake forgetting the "Mobile_" before the factory in some part of our code).

2) taking advantage of the Cascade system of Kohana and using multipl applications. Maybe something like this:
Convert the current application code into a module (and add support for the transparent extension).
Create different applications (different folders, for example application_desktop, application_mobile).
Put only the code that is unique for every application in the application_* folders (using transparent_extension).
Set the application folder based on everything you want (mobile detection, session inside index.php.
I think this could be the best design, we don't need special names, factories, etc and we have everything separated and clean, but with a started project I'm afraid of the refactoring needed for this.

3) ???

What do you think?
How are you doing this in your projects?
Thanks !

As a follow up question: I have some (often used) partials defined in the base layout class (like a sidebar with navigation or a header). What is the correct way to extend the partials array in a few layouts that share a partial, which is a small template used by a handful of pages? For example a product list li item, or some dl list acting as meta data every now and then.

Thanks for any "this is how I do it" insights

I'm trying to implement a phpBB library into Kohana so that I can make my website communicate with a forum. However on including phpBB files to allow this I get errors about abstract methods.

Please see a full description of the issue here: http://stackoverflow.com/questions/8788298/kohana-3-2-phpbb-library-working-with-abstract-methods

I would like to know how I can get around this without modifying the phpBB files.

Cheers, Thomas.

Zombor

Geert De Deckere

Slith

Edam

mGee

Everthing works great with Firefox and Safari with my Kohana 3.2 (auth + orm) but keeps regenerating session files with IE and Chrome.

I have searched over forums and tried suggestions but neither worked.

Please help.

My Auth module works only for a one subdomain, where I am logging in.. For example, if I successful logged in 'kohana' domain, and then I'am going to the 'en.kohana' subdomain, I must to login one more time.

When I'am adding to bootstrap.php Cookie::$domain = ".kohana";, I can't login in my subdomains, only in domain.

Could you help me?

look the DEMO
project on github.com

I hope that module will prove useful.

Somewhere in my Kohana login() action I create a flag: Session::instance()->set( 'wysiwyg_upload_privilege', true );

Then I want to check that flag in third-party module (actually, it's TinyMCE plugin): session_name('session'); session_start(); if (!isset($_SESSION['wysiwyg_upload_privilege'])) die('Unauthorized access');

The problem is that third-party module doesn't know about Kohana and its classes. Kohana (at least it's ORM module) stores some objects in SESSION. So in session_start() I get: Warning: Class __PHP_Incomplete_Class has no unserializer

Of course, I can handle this warning or just suppress it. But thats seems to be a wrong way. What can I do with that?