* don't run querys if not strictly required (e.g. query for chars from ajax context)
* prepare user globals and favorites so errors can be handled and don't destroy the template
this also allows for profiling of the affected queries
* add keys to items table to speed up querying for recipes in general and user completions in particular
* update TrinityCore components to return new Frontend objects
- SmartAI => Markup
- Conditions => Data Listview
* update template files to accept the new Frontend objects
* redo page render following the logic of:
Response ─┬─> TextResponse ─> TextResponseImpl
└─> TemplateResponse ─> TemplateResponseImpl
* split up giant files, one per response path
* caching becomes a trait, implemented where necessary
* TextResponses (Ajax) can now be cached
* make use of previously defined php classes for js objects
* Tabs, Listview, Tooltip, Announcement, Markup, Book, ...
* \Aowow\Template\PageTemplate is the new class to be cached
* do not discard error messages generated after vars have been sent to template
and store in session for display at a later time
* implement tracking consent management
* move logic out of template into their respective endpoints
* the great unfuckening of user and displayName
* `login` is purely used as login with AUTH_MODE_SELF
* `email` may now also be used to log in (if the system knows it)
* `username` is purely used for display around the site, and lookups from web context
* both must exist because of external logins
a) that may be not unique
b) you may not want to share with the rest of the world
* todo: implement rename ( because of b) )
* detatch from User and Util and move to its own enum class
* added definitions for all locales the 12340 client could in theory have
* this is incompatble with the Intl extension
* version bump and php requirement bump
* convert configuration from list of constants to object
* fixes config changes not applying on cli whithout closing and reopening again
* config variables are no longer embedded in localization text
* improve db error handling
* web view should always result in an user friendly error if the db connection is missing or erronous
* cli use should never fatal if the db connection is erronous. How are you going to fix it, d'uh.
* if some CLISetup script requires a db connection check it individually
* fixed misc issues Intellisense was nice enough to highlight.
* mostly deprecated usage of uninitialized parameters
* class GenericPage still needs a long, hard look and a refactor
* append a filemtime timestamp to js/css files to work around browser caching after update
* shuffle script handling around a bit
* also user pages cant have community content
* also fix breadcrumbs on items page
* a guide is a wrapper around an article providing management tools.
* administration is limited to the review process. Needs to be expanded.
* articles on DB pages are seperate. Editor will be added in the future.
* Entities (Objects, NPCs, ect) can now easily be assigned to a different map to be displayed on by clicking their pip on the map
* Entities with already assigned area (by TrinityCore) that were unable to be matched onto the map are no longer discarded. They'll now show up in appropriate listviews.
* Entities without already assigned area that are also unable to be matched onto the map now get an area assigned as long as the relationship areaId <=> mapId is unique (read instanced areas)
* display and link clientside mails to other types and events
* fixed favorites menu for new types
* fixed sorting column triggered spells in enchantment listview
* some misc cleanups
* added option to 'verbose' concatenate a list of items to class Lang
* added option to strip tags from a string to class Markdown
* fixed several instances of wrong categories on pages
* actually display world state conditions for zone music
* some typos all over the place
* vastly improved input validation
* content and type validation occurs when filter is created
* contextual filters like itemTypes are now only applied in context
* fixed file generators involving ?_icons table
* known spells onspell detail page should have a localized tooltip
* fixed numer formating in spell tooltips for locales with a ',' as decimal
* fixed php-tag in contribute template, causing parse error
