propel-load-data fails with sandbox

[Matthias Nothhaft]

Hi,

I'm currently trying to get the CMS work. :-)

"symfony propel-build-all" works fine. But "symfony propel-load-data"
throws this exception:

[PropelException]
[wrapped: Unable to load driver class: p [User Info: Array]]


Any ideas? Below is the full output I get.

Regards,
Matthias


$ ./symfony propel-load-data backend
>> propel load data from "...ns/sfGuardPlugin/data/fixtures"
>> propel load data from "...eerCMSBlogPlugin/data/fixtures"
PHP Warning: session_start(): Cannot send session cookie - headers
already sent by (output started at ...steer/lib/symfony/vendor/pake/
pakeFunction.php:366) in ...steer/lib/symfony/storage/
sfSessionStorage.class.php on line 77

Warning: session_start(): Cannot send session cookie - headers already
sent by (output started at ...steer/lib/symfony/vendor/pake/
pakeFunction.php:366) in ...steer/lib/symfony/storage/
sfSessionStorage.class.php on line 77
PHP Warning: session_start(): Cannot send session cache limiter -
headers already sent (output started at ...steer/lib/symfony/vendor/
pake/pakeFunction.php:366) in ...steer/lib/symfony/storage/
sfSessionStorage.class.php on line 77

Warning: session_start(): Cannot send session cache limiter - headers
already sent (output started at ...steer/lib/symfony/vendor/pake/
pakeFunction.php:366) in ...steer/lib/symfony/storage/
sfSessionStorage.class.php on line 77
PHP Warning: Creole::include_once(p.php): failed to open stream: No
such file or directory in ...steer/lib/symfony/vendor/creole/
Creole.php on line 366

Warning: Creole::include_once(p.php): failed to open stream: No such
file or directory in ...steer/lib/symfony/vendor/creole/Creole.php on
line 366
PHP Warning: Creole::include_once(): Failed opening 'p.php' for
inclusion (include_path='...') in ...steer/lib/symfony/vendor/creole/
Creole.php on line 366

Warning: Creole::include_once(): Failed opening 'p.php' for inclusion
(include_path='...') in ...steer/lib/symfony/vendor/creole/Creole.php
on line 366


[PropelException]
[wrapped: Unable to load driver class: p [User Info: Array]]

[Matthias Nothhaft]

Data is inserted into the database. But I think these errors should
not happen. :-)
After clicking a bit around it seems like there is a lot work to
do. :-)

Regards,
Matthias


On 15 Jan., 16:59, Matthias Nothhaft

[Konny Zurcher]

Hi Matthias,

These errors are under investigation now. They are warnings only but still annoying though.

This version of Steer CMS is still an early alpha version and we are working on all the open issues now.

Cheers,

Konny Zurcher
Steer CMS - Development Team

[pi...@wranglers.com.au]

Hi Matthias,

>> After clicking a bit around it seems like there is a lot work to do

Absolutely, we plan on no sleep for a while :)

- Piers

[Francois Baligant]

Remove this file: plugins/sfPropelVersionableBehaviorPlugin/config/
schema.xml

This will fix your include error with Creole during "symfony propel-
build-all-load backend"

Best regards,
Francois

On Jan 15, 4:59 pm, Matthias Nothhaft

[konny.zurcher]

Hi Francois,

Thanks for answering that one.

Cheers,

Konny Zurcher
Steer CMS - Development Team

On Jan 19, 10:39 am, Francois Baligant <francois.balig...@gmail.com>
wrote:

[pomidor]

I have the same problem.
I removes the file, that you said, but it didn't fix the problem
Could you advice, anything else?

On Jan 19, 1:39 am, Francois Baligant <francois.balig...@gmail.com>
wrote:

[konny.zurcher]

Hi Pomidor,

I assume you refer to that error ...

[PropelException]
[wrapped: Unable to load driver class: p [User Info: Array]]

