aboutsummaryrefslogtreecommitdiffstats
path: root/template/standard/html/user/main.php
AgeCommit message (Collapse)AuthorFilesLines
2019-04-26Remove template names from header comment blocksThomas Lange1-1/+1
2017-09-02Bugfix: An undefined array index "NAME" was used in the user navigation ↵v2.3.1Thomas Lange1-2/+2
instead of the existing index "FULLNAME". This problem has existed since the first initial commit and was only present when more than one user had existed (it did not have affected the functionality of the navigation itself).
2017-09-02Multiple <section> elements were replaced by simple <div> elements. If a ↵Thomas Lange1-2/+2
container element is only used for the CSS and has no semantic meaning, then a <section> element is definitely wrong for this purpose.
2017-08-11Several changes have been made in this commit, which together with the ↵v2.3Thomas Lange1-1/+1
previous commits result in version 2.3: + Optimization: Originally, the core and template languages were completely separated in the logic of the Language class and you had to use "$Language->text()" to get a core language string and "$Language->template()" to get a template language string. Since this commit, the core and template language strings are still located in different files, but you now have to use "$Language->text()" for core and template language strings both. Thus, you can now even overwrite a core language string from the language file of a template if the core language string does not satisfy you. + Deprecated: The method "$Language->template()" was marked as deprecated and will be removed in further versions (currently, it's just an alias for "$Language->text()"). Template upgrade to version 2.3 (only for customized templates): SEARCH: $Language->template REPLACE: $Language->text
2017-05-05A significant increase in the response time has been achieved, since the ↵v2.1Thomas Lange1-1/+1
template parameters "$ITEM['BODY']['TEXT']" and "$ITEM['BODY']['HTML']" are now no longer strings but closures (anonymous functions). This means that the underlying logic, which parses the content or converts it into Markdown, is not executed until one of these parameters is really needed and called in the template (which maybe significantly increases the response time on a long list of items which not use one of those two parameters). This means that within templates you now have to call these parameters in the following way (note the brackets at the end, which represent a function call): <?=$ITEM['BODY']['TEXT']()?> <?=$ITEM['BODY']['HTML']()?> In the background, the anonymous functions are called and executes $Item->getBody() and $Item->getHTML() only when needed. Previously, $Item->getBody() and $Item->getHTML() were basically executed and the parsed content was passed to the template, regardless of whether these parameters are required in the template or not!
2017-03-20The javascript part was outsourced to a new file to reduce duplicate code.Thomas Lange1-15/+3
2017-02-26Spelling mistakes corrected, comments added and unnecessary language ↵Thomas Lange1-2/+2
variables removed.
2017-02-24Initial commit.v1.0Thomas Lange1-0/+43