core: Enforce correct access protocol (HTTP vs HTTPS)

2 votes

Vote

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

If a base URL / page specifies HTTPS, and you access with HTTP, handle this with a redirect, just like as if you didn't use the correct URL scheme.

Also HTTPS to HTTP, just in case caching creates issues if the wrong protocol is used.

Suggested by Chris Graham on 24th January 2016

core_abstract_interfaces: AFM pre-check

1 vote

Vote

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

A pre-check call for the AFM that can be done before trying to remove addons (or whatever). This allows us to check we have the file-system permissions we need to finish an operation before starting changing other stuff first like DB structure.

Suggested by Chris Graham on 24th February 2016

realtime_rain: Better time-line setting

0 votes

Vote

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

Ability to easily choose what exact time to jump into the timeline at.

Suggested by Chris Graham on 5th March 2016

tickets: Search filter

0 votes

Vote

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

Ability to filter tickets shown by a simple search box.

Suggested by Chris Graham on 22nd March 2016

core: Member daily login hooks

1 vote

Vote

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

Hooks that run for the first time a member logins in on a day.

Suggested by Chris Graham on 23rd March 2016

core_menus: Option to delete automagically generated menu (i.e. to start from scratch as opposed to copying it)

1 vote

Vote

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

Would you like to copy the current automated menus into an editable menu...

My answer to that question is no, I wouldn't like to copy the currently automated menus, I would like to delete them and create the main_menu from scratch.

However, I can either proceed or accept the default. Perhaps the text…

Suggested by KingBast on 15th April 2016

core_configuration: Better control of WYSIWYG editor default status

1 vote

Vote

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

There's an accessibility option to disable WYSIWYG.

Instead it should be possible to select from these 3 different options:

On by default
Off by default
Disabled

Suggested by Chris Graham on 24th April 2016

core_notifications: Implement blinking notifications CSS

1 vote

Vote

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

See http://compo.sr/forum/topicview/browse/designing/make-notification-icons.htm

Suggested by Patrick Schmalstig on 27th April 2016

core: "Did you mean?" for zone suggestion as well as misnamed pages

1 vote

Vote

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

Currently if you access a misnamed page it will suggest the correct name. Have something similar if the module exists, but in a different zone.

Suggested by Chris Graham on 4th May 2016

core: Re-review HTTP status codes wrt IE and IIS

1 vote

Vote

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

We have this line of code limiting when we send out accurate HTTP status codes:

if ((!headers_sent()) && (function_exists('browser_matches')) && (!browser_matches('ie')) && (strpos(cms_srv('SERVER_SOFTWARE'), 'IIS') === false)) {

The reason is that...

1) IE has traditionally replaced our HTTP outp…

Suggested by Chris Graham on 27th April 2016