kent55 / rafflingsystem Goto Github PK

A discussion forum for members. Fully configurable via the adminCP.

Currently, the link to delete your current avatar doesn't have any token. I need to add this. Most likely by making the link a button and submitting it as a form.

This is the design that @Wild1145 and @WickedGamingUK did. I need to add this, currently it's only the panel for when the user's are logged in.

Also, I personally feel that once the user is logged in, only allow them to see the panel, and in order to go back to the public area, hence the "public/en_gb", they need to logout. This could help with security as although it will most likely be over SSL, not having to access the session superglobal means zero chance of session hijacking from the public area, i.e. affecting a logged in user. What do you guys think? @WickedGamingUK @Wild1145

Currently sayS JPG and PNG supported. Only JPG is currently supported though 🌴

Allow users to select their desired filter.

I need to do this, currently it's just functions as I wanted to make it work, and I had the code from a previous project.

Currently, the avatar directory has no form of protection, I need to add this.

Well, I lie, it has some but only direct access and protection for executables. Although the system only allows for .jpg uploads, we never no.

Currently it's:

Closed today: red
Closed tomorrow: orange
Closed 2 days or later: green

This is more based off of what people think. @Wild1145 @WickedGamingUK?

This will be implemented...

Currently, we're establishing a database connection in every method, and this isn't as performance friendly as it could be. I would like to improve on this, maybe by storing the connection in a static class variable. It can wait though.

Currently, all account modification links via the user dropdown redirect to a separate page. I want to make these JS modals.

When a user doesn't exist, this warning is thrown:
Warning: array_walk_recursive() expects parameter 1 to be array, boolean given.

A simple suppression should suffice, although it definitely can be fixed but just suppress for now.

Currently, although the raffle system is incomplete and is also in a very early pre-alpha stage, as there has been no official unit and other tests since the initial MVC design was built, there is no caching.

On localhost, with just me, there is no real performance problems, the slowest pages being login and the raffle listing. The worst is probably the raffle listing since it has to perform 2 queries. One to get the raffles >= CURDATE() and also one to insert the colour of each returned record. With high traffic this is going to become a complete bitch regarding performance. A cache here could work, maybe recheck for new raffles every hour. I could store them in a JSON or XML format. Either could work really.

I am going to mark this as "It can wait" as although it's a good thing to have, it's not utterly important in the grand scheme of things at this current stage.

Add pagination otherwise it's gonna get messy...

Add 3 attempts to any user trying to login, regardless of the account existing, we can store it in a cookie.

I will first off need to implement scheduled tasks or Cronjobs, really it depends on site visits. If there are enough then all tasks will be executed otherwise they won't.

Personally to make it easier to manage with the fact that the system is hosted on their system the amount of unorganized cronjobs would be ridiculous, hence why personally I feel that scheduled tasks would be better, and more sustainable option. The only exception being, tasks are only executed upon a site visit. However with a system such as this, I don't see site visits being a problem.

I would love to hear what you think @Wild1145 @WickedGamingUK. I'm thinking of the future and making a more sustainable application.

Going back to the issue title, this would then allow the ability to archive the raffles.

This I need to do, it's like half done and it's probably best to get the usergroups implemented and working before continuing with the admin area and other user options.

Yep, this needs fixing.

If no ID is specified, this happens:

Warning: Missing argument 1 for RaffleController::enterRaffle(), called in C:\xampp\htdocs\SwindonTown\application\core\Application.php on line 47 and defined in C:\xampp\htdocs\SwindonTown\application\controller\RaffleController.php on line 44

Need to fix.