Hi

I had the install error 'Unable to find source directory' at the installing Apps stage. Skipped that, and have noticed that the themes in the Open Enterprise profile are not being recognized (perhaps it is not only themes, but that's what I've noticed so far).

Folder / file permissions are ok (all accessible). FTP / sFTP connection was available and working fine.

I think it seems likely the install error and the missing connection to the profile are one and the same issue.

Shame more people are not using and testing this. It looks great, and very useful for creating quick and comprehensive sites suitable for typical users.

Comments

August1914’s picture

August1914 CreditAttribution: August1914 commented

Could you describe how you're going about the install? What platform are you installing on?

I'm guessing that when you say "at the installing Apps stage", you mean on initial installation? If you saw "Unable to find source directory" at that point, I suspect that the installer didn't have rights to create the directory or write to directories, and that would result in an irregular installation.

I would suggest starting over, and at then after the standard installation steps, at the OE "Apps" page, select [Skip this step] and check out the site before installing apps. You should be able to change the theme to Omega or Navin at this stage. Then you can proceed to installing the Apps individually. If the installer doesn't have rights to write to sites/all.. of course it's not going to work.

mikeaja’s picture

mikeaja CreditAttribution: mikeaja commented

I should have explained everything I did.

Yes you're right that this first occurred on a new, fresh install, at the 'Apps' stage. It's the same type of account of many other Drupal installations. Plus I've since installed a standard Drupal install to the same place.

I would say the issue you describe is unlikely to be the cause anyway, unless installing to a subdirectory (which I wasn't). If writing to root was an issue, it wouldn't get past the first stage.

After the issue, I did almost exactly as you described. After 'Skipping' the Apps step, the site is there. But as I mentioned above, neither Omega nor Navin were available in the themes list. Assuming therefore the Profile's themes not being accessible (which suggests Drupal is not recognising the profile perhaps?).

I think it is fair to assume that these two issues are linked - the Apps issue with 'source directory' may be because an an issue creating a link to the Profile. Permissions are fine (as in, this is my area - the server and setup is about as good as it gets for Drupal).

Specs: Vista, Firefox 11, quality LAMP VDS (up to date and with many Drupal installs). I have the option of PHP 5.2.x or 5.3.x, but I doubt PHP version is the issue.

The trouble is with this type of issue, too many users will try it and not continue and not post here. So it is hard to judge how many may have experienced this.

I have a vague recall of very early OpenAtrium having such an issue, although I can't find anything on their support site.

August1914’s picture

August1914 CreditAttribution: August1914 commented

First just to reiterate, I can install oe 7.x-1.0-beta7 successfully, repeatedly. (I build on mamp, and then after some site-building, move to lamp.)

Distros try to bundle (and hide) complexity, and this is a great thing, but often I have to break it down to sort out what is a problem in the build, what is a problem on the host environment, and what is a problem in my own misconception of how things are supposed to work.

If oe installs themes to {webroot}/openenterprise/themes/{navin|omega|rubin|tao}, then we'd expect to see the themes available to the drupal site, no? What would prevent drupal's theme system from seeing those themes and showing them as available? (is that what you're seeing?)

mikeaja’s picture

mikeaja CreditAttribution: mikeaja commented

Yep, that's what I'm seeing. The themes are there, in the correct folder. And can confirm now it is the whole profile. Profile specific modules aren't showing either.

What would prevent drupal's theme system from seeing those themes and showing them as available?

Right....... what, indeed...... This has me slightly baffled. I'm sure this is the same issue a pre-release OpenAtrium had (not one I had, but that I remember reading about).

Perhaps the key here is the local install compared to a remote install. I'm not sure why though. It's not a difference I've experienced myself.

i appreciate your input though. If I get more time, I'll try to get to the bottom of this. I just installed NodeStream to the same location, without issue. I was torn anyway about which one to use for a project.

Hopefully if others have the issue they will be encouraged to post with an existing thread.

August1914’s picture

August1914 CreditAttribution: August1914 commented

Have your tried a rinse cycle? drop database, create database, overwrite settings.php with default.settings.php, run the install (skip apps).

I'm interested in nodestream as well. There seems to be less momentum in terms of adoption at this stage, but it certainly has a really great team behind it

mikeaja’s picture

mikeaja CreditAttribution: mikeaja commented

No, but I could try that. I just never normally have to do anything like that...... I think this is a first for me with an install, other than memory / execution time issues (probably cause I'm so fussy about the hosting I use). I might try an xampp install instead.... follow a similar approach to yours.

The way nodestream is presented is excellent on their site, but yes, you're right about adoption based on Drupal stats.

mikeaja’s picture

mikeaja CreditAttribution: mikeaja commented

Well..... can't explain..... but 3rd time lucky. Thanks for your input August1914.

Now let's see what I can do with it..... new to Apps ....... I'd be interested to see what you've done with this so far, if you have sites you're able to provide links to.

mikeaja’s picture

mikeaja CreditAttribution: mikeaja commented
Status: Active » Closed (fixed)

I'll mark as closed (fixed). Sorry I can't provide an explanation. Nothing was changed. Just a 3rd re-install, and the 3rd time I made sure to 'Skip' Apps in the install process.

August1914’s picture

August1914 CreditAttribution: August1914 commented

Maybe the problem is fallout from a mysql timeout to a large write during the installation -- you might try opening up the window, in my.cnf:
max_allowed_packet = 100M
for example.