Whatever version you download (Sandbox or SVN) you will have to edit
the following files:

{path_where_steerCMS_installed}/config/databases.yml
{path_where_steerCMS_installed}/config/propel.ini

There are also some other slight installation differences between the
sandbox version and the SVN version. Read here: http://www.steercms-project.org/installation

There you will have to set the database connection. From your mail, I
do not know if you use MySQL or SQLite or some other database. The
error above is due to a configuration mistake of the (dsn) entry. Then
the driver path can not be found.

For SQLite: http://trac.symfony-project.com/wiki/HowToUseSqLite

For MySQL use:

[config/database.yml]
all:
propel:
class: sfPropelDatabase
param: mysql://{mysql_username}:{mysql_password}@{hostname/{mysql_database_name}

[config/propel.ini]
propel.targetPackage = lib.model
propel.packageObjectModel = true
propel.project = {Projectname} <= needs adjusting to your
CMS Project name
propel.database = mysql
propel.database.createUrl = mysql://{mysql_username}:{mysql_password}@{hostname}/
<= in a default web-server configuration hostname = localhost
propel.database.url = mysql://{mysql_username}:{mysql_password}@{hostname/{mysql_database_name}

If you use any other database type .... check the Symfony
documentation for connection details here: http://www.symfony-project.org/doc/1_0/

Also an important point is that before executing:

>> symfony propel-build-all-load backend

or

>> symfony propel-load-data backend

do a

>> symfony cc

to cleat the cache. A problem could also be that in most cases the
database itself should be created by propel when doing the "symfony
propel-build-all-load backend" but we had some cases (in CentOS and
Mac OS x 10.4) that the database needed to be created manually before
using the propel commands.

To the session and cookie warnings ...

Problem when using:

>> symfony propel-load-data backend

or

>> symfony propel-build-all-load backend

To get rid of these warnings the following parameters will have to be
adjusted in your php.ini file.

For this warning: Warning: session_start(): Cannot send session cookie
- headers already sent by (output started at {path}) in {path}/
sfSessionStorage.class.php on line 77

Change: session.use_cookies = 0 <== when set to 1 problem occurs

For this warning: Warning: session_start(): Cannot send session cache
limiter - headers already sent (output started at /{path}) in {path}/
sfSessionStorage.class.php on line 77

Set parameter session.cache_limiter to:

session.cache_limiter =

The solution for changes in php.ini is not that nice. I am checking
out now if these values can be overwritten by php so I can prevent
users for making changes to that file which could effect other
projects users are running. We are working on a solution for that. For
now, there is no error just the warnings so watch out which session
parameters you change because they can affect the user login on
frontend and backend too.

Let me know if any of this helped.

Cheers,

Konny Zurcher
Steer CMS - Development Team

[pomidor]

Hello Konny Zurcher .
Big thank's for such a detailed answer.
I would have to inform that i use PEAR installation of symfony 1.0.9,
i changed symfony directories in config/config.php

I had this warnings:

For this warning: Warning: session_start(): Cannot send session cookie
- headers already sent by (output started at {path}) in {path}/
sfSessionStorage.class.php on line 77

i changed session.use_cookies = 0
and warnings disappear, but
know when i execute
>>symfony propel-build-all

i see that 88 of 90 SQL statements executed successfully

