SteerCMS error

[LordKain]

Hello,
I just completed all the steps for installing the cms, but that access
in the following url, returns an error: "http://streercms.local/". The
error is 404, it's . but that access to: "http://streercms.local/cms"
and input admin/admin, I have redirection to: "http://streercms.local/
cms/login" and this pages do not exist!!!

I appreciate all the help you can give me! I am lo ing forward to
your answer, a.s.a.p.

thank you very much

[Konny Zurcher]

Hi,

When you use http://localhost/ do you actually see the frontend page? I ask that because if you can see the frontend with the navigation then there will also be an 404 error because there was no page created yet in Steer CMS. To rectify that create a Site directory in the CMS (under CONTENT) in the navigation and call it index.html.

About the login. If you check your {path_where_steercms_installed}/plugins directory. Is there a directory called sfGuardPlugin and more directories available. If you used the Sandbox for installing and not the SVN version the it can be that some of the directories were suppressed when you extracted the archive file (steerCMSSandbox_0_1_0.tar.gz).

If http://localhost/cms/login does not work then try http://localhost/cms/sfGuardAuth/signin. You should then get to the Login page for the CMS where you can login with admin/admin.

If you are using an apache web server. Did you edit the httpd.conf file? At the end of that file under the title "### Section 3: Virtual Hosts" you will need to add this:

This example can be used if you want to run steerCMS under the apache standard port 80 ... so you can access the pages with httpd://localhost/

### STEER - CMS Sandbox

 <VirtualHost *:80>

  ServerName steerCMSSandbox

  DocumentRoot "{directory_where_steerCMS_installed}/web"

  DirectoryIndex index.php

  Alias /sf /$data_dir/symfony/web/sf  <-- this path will have to be adjusted eventually depending on your system configuration

  Alias /cms/sf /$data_dir/symfony/web/sf  <-- this path will have to be adjusted eventually depending on your system configuration

 <Directory "{directory_where_steerCMS_installed}/web">

  AllowOverride All

 </Directory>

</VirtualHost>

After adding that you will have to restart your apache web server so that the changes come into effect ..

Let me know if it worked and when not let me know also if you work with windows or linux. Steer CMS was tested thoroughly on linux systems and Mac OS X. Windows system configuration needs some special considerations.

Cheers,

Konny Zurcher

Steer CMS - Development Team

[freshup]

Hello!
I'm using XP and have the same problem. I can't login as Admin, cause
there is no Login path. Also there is no /sfGuardAuth/signin.I've
found sfGuardAuth plugin in the root, but how it can help me?

Thanks

[Piers Warmers]

Hi freshup,

Hmm.. well:

/cms/login

and 

/cms/logout

Will get you to the respective authentication locations.

But if you point your browser simply at /cms without being logged in, a login prompt should be presented.

Let me know if that does the trick :)

- Piers

[freshup]

The problem is that there is no /cms/login and /cms/logout folders :)
And so, after typing login and pass, the requested url can't be found.

[Piers Warmers]

Hi,

> The problem is that there is no /cms/login and /cms/logout folders :)

That's actually correct. So we use Symfony routing to take care of
those routes, pointing them back to the relevant modules / actions.

> And so, after typing login and pass, the requested url can't be found.

OK, so stepping back a moment, are you testing with the pre-packaged
version of the sandbox or via SVN?

- Piers

[freshup]

I'm using pre-packaged version of the sandbox.

It's my first time working with Symfony, that's why my questions can
be a little foolish.
By the way, when I'm typing /cms/backend_dev.php (not /cms) after
being logged in I get such a message:

[wrapped: Could not execute query [Native Error: Table
'hitch.sf_guard_user' doesn't exist] [User Info: SELECT
sf_guard_user.ID, sf_guard_user.USERNAME, sf_guard_user.ALGORITHM,
sf_guard_user.SALT, sf_guard_user.PASSWORD, sf_guard_user.CREATED_AT,
sf_guard_user.LAST_LOGIN, sf_guard_user.IS_ACTIVE,
sf_guard_user.IS_SUPER_ADMIN FROM sf_guard_user WHERE
sf_guard_user.USERNAME='admin' AND sf_guard_user.IS_ACTIVE=1 LIMIT
1]] ... and a long stack trace

*where "hitch" is a database login.

[Piers Warmers]

Hi freshup,

It's my first time working with Symfony, that's why my questions can
be a little foolish.

No question is foolish :) but... I might pause on that point and just say that Steer CMS, in its infancy, probably requires some Symfony knowledge.

It the very least, there are a number of stack configurations which might need fine tuning. Without going into too much detail, it definitely sounds like the routing isn't correctly being handled. This could stem from a number setup steps. In addition to that, you will need to make sure the database is built by using the CLI.

$ symfony propel-build-all-load backend

But, while these pieces will be very familiar to Symfony developers, it might seem like voodoo if this is your first introduction to Symfony.

In fact, if you haven't yet set Symfony up on your machine, most of this will be impossible.

What I'd recommend, is taking a look at:

http://www.symfony-project.org/installation

And then some of the starter tutorials. 

Hope this helps :)

Piers

[freshup]

Thank you for all suggestions! I think, it's a great idea to read
tutorials at first ;)