bitpiston / chowder Goto Github PK

The only time this is relevant is for a home page where we wouldn't want a slug as it should be available at /

Should we make a software licensing module? We will need one for the AppStore perhaps. At work we may need to roll our own and it would fit in good with the cart. Certainly sellable.

We should just have the Chowder modules, styles and other resources in the repository. We can safely assume they work under the latest Oyster (in theory).

Implement some sort of archiving and pruning for old threads.

I already have a cart module that I use at work but its very specific to: 1) PayFlow Pro 2) Our licensing system. We should make a more general purpose cart at some point as I'm sure it will come up in client work.

http://codemirror.net/

http://codemirror.net/demo/closetag.html

http://codemirror.net/demo/folding.html

http://codemirror.net/demo/fullscreen.html

It would certainly add a lot of flexibility having a common post system like WP for content and posts where custom types could even be added for things like creating portfolios and galleries. The fancy admin backend is also something we'd need if anyone other than ourselves was to use this in production probably.

We'd probably also want to implement shortcode to replace oyster directives?

Partly finished awhile back - still needs to print archive XML and put together an administration interface.

Ideal for meta description or alternate titles from url titles.

To support the fancy new WYSIWYG editors that are not just textarea replacements we will need to redesign the content module to work with one. This also allows us to add a lot of neat features like notes and snippets (predefined markup chunks that can be inserted on a page) plus a much better interface for history revisions.

http://jejacks0n.github.com/mercury/

The interface may be an issue if it clashes with any layout CSS.

The challenge I see is that this almost needs two content managers in a sense. One like the current one where the web developer would have complete control of the markup and could define what regions are editable and one where the users edit their content.

Are we going to scrap it entirely? Use the github API to create a github module?

Looks like the requested URL is cached after the first attempt and its throwing a internal error instead of the usual 404. server.pl doesn't replicate this as its always a new fcgi instance so it has to be reproduced using lighttpd.

Executing Function:
:: ()
Perl Error:
Undefined subroutine &main::main:: called at /usr/home/5381/chowder/shared/lib//oyster.pm line 529.
Trace:
File                          Line Subroutine
...r/shared/lib/exceptions.pm 93   (eval) oyster::__ANON__
...r/shared/lib/exceptions.pm 186  (eval) exceptions::throw
...owder/shared/lib/oyster.pm 530  exceptions::try
...r/shared/lib/exceptions.pm 178  (eval) oyster::__ANON__
...owder/shared/lib/oyster.pm 558  exceptions::try
...chowder/shared/oyster.fcgi 33   (eval) oyster::request_handler

Boils down to:

• Add a submodule for Oyster
• Throw everything in chowder's shared directory into _chowder

See: bitpiston/oyster#47

Pretty evil eating my entities and borking trying to encode em dash etc.

Add support for PostgreSQL to the forum module.

See: oyster/trunk/documentation/sql_compatability.xhtml

http://codemirror.net/

Not sure whats going on with the code highlighting but the content is not visible in firefox until you right click and inspect the page.

Anything (X)HTML5 should work as long as it acts as a textarea replacement.

Redactor seems like the best bet as long as it can handle XHTML. Unfortunately its not free.

http://imperavi.com/redactor/

Everything has been completed except the interface to manage history revisions.

Everything is using it instead of prepared queries for stuff thats called a lot. Needs to be replaced with prepared statements.