>>>>
propel > insert-sql:
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.steerCMSSearchPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.steerCMSPropertiesBehaviorPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.steerCMSProjectPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.steerCMSFoundationPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.steerCMSCommentPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.steerCMSCalendarPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.steerCMSBlogPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.sfPropelActAsTaggableBehaviorPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.sfErrorLoggerPlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.sfPropelVersionableBehaviorPlugin.lib.model.schema.sql
[propel-sql-exec] File 'C:\Apache\htdocs\steercms\data\sql
\lib.model.schema.sql'
in sqldbmap does not exist, so skipping it.
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.steerCMSCorePlugin.lib.model.schema.sql
[propel-sql-exec] Executing statements in file: C:\Apache\htdocs
\steercms\data\s
ql\plugins.sfGuardPlugin.lib.model.schema.sql
[propel-sql-exec] Our new url -> mysql://root:zaq123@localhost/steerCMS
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSSearchPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSPropertiesBehaviorPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSProjectPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSFoundationPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSCommentPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSCalendarPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSBlogPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.sfP
ropelActAsTaggableBehaviorPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.sfE
rrorLoggerPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.sfP
ropelVersionableBehaviorPlugin.lib.model.schema.sql
[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSCorePlugin.lib.model.schema.sql
[propel-sql-exec] Failed to execute:
>>>>

then i execute
>> symfony propel-load-data backend

it executes only

>> propel load data from "C:\Apache\htdoc...ns\sfGuardPlugin\data\fixtures"
>> propel load data from "C:\Apache\htdoc...eerCMSBlogPlugin\data\fixtures"
>> propel load data from "C:\Apache\htdoc...MSCalendarPlugin\data\fixtures"
>> propel load data from "C:\Apache\htdoc...FoundationPlugin\data\fixtures"

and stops haven't finished the execution

could you advice something about this

[Konny Zurcher]

Hi Pomidor,

The problem is that with the session parameters in the php.ini that
if you set the they are used for everything in php from then on,
except you overwrite them.

That means that if they are changed they all they affect also the
Login which uses sessions and cookies. I will have to look into that
a bit more. Will keep the user group posted about changes.

So if it runs through (despite the warnings) with the original
session settings in the php.ini, leave it as it is until we solved
that issued.

If you leave the session parameters as they were originally and
change the databases.yml and propel.ini with the correct database
connection, does it build the model and database structure properly?

Cheers,

Konny Zurcher
Steer CMS - Development Team

>>>>> PHP Warning: Creole::include_once(): Failed opening 'p.php' for
>>>>> inclusion (include_path='...') in ...steer/lib/symfony/vendor/
>>>>> creole/
>>>>> Creole.php on line 366
>>
>>>>> Warning: Creole::include_once(): Failed opening 'p.php' for
>>>>> inclusion

>>>>> (include_path='...') in ...steer/lib/symfony/vendor/creole/
>>>>> Creole.php
>>>>> on line 366
>>

[pomidor]

Hi, Konny Zurcher.

My settings concerning database connection are OK.
but it falls to execute

[propel-sql-exec] Executing file: C:\Apache\htdocs\steercms\data\sql
\plugins.ste
erCMSCorePlugin.lib.model.schema.sql
[propel-sql-exec] Failed to execute:

and there is a problem that it doesn't load all fixtures
i get errors in the public (listed below) and i couldn't enter into
admin area

>>
[PropelException]
[wrapped: Could not execute query [Native Error: Table
'steercms.steercms_core_node_public' doesn't exist] [User Info: SELECT
steercms_core_node_public.ID, steercms_core_node_public.NODE_ID,
steercms_core_node_public.NODE_TYPE,
steercms_core_node_public.MIMETYPE, steercms_core_node_public.SLUG,
steercms_core_node_public.UUID, steercms_core_node_public.VERSION,
steercms_core_node_public.IS_EXPORTED,
steercms_core_node_public.IS_IN_NAVIGATION,
steercms_core_node_public.NAVIGATION_POSITION,
steercms_core_node_public.IS_LOCKED_BY_SYSTEM,
steercms_core_node_public.IS_LOCKED_BY_USER,
steercms_core_node_public.LOCKED_BY_DETAILS,
steercms_core_node_public.TEMPLATE, steercms_core_node_public.STATUS,
steercms_core_node_public.PUBLISHED_FROM,
steercms_core_node_public.POSITION_LEFT,
steercms_core_node_public.POSITION_RIGHT,
steercms_core_node_public.POSITION_PARENT,
steercms_core_node_public.POSITION_BRANCH_ID,
steercms_core_node_public.SLUG_TRAIL,
steercms_core_node_public.CREATED_AT,
steercms_core_node_public.CREATED_DETAILS,
steercms_core_node_public.UPDATED_AT,
steercms_core_node_public.UPDATED_DETAILS FROM
steercms_core_node_public WHERE
steercms_core_node_public.SLUG='index.html' AND
steercms_core_node_public.POSITION_PARENT=1 LIMIT 1]]
>>

changes in php.ini didn't helped

> ...
>
> read more »

[Konny Zurcher]

Hi Pomidor,

This looks to me as a permission problem of the database user.

Check the permissions of the database user you specified in the databases.yml and propel.ini. This user needs write permissions for the database you provided, otherwise the predefined Steer CMS content can not be written into data tables of the database.

A thing also to check is that if that there is no "no database found" error while doing the symfony 

> propel-build-all-load backend

that's because on some systems the database needs to be created before the execution of that command. The command should basically create the database, but there were some cases where it did not.

Another thing to check is also in the {path_where_steer_installed}/config/config.php that the path to symfony and data/symfony are correct:

$sf_symfony_lib_dir  = '{path_where_symfony_installed}/lib/symfony';

$sf_symfony_data_dir = '{path_where_symfony_installed}/data/symfony';

if you do not know your directory, you can try this:

$sf_symfony_lib_dir  = dirname(__FILE__).'/../lib/symfony';

$sf_symfony_data_dir = dirname(__FILE__).'/../data/symfony';

This variables define, where the symfony libraries are found and these are used through the whole symfony and CMS projects ... 

Another point to check if you have used the tagged SVN version of the trunk SVN version:

Check {path_where_steer_installed}/config/propel.in on the following line:

propel.output.dir              = {path_where_steer_installed}        => in your case something like C:\Apache\htdocs\steercm but check

Some general issues with symfony on windows platforms can also be found here under the Installing Symfony => Windows subject:

http://trac.symfony-project.com/wiki/

If still problems then let me know about the following:

1 ) Method of install

        - Archive (Sandbox)

        - SVN (Tagged release or trunk)

