@schiesbn Sure. I’ve haphazardly tried it already, but I’ll give it a proper go sometime soon.

### Description
The Apache log file for my Owncloud site sporadically registers ”File does not exist: *[my OC root directory]*/data” errors from Owncloud; these go back to at least July last year (2014). To me this appears as if OC was erroneusly trying to access a hard-coded path for the data directory under the OC root, whereas my data directory actually resides elsewhere, entirely outside www my root, and there is no data directory under OC root.

The error timestamps indicate they only occur during daytime when I’m interacting with my installation (I’m the sole user), possibly only through the web interface, as I have the desktop client always on but the errors are rare relative to that. I use the web interface less and I think it corresponds to the timestamps better (but not all web interactions result in the error either, and I haven’t been able to pinpoint any specific action that triggers it).

Apart from those errors in the log my Owncloud installation appears work just fine, so the issue seems pretty harmless. I’ve considered creating an empty data directory under the OC root in case that might make the error go away, but then again it might just break something. Anyway, because it looks like a bug, I figured I’d better report it.

### Server configuration
**Operating system**: Debian Wheezy (I think; I’m a non-privileged user on shared hosting)

**Web server:** Apache/2.2

**Database:** MySQL 5.5.43

**PHP version:** 5.4.39-0+deb7u2

**ownCloud version:** 8.0.4.2

**Updated from an older ownCloud or fresh install:** updated

**List of activated apps:**
* Activity 1.2.0
* Deleted files 0.6.2
* External storage support 0.2.3
* First Run Wizard 1.1
* PDF Viewer 0.7
* Pictures 0.6.0
* Share Files 0.6.1
* Text Editor 0.4
* Updater 0.4
* Versions 1.0.5
* Video Viewer 0.1.3

**The content of config/config.php:**

”`
’datadirectory’ => ’/siilo/users/mummila/owncloud-data’,
’asset-pipeline.enabled’ => true,
’dbtableprefix’ => ’oc_’,
’dbtype’ => ’mysql’,
’forcessl’ => true,
’installed’ => true,
’logdateformat’ => ’l, j. F Y’,
’loglevel’ => 3,
’mail_smtpmode’ => ’smtp’,
’mail_smtpport’ => ’465’,
’mail_smtpsecure’ => ’ssl’,
’maintenance’ => false,
’max_filesize_animated_gifs_public_sharing’ => 5,
’preview_max_filesize_image’ => 5,
’session_lifetime’ => 60 * 60 * 24 * 15,
’theme’ => ”,
’version’ => ’8.0.4.2’,
”`

**Are you using external storage, if yes which one:** none

**Are you using encryption:** no

**Are you using an external user-backend, if yes which one:** none

### Client configuration
**Browser:** Chromium 37.0.2062.120 (build 281580)

**Operating system:** Ubuntu 12.04

### Logs
#### Web server error log
”`
[Sun Jun 14 13:57:52 2015] [error] [client 217.30.184.173] File does not exist: /var/www/use
rhome/mummila/sites/mummila.kapsi.fi/secure-www/oc/data
[Sun Jun 14 13:58:47 2015] [error] [client 217.30.184.173] File does not exist: /var/www/use
rhome/mummila/sites/mummila.kapsi.fi/secure-www/oc/data
[Sun Jun 14 14:29:18 2015] [error] [client 217.30.184.173] File does not exist: /var/www/use
rhome/mummila/sites/mummila.kapsi.fi/secure-www/oc/data
”`

#### ownCloud log (data/owncloud.log)

(No recent events coinciding with the log above. Last entry below, with my desktop IP address redacted, from two days ago)
”`
{”reqId”:”71513d1b6f44276a8cd6cad21bc98864″,”remoteAddr”:”[my desktop IP]”,”app”:”PHP”,”message”:”Undefined index: extension at \/var\/www\/userhome\/mummila\/sites\/mummila.kapsi.fi\/www\/oc\/apps\/files_versions\/lib\/storage.php#320″,”level”:3,”time”:”2015-06-12T04:37:22+00:00″}
”`

