Upgrade Overall Experience

[technowhizz]

The changes are intended to improve the usability and functionality of the project.

Environment Configuration

• Added env.php to bootstrap/app.php

  Shortener Domains

• Modified LinkHelper.php to add adf.ly to the list of shortener domains

  Redirect Notice

• Modified LinkController.php to enable a redirect notice if enabled in the environment

  Link Ordering

• Modified add_link_table_indexes.php to order links by ID when chunking them

  CSS Styling

• Modified CSS for site URL field and check button in index page

  Input Validation

• Added input validation script for link URL field in index page

  Login Page Message

• Updated login page with message from environment, if enabled

  Admin Link

• Added admin link to navbar dropdown menu on small screens

  I'm not sure if this is the best way to achieve this, but it works.

Looking further into https://github.com/Antelope-Valley-College/polr/issues/9 I found that the useCurrent() function was returning 0000-00-00 00:00:00 instead of CURRENT_TIMESTAMP. The same with useCurrentOnUpdate(). This should hopefully avert this.

Open to other ideas as to why this might be happening but in the meantime this should work

(Messed up the previous PR hence opening this one)

[technowhizz]

From #10

@technowhizz This patch looks great; thank you for your efforts. I have one question about database/migrations/2023_01_24_234401_add_secrets_key_default.php. The code in my repository uses Schema modification commands to remain DB agnostic. I would like to allow for other DBs to be used with POLR in the future. The update I'm seeing is an ALTER statement that only works for MySQL. I don't have much experience with Laravel; this upgrade was a knee-jerk to get to PHP 8. Do you see any technical reason that we could not keep the declarative syntax using Schema?

[technowhizz]

@mwilmes-at-avc I too would love to keep the laravel code to interact with the DB but for some reason it just didnt seem to work. I think others have also faced this issue as noted by @nitz in #9

The issue is also noted at https://github.com/laravel/framework/issues/3602

However it seems like telling laravel that you have a strict db in database.php may fix it. However, this is the default in the repo and hasnt fixed it for me.

[technowhizz]

@mwilmes-at-avc After searching around quite a bit, the code should work but for some reason it just doesn't. As far as I can tell the only way to fix this for now is with the raw SQL. I understand if that means that you no longer want to merge this in as it doesn't permit the use of postgres.

If anyone does manage to fix it do let me know