2 ) Version of Symfony

3 ) Operating System

        - Windows: 2000, XP, Vista

3 ) PHP, MySQL, Apache versions (all of this should be available if check phpinfo())

4) Database connection type if not MySQL

5 ) Has the patch sfPropelVersionableBehaviorPlugin.patch been installed?

So I could try to reproduce the problems on a windows installation.

Cheers,

Konny Zurcher

Steer CMS - Development Team

[pomidor]

Hi Konny

i use the root database user, so i have no problems with permisions

after
>symfony propel-build-all
i have 88 of 90 sql queries successfully executed

after
>symfony propel-load-data backend
i see that only part of fixtures are seccussfully executed and only
part of data loaded into database

1 ) Method of install
- Archive (Sandbox)

2 ) Version of Symfony 1.0.9

3 ) Operating System
- Windows XP

4 ) PHP 5.2.4, MySQL 5.0.41, Apache 2.2.6

5) Database MySQL

5 ) i tried to install patch sfPropelVersionableBehaviorPlugin.patch
but i couldn't
How to install this patch using windows cmd?
it replyes that it doesn't understand comand

>patch

On Jan 30, 12:16 am, Konny Zurcher <ko...@wranglers.com.au> wrote:
> Hi Pomidor,
>

> ...
>
> read more »

[Konny Zurcher]

Hi Pomidor;

Thanks for all the details. I will have to look a bit more into that as for most of the testing so far was done on Mac, Unix and Linux systems.

Will come back to you about a solution for that soon.

And for the patching of sfPropelVersionableBehaviorPlugin. Sorry for the misunderstanding. The patching only needs to be done if you use the tagged SVN version or the trunk SVN version. The necessary changes for the patching are already included in the Sandbox version.

