ida / adi.forumail Goto Github PK

Append a minus to it.

The smallest fractal is a minute, a post created some seconds after another might falsely precede the older one in the results, because then the dates are interpreted to be the same (minute) and the second sorting by ascending titles can lead to the effect, if the newer title is greater than the older.

Currently everything's tight to the location: '[plonesiteId]/forumail'. Be more generic, allow a forum to be added anywhere.

• Extend m2p with an 'IPostMailDropBoxMarker'-interface and add 'adapters/post.py'.
• CT 'Forum' -> Clone of 'Folder', set 'IPostMailDropBoxMarker' on creation via eventlistener.
• CT 'Post' -> Clone of 'Document'.

Trigger a post-creation with the next increasing id
relative to the post answered to, e.g.: '1-1' -> '1-2', or '2-7-3' -> '2-7-4'.

Looks for not anymore existing kukit.js, but that seems to be no harm, so far. If not needed, remove registry of kukit.js.

By id's reply-depth (id, id-1, id-1-1, id-2, id-2-2 ...)

Use JS'ses encodeUriComponent and decodeUriComponent

Change:
"On 08/11/2015 04:22 PM, [email protected] wrote:"
To:
"On 08/11/2015 04:22 PM, Harry Belafonte wrote:"
If no username found, to:
"On 08/11/2015 04:22 PM, hbelafonte wrote:"

When adding a post or replying via UI, the latest info-message (if there was one) will show up, such as:
"Add News Item operation was cancelled" or "Welcome! You are now logged in".
This might be the solving fit and brings even more goodies to configure msgs at your will via the UI:
https://github.com/IMIO/collective.messagesviewlet

If edit triggered of forum-main-view, go back there. If triggered of a post-view, go back there, and include hash in url to the post's headline-link, provided of reply-link, equalizing the reply's path, e.g. '#2-7-7', to land back in context without the need for scrolling.

E.g. '[email protected]', '[email protected]'. Need to be aliases of send-to-address, add tag before pushing mail.

Umlaute will give:

Traceback (innermost last):
Module ZPublisher.Publish, line 138, in publish
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 48, in call_object
Module mailtoplone.base.browser.xmlrpcview, line 57, in drop
Module mailtoplone.base.adapters.blog, line 93, in drop
Module mailtoplone.base.utilities, line 79, in __call__
Module email, line 57, in message_from_string
Module email.parser, line 82, in parsestr
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf6' in position 1346: ordinal not in range(128)

Restrict to available tags.

Currently only done for replies.

If an email-reply contains quots, wrap into a div.
If replied via UI, insert quots in wrapped-div into text-area.

While it e.g. cioppino.twothumbs provides a dis/like-option, it doesn't give information why a person liked something, maybe one does only partially agree with a liked post, that should be expressable somehow, annotating a comment to an up-/downvote.
A possibility could be to implement a second workflow with two transitions 'up-/downvote', including a popup offering the comment-field right next to the trans-button, provided by 'collective.wfcomment', encouraging the user to leave a statement.

Also load add-form via jQinto forum-view. Show categories-field, immediately. Recheck inhibiting to add new categories.

So user doesn' have to use the install-script.

Via assigning a static-text-portlet to 'forumail'.

Might need to set states, too, when pushing URL's to history (!=null).

m2p.base causes on instance-rising:
"zope/configuration/config.py:706: UserWarning: The set_schema option of the directive is not supported in Zope 2."

Concerns

https://github.com/ida/collective.contentrules.mailtogroup --branch forumail

If the site's email_from_address is supposed to be the inbox-address, it cannot be the 'To: '-address, as well, that'll create a circular loop of being notified fo new posts and then immediately pushing, them.
Using a 'Reply-To'-address would solve this, but also require to have two mail-accounts, one for receiving (inbox-address, IMAP) and one for sending (site-from-address, SMTP) :-(

Update:
Inserting a "source"-address via the contentrule's UI/xml works, if the adress has the same domain as the site's sender-address.
Ideally c.c.m2p checks, whether the user set a source-address, and if not, uses the site's address for 'To: '.

Even better would be, if the Plonesite's properties allowed setting a "Reply to"-address, also. But according to https://dev.plone.org/ticket/12413, an open ZOPE-bug will likely not allow that.

We currently only regard reply-links for the forum's main-view, also do that for single thread-views.