core: Defaults for most required fields (idea staging issue)

0 votes

Vote

Raised 0% of 48 credits
(48 credits = 8 hours or $333.96)

I just skim-read an interesting article about how required fields should be considered bad:
https://prismic.io/blog/required-fields

It's a polemic, but it makes you think some unchecked assumptions.

For example, on a news article, should the title really be manually entered for every article you pos…

Suggested by Chris Graham on 12th November 2018

core: FILE_EXISTS symbol

0 votes

Vote

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

Create and document a FILE_EXISTS symbol. This may be useful to templators who may embed procedurally-named graphics present on the filesystem, iff they exist.

Suggested by Chris Graham on 9th November 2018

core_forum_drivers: Split "Strongly tie content to the forum" option into 2

1 vote

Vote

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

Currently this option does 2 things:
1) Auto-creates empty comment topics
2) Redirects to view the comment topic standalone when you post a comment

These can be logically separated into 2 different options.

Suggested by Chris Graham on 8th November 2018

core: Special-forum segregation by language

1 vote

Vote

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

Create some hidden options for overriding forum options on a per language base.

comments_forum_name_<langcode>
main_forum_name_<langcode>
intro_forum_id_<langcode>

This will avoid topics for different languages getting automatically crowded together by Composr.

Suggested by Chris Graham on 8th November 2018

core: Review what Comcode or block attributes should support nested Comcode

1 vote

Vote

Raised 0% of 48 credits
(48 credits = 8 hours or $333.96)

Make a list of all the Comcode or block attributes that take plain text.

Decide which of these should support Comcode.

Particularly it would be nice for block 'title' attributes to support Comcode.

Then implement it.

Suggested by Chris Graham on 8th November 2018

core: Consistent Comcode support on content titles and descriptions

1 vote

Vote

Raised 0% of 132 credits
(132 credits = 22 hours or $918.39)

Currently only a few content types support Comcode for titles...

news.title
galleries.fullname
calendar_events.e_title
calendar_types.t_title
iotds.i_title

Almost all content types support Comcode for descriptions.

Support it more consistently. This will allow people to:
1) use Comcode effect…

Suggested by Chris Graham on 8th November 2018

core_language_editing: Easy/Automated marking as not needing translation

1 vote

Vote

Raised 0% of 30 credits
(30 credits = 5 hours or $208.73)

When going through the translation queue you'll find stuff that does not need translating.

Some of this stuff can be auto-detected. These could be automatically copied across translations at content add/save.
Examples:
1) {!EXAMPLE} [language string references are inherently multi-lingual]
2) 12345 […

Suggested by Chris Graham on 6th November 2018

core_language_editing: Smarter DB sorting for multi-lang sites

2 votes

Vote

Raised 0% of 48 credits
(48 credits = 8 hours or $333.96)

Sorting order is undefined for sites with partial content translations.

Imagine a site with these entries...
1) German=Foo,English=Foo
2) German=Hallo,English=Hello
3) German=Zehr,English=Very
4) German=(untranslated),English=Something
5) German=Uber,English=(untranslated)

Viewing in German you'…

Suggested by Chris Graham on 6th November 2018

core: Close tooltips by clicking anywhere

1 vote

Vote

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

Composr supports tooltips that are activated with a click.
You click again to close them.

However, some users may try and click elsewhere to close them. Support this.

We just need the equivalent of onclick="clear_out_tooltips();" on body.

Suggested by Chris Graham on 30th October 2018

catalogues: Allow configuring what fields are scanned for possible keywords

2 votes

Vote

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

Currently all fields are scanned for meta keywords.

Add a field option to specify whether any particular field should be scanned for meta keywords.

Suggested by Chris Graham on 30th October 2018