{5} Assigned, Active Tickets by Owner (Full Description) (18 matches)

For richer and more scalable web service we need support for message queuing. https://www.dropr.org/ might be a good place to look into.

A generic message queue system would replace application specific queues like MidCOM 8.09 replicator.

Some usage examples: http://www.slideshare.net/carsonified/dopplr-its-made-of-messages-matt-biddulph-presentation?type=document

It would be nice to have threads merged based on subject too. We see mails, which are obvious replies, show up as separate threads. For example:

#
Re: identi.ca group
0 replies, latest post by Matt Emson on 02/18/09 13:19:34
#
Re: identi.ca group
0 replies, latest post by Matt Emson on 02/18/09 11:36:59
#
identi.ca group
0 replies, latest post by Keywan Najafi Tonekaboni on 02/17/09 19:12:09

It would be really nice to be able to filter default mail footers from messages in n.n.discussion.

Example here: http://maemo.org/community/maemo-developers/handling_feature_requests/

There are many places in MidCOM where the deprecated ereg PHP functions are used. They must be replaced with PCRE instead.

If I have a large float value like 2900000, it is displayed f.x. in DM2 edit forms as 2,9E+6. If I try to save the edit form, I get the error "This is no valid number.".

For easier handling, it would be better if midgard core could ensure that all floats are in normal decimal notation when passing them to the php object

Midgard has a feature where the "name" field is checked for uniqueness, so for example there can't be two articles named "news_item" under same topic.

However, this check does not check for multiple possible child types, which can lead into problems with get_by_path and MidCOM components.

For example, under same topic can now be article named "news_item" and topic named "news_item", which is obviously wrong.

Schema for url-name

            'name' => Array
            (
                // COMPONENT-REQUIRED
                'title'   => 'url name',
                'storage' => 'name',
                'type'    => 'urlname',
                'write_privilege' => array('privilege' => 'midgard:update'),
                'type_config' => array
                (
                    'allow_catenate' => true,
                ),
                'widget'  => 'text',
                'default' => date('Y-m-d'),
            ),

Composite-items has only ajax-editing and because of that, you can create composite-items, that has only one br as an content (goes through validation), but you can't delete the item, because you can't doulble click the br-element.

So, if you create empty composite item, you can't delete it

When someone looks at this, at the same time it would be great to have cancel-button when creating new composite item

It would be useful to have a generic chart drawing component for Midgard.