For windows. Do you use and admin user there to? Because the system needs write access to some of the steercms folders. The folders are:

{path_where_symfony_isntalled}/config

{path_where_symfony_isntalled}/cache

{path_where_symfony_isntalled}/data

{path_where_symfony_isntalled}/log

{path_where_symfony_isntalled}/web

Because after doing a propel-build-all-load backend you should get some more files here. Some examples:

{path_where_symfony_isntalled}/config

    generated-sfErrorLoggerPlugin-schema-transformed.xml

    generated-sfGuardPlugin-schema-transformed.xml

    (13 generated- files in all)

{path_where_symfony_isntalled}/data/sql

    plugins.sfErrorLoggerPlugin.lib.model.schema.sql

    plugins.sfGuardPlugin.lib.model.schema.sql 

    (12 plugins. files in all)

    sqldb.map

Eventually worth checking too.

Is it possible for you to send the output you get when doing a symfony propel-build-all-load backend?

It should be easy to do with something like this in DOS:

symfony propel-build-all-load backend > {path_where_to_save}\propel_output.txt

That should write the output into the propel_output.txt file.

Cheers,

Konny Zurcher

Steer CMS - Development Team

[yury maksimenko]

Hi, Konny

here is my output after calling >symfony propel-build-all-load backend

propel_output_0.txt with php.ini: session.use_cookies = 0
propel_output_1.txt with php.ini: session.use_cookies = 1

[Konny Zurcher]

Hi Yury,

The standard values in the php.ini are:

session.use_cookies = 1

session.cache_limiter = nocache

If you change them to:

session.use_cookies = 0

session.cache_limiter = 

you get rid of the warning messages but the login will not work anymore. So leave the standard values and overlook the warnings for the moment until we find a fix for that. The warnings do not affect the functionality at all.

As for the SQL problem. I found a solution for that one ...

Before I add it to the Sandbox could you please replace the following file in your sandbox directory (in your case C:\Apache\htdocs\steercms\plugins\steerCMSCorePlugin\config\schema.yml ) with the file attached then do again a:

$ symfony propel-build-all-load backend

and let me know if it runs through smoothly?

[pomidor]

Hi, Konny

after replacing schema.yml everithing is OK
big thank's for help
now let's try to use steerCMS )

> 

> > Cheers,
>
> > Konny Zurcher
> > Steer CMS - Development Team
>

> >>> Cheers,
>
> >>> Konny Zurcher
> >>> Steer CMS - Development Team
>

> >>>>> Cheers,
>
> >>>>> Konny Zurcher
> >>>>> Steer CMS - Development Team
>

> >>>>> On 27/01/2008, at 7:37 AM, pomidor wrote:
>
> >>>>>> Hello Konny Zurcher .
> >>>>>> Big thank's for such a detailed answer.
> >>>>>> I would have to inform that i use PEAR installation of symfony
> >>>>>> 1.0.9,
> >>>>>> i changed symfony directories in config/config.php
>
> >>>>>> I had this warnings:
>
> >>>>>> For this warning: Warning: session_start(): Cannot send session
> >>>>>> cookie
> >>>>>> - headers already sent by (output started at {path}) in {path}/
> >>>>>> sfSessionStorage.class.php on line 77
>
> >>>>>> i changed session.use_cookies = 0
> >>>>>> and warnings disappear, but
> >>>>>> know when
>

> ...
>
> read more »

[Быкадоров Дмитрий]

How about this error?

"Warning: Creole::include_once(p.php): failed to open stream: No such

file or directory in Z:\home\steercms\lib\symfony\vendor\creole
\Creole.php on lin
e 366"

I see no ways to solve it in this tread (my environment: steercms
sandbox and symfony 1.0.11)

> ...
>
> продолжение »- Скрыть цитируемый текст -
>
> - Показать цитируемый текст -

[Быкадоров Дмитрий]

upd.

