catalogues: Allow configuring what fields are scanned for possible keywords

2 votes

Vote

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

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

catalogues: Don't split up codename fields when scanning for words

1 vote

Vote

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

Even if punctuation is used (e.g. "something.else"), a codename field is by definition all one word. So have some way of signalling this when passing codename fields into the meta keyword scanner.

Suggested by Chris Graham on 29th October 2018

core_webstandards: Different colours for different kinds of warning

0 votes

Vote

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

Currently everything is red.

It would be better to properly define a system of different levels: errors, warnings, notices. And each would get a different colour.

Suggested by Chris Graham on 27th October 2018

core_configuration: 'timezone' config option should not be a special snowflake

1 vote

Vote

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

This option is added in like a virtual config option - shown in the config UI, but actually stored in the values table.

I don't think there's any good reason. It's historical. Making it a normal config option would simplify the code a bit.

Suggested by Chris Graham on 21st October 2018

core: Detect user language via geolocation, if set to English

1 vote

Vote

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

If a user has their browser set to English, try and detect their language via geolocation.

This would be optional, and default to off. It is designed for the common situation of user's leaving their browser language setting to the default English.

Suggested by Chris Graham on 15th October 2018

core: Backing-off algorithm for flood control

0 votes

Vote

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

Rather than the flood control just limiting the number of hits per second per IP, have it reduce the allowed rate for an IP over time.

For example, if 10 hits per 10 seconds are allowed, only allow say 40 hits per 60 seconds, and 100 hits per 10 minutes, and so on.

This is to reduce the ability for b…

Suggested by Chris Graham on 14th October 2018

core: Harsher flood control under high load

0 votes

Vote

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

A good webhost can offer DDOS protection against attacks lower in the network stack (good article saying what they do: https://www.quora.com/How-do-DDOS-mitigation-techniques-work-e-g-RioRey). Suspicious activity can be detected relatively easily, and each machine doing it is not impacting that much of a c…

Suggested by Chris Graham on 14th October 2018

core: Enhanced control of dates during validation

0 votes

Vote

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

When you go to some non-validated content, either through the admin_unvalidated module, or an e-mail notification about non-validated content, open up the edit form in a special validation mode.

Instead of a validated checkbox, have a series of radio buttons:
1) Edit but leave non-validated
2) Validat…

Suggested by enelson on 5th October 2018

health_check: Google Webmaster Tools errors

1 vote

Vote

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

Automatically interface with the Google Search Console API, and find any errors on the Composr site that shouldn't be. Ignore things relating to external links, but anything on the sitemap for a sitemap file that still exists should not be returning any kind of error.

Suggested by Chris Graham on 2nd October 2018

health_check: Automatic speed tests

0 votes

Vote

Raised 0% of 144 credits
(144 credits = 24 hours or $995.70)

Do many of the tests of tools referenced in testManualPerformance, automatically.

Suggested by Chris Graham on 2nd October 2018