physics515 / hivefive.life Goto Github PK

Remove forum border as shown below.

Menu items are yellow text on white background and cannot be read.

Warning: include(C:/xampp/htdocs/.nosync/.hush/dimwit.php): failed to open stream: No such file or directory in C:\xampp\htdocs\hi\poll\poll-simple\tpl.result.inc.php on line 4

Warning: include(): Failed opening 'C:/xampp/htdocs/.nosync/.hush/dimwit.php' for inclusion (include_path='C:\xampp\php\PEAR') in C:\xampp\htdocs\hi\poll\poll-simple\tpl.result.inc.php on line 4

Notice: Undefined variable: secret in C:\xampp\htdocs\hi\poll\poll-simple\tpl.result.inc.php on line 16

Warning: Invalid argument supplied for foreach() in C:\xampp\htdocs\hi\poll\poll-simple\tpl.result.inc.php on line 27

Notice: Undefined variable: secret in C:\xampp\htdocs\hi\poll\poll-simple\tpl.result.inc.php on line 35

This should match the look of the rest of the site. The "Search Settings" button should be removed and the "Hourglass" should be replaced with a button that matched the style throughout the site.

Style the coinhive captcha to fit the site style.

Guidelines for headers, footers, cmd-outputs, etc.

Create custom Coinhive front-end for the main site. Replacing the current miner.

Replace all instances of this:

With this:

Forum header should be locked to the top of the page, have a 1px "Turbo" #FFC920 border on bottom and have a 80px height.

Board nav should be moved on the same line as "ACP" and "MCP" and any other space compressions should take place to make the header fit into the 80px form-factor.

Forum should stretch to 100% width even on very large screens.

These check-boxes should be squares with a 1px "Turbo" #FFC920 border and a "Black Magic" #362A0B background.

See below for prominent instances on the forum index page.

Remove weird progress cursor function when loading poll results and replace with standard progress cursor.

Format the results page to fit within page on mobile. Poll label widths are hard coded and should respond to screen size.

The Command Prompt on each page show have a better solution for overflow. Perhaps scrolling text or display a single line at a time?

"Topic" and "Post" vertical separators should extend full height of give area. See "Last Post" separator.

Create and explain roadmap for the future with clearly defined goals.

Remove the below section from the forum index page:

See below for prominent example on the forum index:

Currently the project logs IP addresses in a unencrypted .txt file on the server. In the Beta version this should be stored and verified as hashes and no IP addresses should be logged for the poll.

@sick115 should restore from his backup the formatting changes from his work on the forum.

See bellow for several notable instances on the forum index page:

There should be a discussion about how we implement the forum into the site. Should we take the approach of implementing an Ajax solution and bringing in only the elements that we want. Or for the sake of ease and time should we continue on the current path of removing and re-theming the stock phpBB forum.

I believe the Ajax approach is the optimally desired rout, and what I would like to see in the end final product but I also feel that as we are pressed for time that we should focus on producing a minimally viable product. This discussion should take place before we should proceed with modifying the forum theme.

Please comment here with your thoughts.

See below for referred section:

Remove below text from forum footer:

Replace with "Copyright © 2017-2018 hiveFive.life".

The forum footer should be docked to the bottom of the page, similar to the "Vote!" button on the main-site. This should be separated by a 1px top-border above the footer (#FFC90D).

See below for reference:

See below for notable instances on the forum index page:

Also remove the page break underneath them. This is unnecessary clutter.

See below for prominent example on the forum index page:

As of now there is not proper token verification. If we continue with the current implementation then there is a chance that a spam attack could occur if the spammer could fake the hashes mined. See coinhive documentation for instructions on how this should be implemented:

Coinhive Captcha Documentation