i think that such error (in apache log: [Sat Mar 15 23:37:28 2008]
[error] [wrapped: Unable to load driver class: p]) appears now in
content management. This is bug or my "curve hands"?


On 15 мар, 22:01, Быкадоров Дмитрий <Dmitry.Bykado...@gmail.com>
wrote:

[Marek]

Same problem here. Creole tries to load class p. The error also shows
up when I try to add any content. Sandbox installation.

sfErrorLogViewer shows:

Type:
500
Message:

[wrapped: Unable to load driver class: p]

Class name:
PropelException
Module name:
steerCMSBlogInstance
Action name:
edit
Created at:
16/04/2008 05:16:47

Request:
URI http://steercms.local/cms/steerCMSBlogInstance/edit
Referer http://steercms.local/cms/steerCMSBlogInstance/create
Method POST
Parameters
module steerCMSBlogInstance
action edit
save Save
id
steer_cms_blog_instance Array


Traces:

# at ()
in SF_ROOT_DIR/lib/symfony/vendor/propel/Propel.php line 489 ...

486. try {
487. $con = Creole::getConnection($dsn);
488. } catch (SQLException $e) {
489. throw new PropelException($e);
490. }
491. self::$connectionMap[$name] = $con;
492. }

# at Propel::getConnection('default')
in SF_ROOT_DIR/plugins/sfPropelVersionableBehaviorPlugin/lib/model/om/
BaseResourceVersionPeer.php line 174 ...

