there was a reference to storing descriptions in the database that no
longer has a corresponding table since it was changed
just commenting it out for now because it will be implemented again at a
later date
changed the the way files are uploaded to go into their own directory
called 'references' organized by location, identified by uuid. the
'references' directory was added to git ignore to those images are not
saved in the repo, since every install will have their own set of images
also updated reference links to be shown on the front end if they have
been added to a location
unnecessary links where moved from the admin member template since they
have been incorporated into the appropriate area.
a template for editing member account information has also been added.
The plumbing for editing location info has been updated, so that data
can be changed by authorized memebers. Also added a new data point for
locations to store archive links
part 2 will focus on setting up permissions and authorizations as well
as smoothing out adding new members and member roles. an edit link will
be added to locations, which will be visible for members with the
correct permissions
changed the function that retrieves a single location to decide what to
get based on the variable type, so it doesn't need to be two seperate
functions
The Location Controller was getting too heavy so an Update and
Maintenance service class was created to offload most of it's
functionality. Location upating was moved to LocationRepository
There was also a small issue with responsive list links not adapting
properly in Safari that was fixed
Adding total actions count to location data has made it possible to
simplify backend data queries, so the custom pagination was optimized
and location repositories have been cleaned up.
the front end controller has been cleaned up as well, which has resulted
in the appropriate template being polished up as well.
Seperated data logic for locations and put it into its own repository
class for better organization and readability of controller classes.
Data methods are still simple so no need for an interface class just
yet, but will probably implement at a later date
