core: Run the PHP codebase through PHP_CodeSniffer beautifier

2 votes

Vote

Raised 0% of 42 credits
(42 credits = 7 hours or $292.62)

Running the beautifier breaks easy merging so we need to take that into consideration. Sometimes reformatted spacing can make code harder to follow but we can fine tune the Code Sniffer config file to deal with that I think.

Attached is the rule set config file following coding standards agreed at https…

Suggested by Salman on 7th September 2018

msn: Support custom fields (catalogue-style fields)

0 votes

Vote

Raised 0% of 60 credits
(60 credits = 10 hours or $418.03)

Allow custom fields to work across MSN.

To do this we need to make most of the catalogues code MSN-aware, which is a lot of complexity.

Suggested by Chris Graham on 28th August 2018

core: Allow main_multi_content block to select by tag

1 vote

Vote

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

Select all content by searching for use of a tag, rather than category.

Suggested by Chris Graham on 5th August 2018

themewizard: Multiple colours in Theme Wizard

1 vote

Vote

Raised 0% of 1,200 credits
(1,200 credits = 200 hours or $8,360.52)

Rather than having a single seed colour in our default theme, have 2 or 3 seed colours.

Suggested by Chris Graham on 5th August 2018

core_feedback_features: AJAXified posting

1 vote

Vote

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

Allow the comments to be posted via AJAX, and then the topic display to update (probably a whole new display would be returned via the AJAX handler). Currently it requires a full page load.

Suggested by Chris Graham on 5th August 2018

core: New symbol to read metadata based on CMA hooks

1 vote

Vote

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

Implement a new symbol that can read out metadata (e.g. title, or thumbnail URL) for any given content type and ID.

This allows catalogue templates to pull in more complex data about resources being referenced.

Make sure it doesn't crash if invalid parameters given, or if there's a failed lookup.…

Suggested by Chris Graham on 5th August 2018

core: Simplified category selection

1 vote

Vote

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

If there is only one category then select it by default in a hidden field, don't even show a category selector.

This will need separately implementing for each CRUD module that has a category selector.

Suggested by Chris Graham on 5th August 2018

core: Breadcrumb takeover

1 vote

Vote

Raised 0% of 24 credits
(24 credits = 4 hours or $167.21)

Composr is a module-orientated CMS, meaning each module (galleries, news, etc) is a world of its own, with its own breadcrumb hierarchy. We want webmasters to be able to more easily override the native module-based breadcrumbs. Currently you need to use breadcrumbs.xml individually for any screen you're ch…

Suggested by Chris Graham on 4th August 2018

core: Disable category selection in content managment modules via URL switch

1 vote

Vote

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

Implement a new 'cat_lockdown' parameter supported by our content management modules.

If you link to say cms:cms_galleries:add:cat=catalogue_images:cat_lockdown=1, then the category selector would be disabled (locked to catalogue_images in this example).

This allows webmasters to create links from th…

Suggested by Chris Graham on 4th August 2018

core_fields: Adapt 'hyperlink' field type to be able to use any media renderer

1 vote

Vote

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

Add and document a new field option, whereby a 'hyperlink' field type can actually render with any media renderer in Composr. Include support for auto-detecting the renderer via a special value.

Example use case:
A catalogue has a hyperlink field set to media_type=youtube. Any URLs in that field would…

Suggested by Chris Graham on 4th August 2018