171.
172.
173. if ($con === null) {
174. $con =
Propel::getConnection(self::DATABASE_NAME);
175. }
176.
177. if (!$criteria->getSelectColumns()) {

# at BaseResourceVersionPeer::doSelectRS(object('Criteria'), null)
in SF_ROOT_DIR/plugins/sfPropelVersionableBehaviorPlugin/lib/model/om/
BaseResourceVersionPeer.php line 161 ...

158.
159. public static function doSelect(Criteria $criteria,
$con = null)
160. {
161. return
ResourceVersionPeer::populateObjects(ResourceVersionPeer::doSelectRS($criteria,
$con));
162. }
163.
164. public static function doSelectRS(Criteria $criteria,
$con = null)

# at BaseResourceVersionPeer::doSelect(object('Criteria'), null)
in SF_ROOT_DIR/plugins/sfPropelVersionableBehaviorPlugin/lib/model/om/
BaseResourceVersionPeer.php line 152 ...

149. {
150. $critcopy = clone $criteria;
151. $critcopy->setLimit(1);
152. $objects =
ResourceVersionPeer::doSelect($critcopy, $con);
153. if ($objects) {
154. return $objects[0];
155. }

# at BaseResourceVersionPeer::doSelectOne(object('Criteria'))
in SF_ROOT_DIR/plugins/sfPropelVersionableBehaviorPlugin/lib/
sfPropelVersionableBehavior.class.php line 80 ...

77. $c = new Criteria();
78. $c->add(ResourceVersionPeer::RESOURCE_UUID, $resource-
>getUuid());
79. $c-
>addDescendingOrderByColumn(ResourceVersionPeer::NUMBER);
80. return ResourceVersionPeer::doSelectOne($c);
81. }
82.
83. /**

# at sfPropelVersionableBehavior-
>getLastVersion(object('steerCMSBlogInstance'))
in n/a line n/a ...

# at call_user_func_array(array(object('sfPropelVersionableBehavior'),
'getLastVersion'), array(object('steerCMSBlogInstance')))
in SF_ROOT_DIR/plugins/steerCMSBlogPlugin/lib/model/om/
BasesteerCMSBlogInstance.php line 967 ...

964.
965. array_unshift($arguments, $this);
966.
967. return call_user_func_array($callable, $arguments);
968. }
969.
970.

# at BasesteerCMSBlogInstance->__call('getLastVersion', array())
in n/a line n/a ...

# at steerCMSBlogInstance->getLastVersion()
in SF_ROOT_DIR/plugins/sfPropelVersionableBehaviorPlugin/lib/
sfPropelVersionableBehavior.class.php line 163 ...

160. $resource-
>setUuid(sfPropelUuidBehaviorToolkit::generateUuid());
161. }
162.
163. if ($version = $resource->getLastVersion())
164. {
165. $resource->setVersion($version->getNumber() + 1);
166. }

# at sfPropelVersionableBehavior-
>preSave(object('steerCMSBlogInstance'), null)
in n/a line n/a ...

# at call_user_func(array(object('sfPropelVersionableBehavior'),
'preSave'), object('steerCMSBlogInstance'), null)
in SF_ROOT_DIR/plugins/steerCMSBlogPlugin/lib/model/om/
BasesteerCMSBlogInstance.php line 378 ...

375.
376. foreach
(sfMixer::getCallables('BasesteerCMSBlogInstance:save:pre') as
$callable)
377. {
378. $affectedRows = call_user_func($callable, $this,
$con);
379. if (is_int($affectedRows))
380. {
381. return $affectedRows;

# at BasesteerCMSBlogInstance->save()
in SF_ROOT_DIR/cache/backend/prod/modules/autoSteerCMSBlogInstance/
actions/actions.class.php line 112 ...

109.
110. protected function
savesteerCMSBlogInstance($steer_cms_blog_instance)
111. {
112. $steer_cms_blog_instance->save();
113.
114. }
115.

# at autoSteerCMSBlogInstanceActions-
>savesteerCMSBlogInstance(object('steerCMSBlogInstance'))
in SF_ROOT_DIR/cache/backend/prod/modules/autoSteerCMSBlogInstance/
actions/actions.class.php line 58 ...

55. {
56. $this->updatesteerCMSBlogInstanceFromRequest();
57.
58. $this->savesteerCMSBlogInstance($this-
>steer_cms_blog_instance);
59.
60. $this->setFlash('notice', 'Your modifications have
been saved');
61.

# at autoSteerCMSBlogInstanceActions->executeEdit()
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 344 ...

341. {
342. $this->getContext()->getLogger()->info('{sfAction}
call "'.get_class($this).'->'.$actionToRun.'()'.'"');
343. }
344. $ret = $this->$actionToRun();
345. return $ret;
346. }
347. }

# at sfActions->execute()
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 935 ...

932. $timer =
sfTimerManager::getTimer(sprintf('Action "%s/%s"', $moduleName,
$actionName));
933. }
934. $actionInstance->preExecute();
935. $viewName = $actionInstance->execute();
936. if ($viewName == '')
937. {
938. $viewName = sfView::SUCCESS;

# at sfExecutionFilter->execute(object('sfFilterChain'))
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 1040 ...

1037. {
1038. sfContext::getInstance()->getLogger()-
>info(sprintf('{sfFilter} executing filter "%s"', get_class($this-
>chain[$this->index])));
1039. }
1040. $this->chain[$this->index]->execute($this);
1041. }
1042. }
1043. public function hasFilter($class)

# at sfFilterChain->execute()
in SF_ROOT_DIR/lib/symfony/filter/sfFlashFilter.class.php line 50 ...

47. }
48.
49. // execute next filter
50. $filterChain->execute();
51.
52. // remove flash that are tagged to be removed
53. $names = $userAttributeHolder->getNames('symfony/flash/
remove');

# at sfFlashFilter->execute(object('sfFilterChain'))
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 1040 ...

1037. {
1038. sfContext::getInstance()->getLogger()-
>info(sprintf('{sfFilter} executing filter "%s"', get_class($this-
>chain[$this->index])));
1039. }
1040. $this->chain[$this->index]->execute($this);
1041. }
1042. }
1043. public function hasFilter($class)

# at sfFilterChain->execute()
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 858 ...

855. {
856. public function execute($filterChain)
857. {
858. $filterChain->execute();
859. $response = $this->getContext()->getResponse();
860. $content = $response->getContent();
861. if (false !== ($pos = strpos($content, '</head>')))

# at sfCommonFilter->execute(object('sfFilterChain'))
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 1040 ...

1037. {
1038. sfContext::getInstance()->getLogger()-
>info(sprintf('{sfFilter} executing filter "%s"', get_class($this-
>chain[$this->index])));
1039. }
1040. $this->chain[$this->index]->execute($this);
1041. }
1042. }
1043. public function hasFilter($class)

# at sfFilterChain->execute()
in SF_ROOT_DIR/lib/symfony/filter/sfCacheFilter.class.php line 56 ...

53. // execute this filter only once, if cache is set and
no GET or POST parameters
54. if (!sfConfig::get('sf_cache') || count($_GET) ||
count($_POST))
55. {
56. $filterChain->execute();
57.
58. return;
59. }

# at sfCacheFilter->execute(object('sfFilterChain'))
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 1040 ...

1037. {
1038. sfContext::getInstance()->getLogger()-
>info(sprintf('{sfFilter} executing filter "%s"', get_class($this-
>chain[$this->index])));
1039. }
1040. $this->chain[$this->index]->execute($this);
1041. }
1042. }
1043. public function hasFilter($class)

# at sfFilterChain->execute()
in SF_ROOT_DIR/lib/symfony/filter/sfBasicSecurityFilter.class.php line
69 ...

66. if ($credential === null || $user-
>hasCredential($credential))
67. {
68. // the user has access, continue
69. $filterChain->execute();
70. }
71. else
72. {

# at sfBasicSecurityFilter->execute(object('sfFilterChain'))
in SF_ROOT_DIR/plugins/sfGuardPlugin/lib/
sfGuardBasicSecurityFilter.class.php line 36 ...

33. }
34. }
35.
36. parent::execute($filterChain);
37. }
38. }
39.

# at sfGuardBasicSecurityFilter->execute(object('sfFilterChain'))
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 1040 ...

1037. {
1038. sfContext::getInstance()->getLogger()-
>info(sprintf('{sfFilter} executing filter "%s"', get_class($this-
>chain[$this->index])));
1039. }
1040. $this->chain[$this->index]->execute($this);
1041. }
1042. }
1043. public function hasFilter($class)

# at sfFilterChain->execute()
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 1006 ...

1003. {
1004. public function execute($filterChain)
1005. {
1006. $filterChain->execute();
1007. if (sfConfig::get('sf_logging_enabled'))
1008. {
1009. $this->getContext()->getLogger()->info('{sfFilter}
render to client');

# at sfRenderingFilter->execute(object('sfFilterChain'))
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 1040 ...

1037. {
1038. sfContext::getInstance()->getLogger()-
>info(sprintf('{sfFilter} executing filter "%s"', get_class($this-
>chain[$this->index])));
1039. }
1040. $this->chain[$this->index]->execute($this);
1041. }
1042. }
1043. public function hasFilter($class)

# at sfFilterChain->execute()
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 590 ...

587. {
588. $this->context->getI18N()-
>setMessageSourceDir(sfLoader::getI18NDir($moduleName), $this->context-
>getUser()->getCulture());
589. }
590. $filterChain->execute();
591. }
592. else
593. {

# at sfController->forward('steerCMSBlogInstance', 'edit')
in SF_ROOT_DIR/cache/backend/prod/config/config_core_compile.yml.php
line 2283 ...

2280. $request = $this->getContext()-
>getRequest();
2281. $moduleName = $request->getParameter('module');
2282. $actionName = $request->getParameter('action');
2283. $this->forward($moduleName, $actionName);
2284. }
2285. catch (sfException $e)
2286. {

# at sfFrontWebController->dispatch()
in SF_ROOT_DIR/web/cms/index.php line 13 ...