For example (not realistic mind):

Car:

• Make (Required, shown on create and update)
• Model (Not required, shown on create and update)
• Registration (Required, shown on create, not on update)

Upon creation of a car, everything is fine. When editing the car, the 'Registration' field does not show, however when saving changes, control states that 'Registration is required', although it already exists in the data.

Don't think this a major issue, as I doubt there are many (if any) use cases for this scenario.

Is it possible to add functionality to preview an article without needing to set it live.

We need a cool logo.

There should be a mechanism to set cookie options for express from inside properties.js

The most common use case for this will be to set the cookie's domain in the event the app needs to respond to requests on multiple subdomains.

To replicate on Unix/Mac:

git clone git://github.com/serby/control control-404-error-example
cd control-404-error-example
npm install
git clone git://github.com/domudall/control-404-error-example bundles/vegetable

Add vegetable to server.js, then start control with node app

Index page returns 404, however all other routes are rendered correctly (going through the process of creation via the new vegetable page).

Tried debugging route defined in genericAdminRoutes.js but to no avail.

Quite a few files still have tabs instead of spaces. Would be good to fix this for consistency.

Feature request for docs in project structure for offline reference when developing.

If you add information to a form mixin for that admin it wraps before the end of the line

When deleting a record in the cms, if the user is on page 3 and deletes a record the pagination resets back to the first record.

It would be nice if you could collapse the admin sidebar and make the form area wider when editing body content.

Have a look at the /admin/article/new on the clock site and you'll see I've has to limit the number of options on the rich-text toolbar to allow it to fix.

Using the asset manager with the same files produces duplicates in the data directory. More of a feature request, feel free to shoot me down if you don't feel it's necessary.

Without a timeout the node app will hang indefinitely if the DB is not available on connection.

As per: https://gist.github.com/357981

Password checking in the authentication module should use this method.

http://throwingfire.com/storing-passwords-securely/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+throwingfire+%28Throwing+Fire%29#notpasswordhashes

Would it be possible to support databases like MySQL or Postgresql?

Control needs a basic forgotten password journey for the admin.

Just went to have a look at the password reset journey, got this:

/Users/bengourley/Projects/control/bundles/administrator/lib/administratorModel.js:98
    return crypto.createHash('sha1').update(str).digest('hex');
           ^
ReferenceError: crypto is not defined
    at hashAdminState (/Users/bengourley/Projects/control/bundles/administrator/lib/administratorModel.js:98:12)
    at EventEmitter.requestPasswordChange (/Users/bengourley/Projects/control/bundles/administrator/lib/administratorModel.js:102:16)
    at /Users/bengourley/Projects/control/bundles/admin/controller.js:106:45
    at /Users/bengourley/Projects/control/lib/utils/mongodbCrudDelegate.js:213:9
    at /Users/bengourley/Projects/control/lib/utils/mongodbCrudDelegate.js:189:9
    at /Users/bengourley/Projects/control/node_modules/mongodb/lib/mongodb/cursor.js:129:9
    at /Users/bengourley/Projects/control/node_modules/mongodb/lib/mongodb/cursor.js:171:11
    at /Users/bengourley/Projects/control/node_modules/mongodb/lib/mongodb/cursor.js:463:35
    at Cursor.close (/Users/bengourley/Projects/control/node_modules/mongodb/lib/mongodb/cursor.js:682:5)
    at Cursor.nextObject (/Users/bengourley/Projects/control/node_modules/mongodb/lib/mongodb/cursor.js:463:17)

I think we should remove all but the 'Admin' and 'Administrator' bundles. All other bundles that we maintain should be optional and live in their own repos.

Bundles should then be installed with https://github.com/serby/control-cli or until that is ready, git clone bundle-repo

Discuss?

Whenever you edit an administrator their password is populated into the password field, and is changing on each save.

@domharrington Can you make pagination.js a npm module and refactor control to use it.

Control needs to be upgraded to node 0.8 but connect currently only works in 0.6.

Discuss

@domharrington @bengourley @aduncan88

With stylus 0.22.0 using the versionPath helper produces the following css:

background-image: url("/images/admin/content/0.0.1/logo-control.png")

After the upgrade to stylus 0.23.0 the following css is produced:

background-image: 'url("/images/admin/content/0.0.1/logo-control.png")'

This breaks the functionality of the helper and produces unexpected results.

Replace with the generic logger

Enforcing a unique constraint involves setting up a callback inside of model at present, it would be nice to be able to express this in the schema definition.

The route in the article bundle is really vague:

app.get('/:section/:article', ...)

This means that any bundles added after it can't have routes in the form /foo/bar.

e.g:

bundled.addBundles(__dirname + '/bundles/', [
  ...
  'article',
  'pageAdmin',
]);

My 'pageAdmin' bundle wants /admin/page, but this won't be reached because the article bundle preceded it (and takes precedence).

It's easy to resolve–just change the order, but could this be a problem further down the line? Is there a better solution?

Currently appearing with a dialog box with [Object object] in, clicking either option closes the dialog without any change.

http://awesomescreenshot.com/045b8sy4d

I believe Control should allow modules to have default ordering and have the ability to remember (per admin) their chosen ordering settings.

e.g. On adoption programme CMS you have to click date created table heading twice each time you navigate to new users. Like Atrox CMS it would be good to store admin preferences.

When creating viewSchema using generic, there is no check to see if the first field is hidden or in list before assuming it should be used as title field.

Example:

var viewSchema = generic.createViewSchema({
  groups: [{
    name: 'My broken view',
    description: 'This view is broken unless I explicitly set the title property',
    properties: {
      _id: {
        form: true,
        type: 'hidden'
      },
      name: {
        list: true,
        view: true,
        createForm: true,
        updateForm: true
      }
    }]
});
// ...remainder of code...

Sometimes you need to say that a textarea is: shortest, short, tall, tallest or smallest, small, big, bigest. I have been added these styles on projects that need them, but it would be good to have a more considered set of modifiers in control.

The update function implies that no error equals success and reports that back to the caller and the logger. It is possible that the returnedEntity will be null on callback, which means no document was found for update. If this occurs the update function should return an error stating the requested document was not found.

I will send across a pull request shortly.

Allow any of the view, list, form to be overridden with a custom view.

After the first administrator is created through /admin/setup, the application crashes with the following error:

Error: TypeError: undefined is not a function
    at Array.<anonymous> (/opt/projects/control/node_modules/mongodb/lib/mongodb/connection/server.js:168:49)
    at EventEmitter._tickCallback (node.js:126:26)

Output of npm list:

[email protected] /opt/projects/control
├── [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ └── [email protected]
├── [email protected]
├── [email protected]
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ └── [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ └── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├─┬ [email protected]
│ └── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├── [email protected]
└─┬ [email protected]
  ├── [email protected]
  ├── [email protected]
  ├─┬ [email protected]
  │ ├── [email protected]
  │ └── [email protected]
  ├── [email protected]
  └── [email protected]

The Stylus middleware can't deal with multiple paths, nor when the requested url doesn't match the file's path.

We could farm out most of the stuff from stylus.middleware and make our own middleware.

Thoughts?

If there are no Filterable properties then don't show the filter block