Page can have a parent, but this is not being displayed in the header/navbar

Add a property that can be configured to show blogwt version number

Cannot hide the icon or the title of the blog from the header.

PageType operations should really be moved into a navigation helper or into the client side page helper.

Should have page title in the header title, something like Site Name - Page Name.

Pages should appear in the header unless they have sub pages in which case the sections (probably the ones marked with a header tag should be shown)

On the post detail page there should be previous and next post links that point to the previous and next published posts if they are available. Probably just hide the links if a previous or next post are not available.

When an post is selected from the archive tree, it might work well to invoke the back to the top button. This might apply across the board i.e. after a post is shown (finished loading) scroll to the top of the page.

On the add/edit post page especially when there is a video or a map the constant flicker is very annoying. Consider adding a pause and refresh button for that.

This has not been mapped yet but will be as simple as getting the salt property if one is defined in the UserService class.

I need to add a contact form to some pages, there does not seem to be a way to do that.

Search does not cover users.

This applies to when there is a priority 0 page and the blog link is now added to the rest of the header pages.

Currently the resource address is added to the description, which is fine, but it makes more sense to add it to the properties

Search does not cover pages (on site search, not search engine search)

It would be ideal to click on the year or month name to expand the tree node, much more comfortable. The triangle is almost impossible to get.

Admins (and user managers) should not be required to enter a user's existing password to assign them a new password.

When login fails errors are displayed on the login page, but navigating away and back does not seem to clear the page.

There seems to be a race between loading the home page and logging out then refreshing the content (without the session) which means that user unpublished content is sometimes shown after the user logs out.

It seams that the tags on the post details page are not being cleared when the page is reloaded

When logged, posts either go blank or come back in a messed up order. This depends on the user and there roles and permissions. It is annoying to find anything when you want to edit it.

When a dynamic page is visited on first load, the page does not seem to come up and all that can be seen is the loader e.g. http://blogwtproject.appspot.com/#!about

This should not really be happening... it should just show the default page or the blog if nothing is configured.

It is probably not a huge issue, but really annoying with the history back button double clicking to get to the actual previous page.

Need some mechanism of hiding private information from the client especially when it relates to user data e.g. email address.

but clicking any link from the header seems work.

This needs an additional field added to the user detail screen and also needs to be displayed at the bottom of the post if the property is enabled.

Blogwt has dependencies on

• gson-gwt already open source (listed for completeness)
• Jasonable parent class
• servlet classes for the API (and the app engine implementation)
• string and json utilities
• service pattern parent classes DONE

There is nothing fancy in any of those and I will get around to making repos for them at some point (soon)

If the property values are updated without any properties changing the update button is stuck in loading mode with the form disabled.

Workaround:
select any other page then go to the properties page

The post permission should be divided into at least

• add -> implies update and delete of own
• delete other
• update other -> implies publish

This seems to be because of an issue parsing strings with \n in them?

Cached objects (mainly user) that are cached by objectify are shared to minimise access to the datastore. When user sensitive information is stripped before a lookup, the lookup returns a user with a stripped email address. This is causing issues with other calls that rely on the data.

Admin users and users with the manage users permission can add a new user but setting the allow users to register permission to true does not have any effect.

Edit:
The register page is always empty even if the link is entered into the address bar.

While pages are loading new content they sometimes display the old content instead of a loading indicator.

This applies to the post detail page and the edit page.

The thumbnails are too small to identify and the meta data displayed is not useful. Need a mechanism to upload images on the resource page and edit the details once that is done.

Consider abandoning the table based layout and using a thumbnail view.

Add google analytics by switching on in properties.

Forms with errors don't show errors on the client side and once server-side validation returns it is not displayed (except occasionally in javascript console).

If there are no archive posts or no related articles... it would be nice to just hide them.