December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3150) Published / Unpublished status on wiki documents

by Per Wiklander (JIRA)

Published / Unpublished status on wiki documents ------------------------------------------------ Key: JBSEAM-3150 URL: http://jira.jboss.com/jira/browse/JBSEAM-3150 Project: Seam Issue Type: Feature Request Components: Wiki Reporter: Per Wiklander Assigned To: Christian Bauer It would be nice to be able to choose if a document is "published" i.e. visible (without using permissions as a workaround). The document could be a work in progress or something that you want to prepare in advance but not release before a certain time. Being able to choose the time the document goes from the unpublished to published state would be even better. This way you can work on a new part of the site and have it published Monday morning 0700 without having to actually be there pushing the button. This shouldn't be too hard (said by someone with about zero knowledge of the wiki code) and I'd be glad to help if the idea is approved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2872) Duplicate command in the directory browser or be able to set creation time to Now

by Max Andersen (JIRA)

Duplicate command in the directory browser or be able to set creation time to Now --------------------------------------------------------------------------------- Key: JBSEAM-2872 URL: http://jira.jboss.com/jira/browse/JBSEAM-2872 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Max Andersen Assigned To: Christian Bauer My problem was that I created 2 blogs A and B and published B first then A later. On the feed it looked correct, but on the front page B was listed before A because the sort is based on creation times. Christian suggested to have a duplicate command... What I would like is a way to either sort based on the first publish time or be able to set the create timestamp to now so I don't have to affect the feeds and risk publishing the same entry twice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2231) Setup wizard for wiki

by Christian Bauer (JIRA)

Setup wizard for wiki --------------------- Key: JBSEAM-2231 URL: http://jira.jboss.com/jira/browse/JBSEAM-2231 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Write a setup wizard that replaces the manual wiki-data.sql editing and import. We should have the following setup procedure: - Get the recommended environment ready (JBoss AS, MySQL) - Deploy the wiki-ddl.sql on a new database - Deploy the wiki.war on the appserver - Open http://server/wiki/ and go through the setup wizard The wizard will first import the minimum dataset (guest/admin users, roles, start page) and then ask the usual setup questions (site base URL, etc.). Depending on the future of the plugin API, it could also optionally allow you to configure some plugin defaults so you don't have to go into the Admin screen to change them after the install. Also, we can offer prepackaged datasets for certain use cases that can be imported with the wizard, e.g. "Help Documents", "Blog Website", "Forum Website". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3872) album plugin

by wu haixing (JIRA)

album plugin ------------ Key: JBSEAM-3872 URL: https://jira.jboss.org/jira/browse/JBSEAM-3872 Project: Seam Issue Type: Feature Request Components: Wiki Reporter: wu haixing Assignee: Christian Bauer There should has directories manage the user's pictures.Besides current WikiDirectory and WikiUploadImage features,the album should accessable by password!So User should maintain the access token to albums in session. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2633) Previous/Next buttons on topic display don't respect new replies

by Christian Bauer (JIRA)

Previous/Next buttons on topic display don't respect new replies ---------------------------------------------------------------- Key: JBSEAM-2633 URL: http://jira.jboss.com/jira/browse/JBSEAM-2633 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer The previous/next links are calculated from lastModifiedOn of documents/topics. If a topic has a new reply, it appears at a different position on the topic list. These are quite complex SQL queries, we might decide to drop these buttons from that view for the time being. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2722) Wiki plugin metadata

by Christian Bauer (JIRA)

Wiki plugin metadata -------------------- Key: JBSEAM-2722 URL: http://jira.jboss.com/jira/browse/JBSEAM-2722 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Blocker Plugins/macros need metadata, some random ideas: protected String[] skins = {"d", "m"} protected long accessLevel = 0; protected boolean documentDiscriminator = false; protected boolean reentrant = true; protected boolean renderedOnce = false; protected boolean affectsRenderingOnly = true; protected boolean appliesToHeader = false; protected boolean appliesToContent = true; protected boolean appliesToFooter = false; protected boolean displayedInPreview = true; createMethodBuildTime createMethodRenderTime -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1852) Implement dynamic privilege system with assignment to roles and users

by Christian Bauer (JIRA)

Implement dynamic privilege system with assignment to roles and users --------------------------------------------------------------------- Key: JBSEAM-1852 URL: http://jira.jboss.com/jira/browse/JBSEAM-1852 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2689) FeedAggregator uses escapeAtSymbol() but should use escapeEmailAddress()

by Christian Bauer (JIRA)

FeedAggregator uses escapeAtSymbol() but should use escapeEmailAddress() ------------------------------------------------------------------------ Key: JBSEAM-2689 URL: http://jira.jboss.com/jira/browse/JBSEAM-2689 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer On the seamframework.org home page we have a feed aggregator that obfuscates the e-mail addresses which show up in the aggregated Fisheye feed. The routine just replaces all @ symbols, which is no good if someone posts a forum topic/reply with for example @In in the subject. We need a new WikiUtil.escapeEmailAddress() method that uses a proper regex to do the obfuscation job. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2410) Editing of comments/forum posts

by Christian Bauer (JIRA)

Editing of comments/forum posts ------------------------------- Key: JBSEAM-2410 URL: http://jira.jboss.com/jira/browse/JBSEAM-2410 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor Users should be able to edit their own comments and forum posts if that is enabled in the system preferences. There is basically only the UI missing for that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3197) RememberMe authentication for wiki

by Christian Bauer (JIRA)

RememberMe authentication for wiki ---------------------------------- Key: JBSEAM-3197 URL: https://jira.jboss.org/jira/browse/JBSEAM-3197 Project: Seam Issue Type: Task Components: WS Reporter: Christian Bauer Assignee: Christian Bauer Persistent cookies for RememberMe automatic logins require significant changes to the wiki: 1. Decouple user profile password changing UI from main profile, require authentication with existing password before entering new password. 2. Decouple user profile email changing UI from main profile, require authentication through regular login, notify user if she is logged in through persistent cookie. 3. (Optional) Require confirmation email procedure after email address change. 4. Add authentication token storage table/entity and implement TokenStore. 5. Implement RememberMe user interface checkbox. 6. Implement configurable expiration policy for cleanup of authentication token table. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009