newsletter: View online support

7 votes

Vote

Raised 0% of 12 credits
(12 credits = 2 hours or $82.48)

Some people have very poor e-mail software and can't read newsletters properly. For these people, provide a link to view via our website. To achieve this
1) move the newsletter archive functionality into site:newsletter from adminzone:admin_newsletter; make sure to check permissions properly.
2) create l…

Suggested by Chris Graham on 5th April 2010

newsletter: Enhanced variable binding

0 votes

Vote

Raised 0% of 6 credits
(6 credits = 1 hour or $41.24)

Allow Tempcode inside a newsletter to operate on the newsletter variables that relate to individual members, including being able to extract custom profile fields and include/manipulate them.

Suggested by Chris Graham on 5th April 2010

core_comcode_pages: Page templates

5 votes

Vote

Raised 0% of 120 credits
(120 credits = 20 hours or $824.85)

Incorporate the idea of "page templates" into the Add-New-Page Wizard.

The objective is to allow a user who is new to marketing, web architecture, and copywriting, to get good-quality standard-format/formula pages quickly onto their site, without having to go on a few courses to really understand all th…

Suggested by Chris Graham on 5th April 2010

core_themeing: Make the zone menu entirely auto-managed

0 votes

Vote

Raised 0% of 6 credits
(6 credits = 1 hour or $41.24)

In order to not create a compatibility-break, we introduced the theme option to allow auto-management of the zone menu rather than forcing it. This is not a good long term solution, it should always be auto-managed.

Suggested by Chris Graham on 5th April 2010

core_menus: Fully support menu stitching

2 votes

Vote

Raised 0% of 18 credits
(18 credits = 3 hours or $123.73)

For example, making a drop-down menu by stitching other menus, or stitching a dynamic menu onto a node of a custom menu.
Currently it's available via hacking a special coding in via the tooltip field.
This was a short-term fudge to avoid changing such a core database structure.

Suggested by Chris Graham on 5th April 2010

core_language_editing: New languages

0 votes

Vote

Raised 0% of 6 credits
(6 credits = 1 hour or $41.24)

When creating new non-ISO languages (e.g. Klingon), it is not currently possible (without hand editing of lang/langs.ini) to set the human-readable name. Make it direct and intuitive.

Suggested by Chris Graham on 5th April 2010

core_language_editing: Option to disable other languages

0 votes

Vote

Raised 0% of 6 credits
(6 credits = 1 hour or $41.24)

Add ability to turn off multi-language mode, if off, the default language will be the one shown. The need for this is because it is annoying to have to select the editing language whenever editing a Comcode page.

Suggested by Chris Graham on 5th April 2010

awards: Display on content screens

0 votes

Vote

Raised 0% of 12 credits
(12 credits = 2 hours or $82.48)

If a content item has been given an award, display it on the content screen. This is probably best achieved via a new block that shows what awards something has been given; it can be deployed in default templates like the main_screen_actions block currently is.

Suggested by Chris Graham on 5th April 2010

core_feedback_features: Invisible comments

0 votes

Vote

Raised 0% of 6 credits
(6 credits = 1 hour or $41.24)

Add parameter to the main_comments block to allow the form to be visible but the comments not to be, except to an Selectcode definition of usergroups. In this mode the block will work as a private feedback system. It must be clear to the user that feedback is hidden from public view.

Suggested by Chris Graham on 5th April 2010

core_feedback_features: AJAX ratings

0 votes

Vote

Raised 0% of 6 credits
(6 credits = 1 hour or $41.24)

Do ratings via AJAX, rather than post-backs.

Suggested by Chris Graham on 5th April 2010