@trentrichardson I’ve just tested the branch with the change and it’s working perfectly.

Hey @trentrichardson, and thanks for the response! The best I could figure in the meantime was to initialize the prompt differently in each branch, like so:

    if (user.isSignedIn) {
        states = {
            signOut: states.signOut,
            signIn: states.signIn,
            register: states.register
        };
    } else {
        states = {
            signIn: states.signIn,
            signOut: states.signOut,
            register: states.register
        };
    }
    thePrompt = $.prompt(states);

But it’s definitely better to have true support for this in the extension itself. Excellent!

Sorry if this is obvious, but how can I open a multiple-state prompt in a specific state other than the first one in the states object? In other words, in the first statesdemo example, how can I open the prompt in state1 instead of state0?

I’m working on a login/logout/registration form with each of the three as a separate state and would like to start the prompt in either the ”log in” or ”log out” state depending on whether the user is currently logged in or not.

(I’m trying to work out the solution reading Impromptu’s source code, but figured I’d also pose this question here for others like me to find in the future.)

@virtadpt, good to know that the search will scale. As long as it’s snappy to open and to react to typing, I don’t think I’ll need anything fancier in the popup selector.

And yes, DataOutputAgent is what I’m currently using for emitting the feeds (I just spelled it with whitespace above), unless I’m missing your point.

I’m a heavy Yahoo Pipes user, and recently deployed Huginn to Heroku to see if I could use it to replace Pipes. My main motivation for this is ensuring continuity (should Y! decide to pull the plug on Pipes), but an almost equally important one is that managing Pipes has become nightmarish with the amount of individual pipes I’ve accumulated, currently more than 150.

With Huginn I see I can employ Scenarios to group agents together, which is already more than what Pipes offers. But duplicating just a couple of my Pipes’ functionality in Huginn has already produced six agents. Additionally, unlike Pipes, Scenarios can’t be nested (into Scenarios of Scenarios), so I fear that finding and managing individual agents, and perhaps even Scenarios, would eventually become as complicated as managing Pipes once I’d get in double- and triple-digit amounts.

So what I’d like to have in the UI is more means to classify and search for agents. My old-fashioned instinct makes me suggest a directory-like tree structure, but more modern and semantic solutions such as tagging could work just as well if not better. Being able to select an Agent Type could also be one way to narrow down the main agents list (/agents). That list also doesn’t seem to have a search function. The popup list for selecting agents in the Scenario editor does have a search and it seems to work nicely, with real-time results and all, although I’ve not yet created hundreds of agents to see how well it scales.

(In my case, another natural way to reduce the clutter would be having a true singular RSS feed filtering agent (fetch a feed, filter the results, emit the filtered feed), which is my main use-case for Pipes. Currently I’m using an RSS Agent to fetch the feed, a Trigger Agent to filter the results and a Data Output Agent to output the filtered feed, resulting in three separate agents for each of my Pipes. But this is a separate ”Agent Suggestions” issue from the one I’m reporting here. And of course there might already exist a smarter way to do this which I’m just not aware of.)

In README, 2.2.1. Step 1 says I need to add ”execute pathogen#infect()” to .vimrc, while the second point in the checklist at the end of 2.2.2. Step 2 says it should have been ”call pathogen#infect()”. I’m guessing both work, but it should probably be consistently the same in the instructions.

I’ve worked around that enum error (since before owncloud 7 already) by adding this in 3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Platforms/MySqlPlatform.php:

@@ -661,6 +661,7 @@
     protected function initializeDoctrineTypeMappings()
     {
         $this->doctrineTypeMapping = array(
+            'enum' => 'string',
             'tinyint'       => 'boolean',
             'smallint'      => 'smallint',
             'mediumint'     => 'integer',

I think post-processing should also rip out (at least) id, class and style attributes from the content. Some pages I fetch using feedmod have elements with ids such as ”overlay” in them that pick up tt-rss’s styling, making things look wonky.