Auto Install Module Missing(?)

[crawfjs]

On a fresh install of stackbox, I receive this message on every request

---

Notice: Undefined index: module in stackboxcms/alloy/Plugin/Spot/Plugin.php on line 139
ERROR

Alloy\Exception\FileNotFound (Code: 0)
Module '' not found

Stack Trace

File: stackboxcms/alloy/lib/Alloy/Kernel.php (450)
#0 stackboxcms/alloy/Plugin/Spot/Plugin.php(139): Alloy\Kernel->dispatch(NULL, 'install')
#1 [internal function]: Plugin\Spot\Plugin->autoinstallOnException(Object(PDOException))
#2 stackboxcms/alloy/lib/Alloy/Events.php(179): call_user_func(Array, Object(PDOException))
#3 stackboxcms/app/www/index.php(147): Alloy\Events->filter('dispatch_except...', Object(PDOException))
#4 {main}

Request Data

Array
(
)

[vlucas]

This error has been fixed, and it should auto-install now. There is still a manual step involved in setting up a new site record since I merged in the site branch, however. You need to add a row to the 'sites' table, and one to the 'sites_domains' table that connects the hostname to the site.

[poetaster]

Hmmm. I have the same issue and would love to 'add the row' to site and sites_domains, but it's not clear what should be added? if it's all of the details for site and domain, then I'd need to troll through all of the data to find out what legitimate values might be. Don't get why this issue is closed since it obtains from a fresh install. Today.

I did, sort of get to the point of adding a user. Just putting values that 'seemed' to fit in place. This resulted in the need to manually install www/site/sitename/content (etc) .... and none of the features (beyond adding users with manual page routes) work.

It's a debian squeeze (php 5.3.3) running in fcgi mode with a virtual pointing at app/www as docroot.

As far as I can tell, this isn't usable in any real sense but maybe a good test harness for alloy? I'm insterested in alloy anyway and also want to be rid of the backend.

[poetaster]

Ok, manually adding site/shortname/content seemed to get something going. don't get it. why short name!

It's pretty messy and evident that something is odd in the setup. In any case i can add pages and modules and so on, but in the 'front end' that is to say and unauthenticated user sees a bare page (css errors). I'm loathe to open up other tickets, since it's obvious that the install fails to be done correctly.

I can fix these errors by selecting 'default/index" instead of the default '/path/to/root/app/www/themes/default/index'

[vlucas]

I agree that the install steps are awkward. I will re-open this ticket until I can fully solve the issue with an more complete auto-installer.

This CMS is still in a alpha/beta stage, so be patient (and consider contributing!) :).

[poetaster]

On Thu, 22 Sep 2011 12:55:12 -0700, Vance Lucas
reply@reply.github.com
wrote:

I agree that the install steps are awkward. I will re-open this ticket
until I can fully solve the issue with an more complete auto-installer.

This CMS is still in a alpha/beta stage, so be patient (and consider
contributing!) :).

Thanks, I'll take a crack at writing a module to see if it's something I
can add to.

[vlucas]

I updated the initial page visit process to automatically insert a site and site_domains record, so now you will at least be looking at a working website out of the box. It's still not a full guided auto-installer, but now at least we're one step closer.

[poetaster]

cool! I haven't had time but I have a proper environment setup so I'll try to get back to this.