catalogues: Do-next shortcuts to edit referenced entries

1 vote

Vote

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

Make it so that you can set up catalogues A and B, such that A has a reference into B, and when you add/edit an entry to A you get do-next icons for editing any already-set dependent records based on the reference field value of the entry you were just working with.

For example, let's imagine catalogue…

Suggested by Chris Graham on 29th January 2020

catalogues: Do-next shortcut to add referencing entries

1 vote

Vote

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

Make it so that you can set up catalogues A and B, such that A has a reference into B, and when you added/edited an entry to B you get do-next icons for adding in dependent records.

For example, let's imagine catalogue A is song and catalogue B is artist. When you added an artist you would get a do-next…

Suggested by Chris Graham on 29th January 2020

catalogues: Ability to create sub-records (one-to-one case)

1 vote

Vote

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

Make it so that you can set up catalogues A and B, such that A has a reference into B, and when you add a new entry to B you can create entries for catalogue A in-form via an XML syntax, and those entries would be set to reference the new entry for B when created.

Allow it to work on edit also, with XML…

Suggested by Chris Graham on 29th January 2020

catalogues: Improve "Auto-fill with categories" feature

1 vote

Vote

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

When you add a catalogue you can specify to pre-create a lot of categories.

This is nice, but could use some work...

1) It would be better to have a text input area and have new lines as delimiters rather than "|" symbols.
2) It would be good to be able to see what exists on another catalogue so you…

Suggested by Chris Graham on 29th January 2020

core_fields: Alternate input methods for reference fields

1 vote

Vote

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

Reference fields allow input via tree-list selection. This may be cumbersome for some sites, especially relationship-heavy catalogue structures.

Via field-options, provide the option to instead allow input via a <select> (with select2 support so you can type and have it auto-complete by substring).

A…

Suggested by Chris Graham on 29th January 2020

core: Logging framework

1 vote

Vote

Raised 0% of 36 credits
(36 credits = 6 hours or $243.87)

Rather than just logging to text files, make it configure on a per-log basis if logs should go to syslog. A sysadmin can then have the syslog be rsyslog, configured to send to a central network location.

This is useful when hosting across multiple servers, not having to chase down logs on individual mac…

Suggested by Chris Graham on 26th January 2020

core: SERVE_LOCALLY symbol

1 vote

Vote

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

Add a new Tempcode symbol, SERVE_LOCALLY. The purpose is a way to copy remote URLs locally using Tempcode, and serve them locally (maybe for speed, maybe to avoid hammering someone else's server, maybe as an automatic backup). You pass it a URL and the first time it runs it copies that URL to a local file…

Suggested by Chris Graham on 9th January 2020

core: Re-review all indexes

0 votes

Vote

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

Review all indexes in the system...

1) Is each necessary? Document why with a code comment. If not, remove (as indexes use disk space and slow writes).
2) Is *sorting* covered on a single index. For example, ideally an index on a category ID will also have a secondary index column on the timestamp, so…

Suggested by Chris Graham on 19th November 2019

core: Cache warm up via Cron

1 vote

Vote

Raised 0% of 180 credits
(180 credits = 30 hours or $1,219.33)

Initial installs may seem slow because initial caches are not populated.
Additionally, future use may seem slow if some resource is accessed but the cache is expired.

These caches could easily be populated in the background (in this priority order):
- Language file cache
- Template cache
- Comcod…

Suggested by Chris Graham on 19th November 2019

core: Opportunistic scheduler

0 votes

Vote

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

Some background Cron hooks are not very time critical, but may have a performance impact. Ideally we would run these hooks only when the server is under low load.

Code in a detector function to find if the server is under 'low load', based on I/O load, CPU usage (uptime command on Linux), and memory usa…

Suggested by Chris Graham on 19th November 2019