Need a way to change the default layout from the Designer app.

Add as part of the social app.

Hi, I have a tiny addition that you may or may not like to see inside elefant, and I'm slightly unsure as to where it should live in the code due to how you select the caching class at runtime. It is simply an tiny extension to your existing Cache class to make caching even quicker to add to existing code. It is used like so:

$value = $memcache->cache('mykey', '30 minutes', function () {
    // Generate expensive value here, eg. database query
    return $expensive_value;
});

It is possible to "monkey-patch" the cache class at runtime by adding this code at ~line 50 in index.php:

$memcache->cache = function ($key, $timeout, $function) {
    if (($val = $this->get($key)) === false) {
        $val = $function();
        $this->set($key, $val, strtotime($timeout) - time());
    }
    return $val;
};

But I'm sure you'll have a better way of integrating it should you choose to do so!

This information is also duplicated here, http://demonastery.org/72/tiny-memcached-wrapper/ where I posted it initially. I should point out that it was because of your Reddit post that I decided to play around with Memcache in the first place, so thank you for that :)

Should be a matter of taking the code from the image dialog and moving it over.

Need a dynamic object handler that shows a textarea to paste HTML, but converts it to a key and stores the HTML elsewhere so the tag doesn't become:

{! admin/html?content=<strong>some+text</strong> !}

As you can see, that would get ugly fast. Need a callback setting for replacing the input in dynamic objects, for example the callback could simply do:

<?php

function my_dynamic_object_callback ($data) {
    // store the data
    db_execute ('insert into dynamic_objects (id, data) values (null, ?)', $data);

    // return the id of it
    return db_lastid ();
}

?>

Then the handler rendering the dynamic object would be able to say:

<?php

$html = db_shift ('select data from dynamic_objects where id = ?', $data['id']);

?>

An API for this would be simple to create.

Add as part of the social app.

An installer app that would:

1. Checks folder permissions
2. Get database connection settings, test connection
3. Get site name, email, choose admin password
4. Create database based on the above
5. Write the conf/config.php file
6. Disable the installer from running again (touch conf/installed then installer can check file_exists(conf/installed) and exit)

Copying the files over via FTP doesn't copy dot-files, so users can get through the install, see the working homepage, then get a 404 when they click /admin or /blog.

Would be good to be able to check for updates and install them through the admin panel, at least bug fix releases. The installer mechanism could be a starting point for applying the updates, but source files would need to be updated too which might mean increased permissions on files...

Checking for updates could be done via an iframe + javascript so it doesn't affect the load of the admin toolbar.

A quick edit button for pages and blocks that lets you edit just the visible elements in-place on the page and save them without leaving the page.

It would be good to be able to drop an app into apps/ and have Elefant recognize that it needs to be installed, and what the install handler is. Some thoughts:

1. An apps table with installed and version status for each app. Missing entries wouldn't be installed at all yet.
2. In the [Admin] block of each app's conf/config.php file it could have these settings:

installer = myapp/install
upgrade = myapp/upgrade
version = 1.0

1. Installer-specific methods could be added to the controller or to the admin app such as:

<?php

// after admin checking do:
if ($this->installed ('myapp')) {
    $page->title = 'Already installed';
    return;
}

// run the install then:
$this->mark_installed ('myapp', '1.0');

?>

1. The admin/head could check the install status in the db and notify admins of apps needing install or updates...

Needs fleshing out, but it's a start.

Embed fields would be address, city, state/province, country, and zip/postal code. It would then generate a map with a marker.

Would also be handy in Designer app.

Should take the form:

$ ./conf/elefant backup /path/to/backups

Steps:

1. mkdir cache/backup-{{ timestamp }}
2. ./conf/elefant export-db cache/backup-{{ timestamp }}/db.sql
3. cp .htaccess cache/backup-{{ timestamp }}/
4. cp -R * cache/backup-{{ timestamp }}/
5. tar -cf cache/backup-{{ timestamp }}.tar cache/backup-{{ timestamp }}
6. gzip cache/backup-{{ timestamp }}.tar
7. mv cache/backup-{{ timestamp }}.tar.gz {{ path_to_backups }}/
8. rm -Rf cache/backup-{{ timestamp }}

Should take the form:

$ ./conf/elefant export-db exported-data.sql

Should create the SQL to be compatible with the database type used by the site (sqlite, mysql).

Need to be able to drag it away to remove it (and have it reappear in/refresh the right column)

Guys get an error on a new install using mysql.

Connection Error:

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'lock ( id int not null auto_increment primary key, user int not null, resource v' at line 1

My immediate guess would be that 'lock' is a keyword in mysql, and we have called a table after it?

Use an environment variable to load alternate configurations for different servers (development, staging, production), e.g.:

