gmazza / tightblog Goto Github PK

The in-memory DB plugin we use works better when being used for integrated tests.

There are wrapper classes (https://github.com/gmazza/tightblog/tree/trunk/app/src/main/java/org/apache/roller/weblogger/pojos/wrapper) created presumably (?) so that the Velocity templates can read but not write values in the POJOs. See if the real POJOs can be designed such that we no longer need these wrapper classes.

Changes:
user_role table gone, TightBlog now one role per user, stored in the roller_user table.
RollerPermission and ObjectPermission classes gone in favor of top-level WeblogPermission class
New GlobalRole and WeblogRole classes created, TightBlog security based on those roles.

No longer needed.

Roller can add little-needed /de/, /fr/, etc. to the blog entry URL. Evaluate removal of this option.

As well as the rest of the custom Exception classes.

Remove from JPAMediaFileManagerImpl the upgradeFileStorage() used in upgrading from Roller 4 to Roller 5, also remove from its test class and the roller.properties file.

Those not providing much of any useful info, delete them.

http://docs.spring.io/spring-security/site/docs/current/reference/html/csrf.html

In several cases we're creating both an index and a foreign key, the latter should make the former redundant.

Allow the user the option of either but not both.

Use annotations instead of xml config for the jpa stuff.

Use better constructors and DI to reduce usage of this global object.

columns weblogid, weblog_role, and pending need to be made not null.

Technorati, IceRocket failing.

To deploy TightBlog on Tomcat or whatever, you already need to be comfortable with Java, so perhaps users can just build TightBlog after downloading it & running mvn clean install.

For those with global role making them an admin.