missing features and some bugs

I'm listing some features that I specially miss and also some bugs while trying out 1.1rc1. Some were present in 1.0 and some I just miss when comparing to Plone.

- Missing option to enable use Tiny(?) text editor (why not make it default?)
- Missing option to enable date/time extjs widget (why not make it default?)
- Can't copy/move content
- Upcomming events portlet display past events
- Clicking on month of calendar does no show me events of that month (even though upcomming events show me the event), url model - http://localhost:8080/events.html?year=2009&month=7
- Workflow support (i've seen there is something in dev setup)
- Don't see how to enable "Join portal" link
- When adding a group I get

2009-11-28T16:37:25 ERROR SiteError http://localhost:8080/groups/+/content.group/index.html/
Traceback (most recent call last):
  File "/home/gustavo/.buildout/eggs/zope.publisher-3.4.6-py2.5.egg/zope/publisher/publish.py", line 138, in publish
    publication.afterCall(request, obj)
  File "/home/gustavo/.buildout/eggs/z3ext.cacheheaders-1.2.0-py2.5.egg/z3ext/cacheheaders/publication.py", line 72, in afterCall
    return super(BrowserPublication, self).afterCall(request, ob)
  File "/home/gustavo/.buildout/eggs/zope.app.publication-3.5.0-py2.5.egg/zope/app/publication/browser.py", line 78, in afterCall
    super(BrowserPublication, self).afterCall(request, ob)
  File "/home/gustavo/.buildout/eggs/z3ext.cacheheaders-1.2.0-py2.5.egg/z3ext/cacheheaders/publication.py", line 109, in afterCall
    txn.commit()
  File "/home/gustavo/.buildout/eggs/transaction-1.0.0-py2.5.egg/transaction/_transaction.py", line 322, in commit
    self._commitResources()
  File "/home/gustavo/.buildout/eggs/transaction-1.0.0-py2.5.egg/transaction/_transaction.py", line 416, in _commitResources
    rm.commit(self)
  File "/home/gustavo/.buildout/eggs/ZODB3-3.9.3-py2.5-linux-i686.egg/ZODB/Connection.py", line 554, in commit
    self._commit(transaction)
  File "/home/gustavo/.buildout/eggs/ZODB3-3.9.3-py2.5-linux-i686.egg/ZODB/Connection.py", line 602, in _commit
    self._store_objects(ObjectWriter(obj), transaction)
  File "/home/gustavo/.buildout/eggs/ZODB3-3.9.3-py2.5-linux-i686.egg/ZODB/Connection.py", line 642, in _store_objects
    repr(self._storage))
Unsupported: Storing Blobs in <ZODB.FileStorage.FileStorage.FileStorage object at 0xb3a3b6c> is not supported.

- Security "tab" of a content only gives me the option to assign a permission to a user, not a group.

​We are willing to implement the ability to assign permissions/roles of a object/content to a group. And for that I would appreciate some pointers

1. Is something like this already planned?
2. If not, is it desirable? (would it be accepted upstream)
3. I noticed that the place do to this is "z3ext.content.permissions" module. Anywhere else I should look at?

Perhaps it would be even nicer if instead of assigning specific permissions assign roles.

So a new "Content roles" section (Inside Security "tab" of content) below "Content permissions", would have something like this (it would only appear if groups workspace was available):

                             Group1,    Group2,  Group3
Role 1                        X                      
Role 2                                       X                      
etc...


Looks good?

Any news about the other topics raised?


Thanks

I'll continue updating here until someone has sometime to answer...

I noticed that revision 8729 "remove unused code; update tests" apparently removed some of the support I mentioned above... There was a "sharing" pagelet that allowed the type of fine grained permission I mentioned. Any reason for removal?

Thanks

1) TinyMCE widget is not work properly. And i'm not sure about js based editor in base setup.

2) You can copy content only from one workspace to other workspace of same type.

3) I'll gladly accept patches related calendar/events :)

4) We use workflow only for project tasks, i don't see reasons to use it in other part of system. You can use workflow for your content types

5) To enable 'Join' check 'System settings' -> 'Principal management' -> 'Portal registration'

6) get new 'z3extproject' to fix blob problem

7) Groups roles code should have unit tests

8) We changed how setup local permission, that's why there is no need for custom permission settings

Thanks

Regarding 8, can you elaborate a bit more? how different is it?
Would this new way of doing things related to a entry like:

    <z3ext:contentpermission
     permission="tp4.SubmitSystem"
     managepermission="z3ext.ManageContentPermission"
     for="z3ext.content.space.interfaces.IContentSpace"
     category="z3ext.content.permissions.interfaces.ISubmitPermission" />

I tried this and it worked as expected. Permission shows up in "space" permission pagelet

Ok, I guess now it makes more sense

Doing something like zcml entry below (plus some other zcml directives to "declare" ISystemPermissions) worked well. The space that has the System workspace shows a specific "System permission" categories with the related permissions.

     <z3ext:contentpermission
       permission="tp4.AddSystem"
       for="z3ext.content.space.interfaces.ISpace"
       workspace="systems"
       managepermission="z3ext.ManageContentPermission"
       class="z3ext.content.space.permission.SpacePermission"
       category=".interfaces.ISystemPermissions"
       provides="z3ext.content.space.interfaces.ISpacePermission" />

Looks like things might be simpler then expected. It would suffice to add groups in the column next to users for the current requirement. To fulfill this, z3ext.groups needs to regain "principal" status that apparently was lost when moving from z3ext.principal.groups.

z3ext.principal.field.utils.searchPrincipals searches on "principalType" which I assume search for types names with the "principal." prefix. Group is named as "content.group".

How to proceed in this case? I could just hack searchPrincipals but marking content.group as a "principalType" as well seems like the best option...

problem with groups that they are not real IPrincipal from zope.security, so you can't get group by id by IAuthentication.getPrincipal(). So maybe you need make real IAuthenticator plugin for groups

What do you suggest then?
Merge z3ext.principal.groups into z3ext.groups? What was the motivation of removing the principal nature in the first place?

i didn't like design of z3ext.principal.groups, i suggest just develop authenticator plugin for new code. and if you will do this create branch in package svn