define ('ELEFANT_ENV', (getenv ('ELEFANT_ENV') ? getenv ('ELEFANT_ENV') : 'production');

$conf = parse_ini_file ('conf/' . ELEFANT_ENV . '.php');

Then specify your environment in .htaccess or your vhost configuration:

SetEnv ELEFANT_ENV development

• Could also force debugging to be off for production.
• We would also need to update any hard-coded references to conf/config.php or split it into conf/general.php and env-specific settings like database info into conf/staging.php and the like.
• Need to find out how to set environment variables in Nginx

Could this just be done with a cookie?

Should scale down automatically to fit mobile screens, or render an alternate layout for mobile devices.

Enter the video URL and the size and it will embed the video.

See lib/MongoModel.php and tests/MongoModelTest.php for model info. See lib/MongoManager.php for connection info. Already implemented:

• connection settings
• creating basic models
• __construct()
• put(), get(), and remove()

Still several methods yet to be implemented:

• group()
• fetch()
• single()
• count()
• fetch_orig()

Just like the youtube dynamic object. Use vimeo video urls (e.g., http://vimeo.com/23299746) and grab the video ID then generate the appropriate embed code, such as:

<iframe src="http://player.vimeo.com/video/23299746?title=0&amp;byline=0&amp;portrait=0" width="480" height="270" frameborder="0"></iframe>

Currently uses a global $db object to contain a single PDO reference. Would need to store multiple database connections perhaps in conf/db.php...

[master]

; connection info

[slave1]

; connection info

Then lib/Database.php would need a helper to balance reads between connections (with writes still going to master).

In edit forms, must unlock the object too.

Replace direct filesystem calls with a FileStore class that extends Model, with a schema like:

create table filestore (
    path char(128) primary key,
    link char(255),
    size int not null,
    mtime int not null
)

The link field would reference the S3 copy once synced, or be empty if not. We would then need a background task to sync uploaded files to S3 (with option to delete local version too). A download handler (e.g., /filemanager/dl/path/to/file.ext) would simply have to do the following:

<?php

$fs = new FileStore (join ('/', $this->params));
if ($fs->error) {
    // check if local file does exist and if so, create entry.
    // it may have been uploaded outside the system.
    // if not, real error
}

if (! empty ($fs->link)) {
    $this->redirect ($fs->link);
}
$this->redirect ('/files/' . $fs->path);

?>

That way dynamic embeds can have a "Choose a file" option.

When your cursor is in one of the dynamically embedded objects and you click the dynamic objects icon, you should be able to edit the object's settings.

Should be the same across all dialog windows.

Add as part of the social app.

This would make it possible to create layout "themes" by creating a themename.html file and a corresponding themename folder for associated assets (css, images) and just drop it into layouts.

Then to make that the default theme, you would simply change the setting for "Default layout" from default to themename and the site would change.

Allow developers to customize the logo, name, and colours via a configuration file, so they can produce their own branded version of Elefant.

Just like the filemanager/swf handler, flv and mp4 files should embed a video player instead of a link.

Would simply need to clear memcache on the hooks and api changes, then it could be set to speed up all navigation handlers substantially.

Default as it is now should be the minimum. Add some JS to resize if the window height is greater.

For layouts: An iframe filling the bottom of the window (with popout option?), updating every x seconds.
For stylesheets: The same iframe, but with a "choose a layout" option.

List will quickly grow to be too long to be manageable.

Shipping with full internationalization and an indexed translation file would allow translators to contribute new languages more easily.

An app for managing translations of strings/objects in published sites

Instead of having separate script names to remember, there should be one main script with help info that runs each command, for example:

# conf/createdb.php becomes:
$ ./elefant install

# conf/translations.php becomes:
$ ./elefant build-translation de

# conf/genpass.php becomes:
$ ./elefant encrypt-password "my pass here"

# conf/make.php becomes:
$ ./elefant build-app myapp

# print all commands:
$ ./elefant --help

# help for the build-app command:
$ ./elefant build-app --help

This would give a much better base for building on, and be much clearer for developers to use.

Use $this->cache = 300; to tell the Controller to cache a handler with a key of the form app/handler and bypass it entirely next time. You can then clear it in another handler later via $cache->delete ('app/key');.

1. Create a way to set and show notifications for add/edit/delete actions
2. Instead of showing a 'Page saved' page with a 'Continue' link, set a notification message and send them to the link immediately
3. On the next page, show the notification

This will save a lot of clicks and improve overall usability.

Committing changes to a database can be scary for new users. We should add more info to the database screen of the installer to explain what it will do.

At PHP Fog we have the apache_get_modules() command disabled for security purposes, which causes a false "Missing mod_rewrite" error when installing. I patched in a quick fix that removes this check since PHP Fog will always have mod_rewrite enabled.

Would noticeably improve bandwidth and performance of gallery pages.

Right now it simply embeds the following:

<div class="embedded">{! app/handler !}</div>

Behind the scenes, it will need:

• a way to configure which handlers are embeddable and what parameters they require
• a handler that generates a list of all embeddable handlers from all apps
• a handler that generates a form to input any parameters needed by a chosen handler
• a jWysiwyg plugin that calls out to these handlers