aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2021-06-12Place message boxes outside the <form> elementsThomas Lange7-53/+62
2021-06-12Remove function "getRandomValue"Thomas Lange2-8/+1
This commit removes the "getRandomValue" function. In addition, the Application class now calls PHPs "random_bytes" function directly.
2021-06-12Show first image from items contentThomas Lange6-9/+40
If a item has at least one Markdown image embedded in its content, show this image within the <blockquote> tag in the item.php template files.
2021-06-12Use SCSS for stylesheetsThomas Lange15-1083/+2536
2021-05-25Change header icon link in admin themeThomas Lange1-1/+3
This commit changes the URL of the icon link in the admin theme. The link now leads to the blogs home page instead of the admin dashboard.
2021-05-20Update Parsedown library to version 1.7.4v2.4.3Thomas Lange1-5/+38
This commit updates the Parsedown library to version 1.7.4. The patch to prevent tab indentations in code blocks from being converted to spaces is already applied here. See: 78c5974cd34559d0130d8be509935e2c992cd9ca
2021-05-20Update readme.mdThomas Lange1-3/+0
2020-12-31Remove PHP closing tags and add LF in "core/namespace/User/*"Thomas Lange4-4/+0
In addition to the last commit, remove the unnecessary PHP closing tags from the end of the files and ensure that the files ending with an LF character.
2019-10-29Remove PHP closing tags and add LF to text filesThomas Lange99-99/+40
Remove the unnecessary PHP closing tags and ensure that *all* text files ending with a LF character.
2019-10-16Use strftime() with locale supportThomas Lange2-29/+6
This commit changes the parseDatetime() function to use strftime() with locale support to replace the day-and-month name related parts within the format string. The strftime() function uses the locale defined by the LC_TIME or LC_ALL environment variable which can be set with PHPs own setlocale() function within the configuration.php.
2019-07-27Add notice to readme.mdThomas Lange1-0/+3
2019-07-03Add references to the documentationThomas Lange1-2/+5
2019-05-05Update CSS layoutThomas Lange2-26/+36
2019-04-27Add missing indentationThomas Lange1-6/+6
2019-04-27Remove if condition with empty bodyThomas Lange1-2/+1
2019-04-26Remove "box-sizing" property with invalid valueThomas Lange1-2/+0
The "box-sizing" property can only have two values: "content-box" (default) or "border-box" (the "padding-box" value has been removed from the specification a long time ago).
2019-04-26Replace term "template" with "theme"Thomas Lange2-3/+3
2019-04-26Rename "template" directory to "theme"Thomas Lange69-5/+5
This commit renames the "template" directory to "theme" because "theme" is the more correct term here.
2019-04-26Rename "standard" template to "default"Thomas Lange31-3/+3
2019-04-26Remove template names from header comment blocksThomas Lange21-21/+21
2019-04-26Update readme.mdThomas Lange1-1/+1
2019-01-25Reformat the entire CSS codeThomas Lange2-277/+1315
2019-01-21Close CSS comment blocks correctlyThomas Lange2-156/+156
2018-09-20Update style of emoticon selectionThomas Lange1-3/+2
2018-09-10Remove background imageThomas Lange2-1/+1
2018-09-09Correct regex replace stringsThomas Lange1-2/+2
2018-09-09Use function "parseUnicodeEmoticons"Thomas Lange1-0/+1
We will now use this function (in addition to "parseEmoticons") to parse already UTF-8 encoded unicode emoticons (instead of the ASCII emoticons for which "parseEmoticons" is responsible) from the markdown content.
2018-09-09Add function "parseUnicodeEmoticons"Thomas Lange1-0/+14
This function wraps all the UTF-8 encoded emoticons (from "getUnicodeEmoticons") found in $string into a "span" element with a "title" attribute, which will contain the emoticon explanation text.
2018-09-09Use function "getUnicodeEmoticons" in form templatesThomas Lange3-6/+6
2018-09-09Update example postThomas Lange1-1/+1
2018-09-09Add function "getUnicodeEmoticons"Thomas Lange1-0/+24
This function returns an associative array with the UTF-8 encoded emoticon character as key and the corresponding explanation text as value.
2018-05-20Remove margin-bottom from paragraph in item excerptsThomas Lange1-0/+1
2018-05-18Remove square brackets from form placeholdersThomas Lange3-10/+10
2018-05-15Fix javascript problem that causes unintended behaviorThomas Lange2-2/+2
If you browse in a browser tab through some websites and want to go back to the previous page, post or user, you can either click the history back button, press the corresponding key on your mouse or even press <alt>+<arrow-left> on your keyboard. But if you only press <arrow-left> on a page, post or user, the callback function of the "keyup" event will change the location in the desired direction on the blog if there is a previous page, post or user, and if neither <ctrl> nor <shift> is pressed. This is a functionality of the javascript from the template and not a functionality of your browser. Pressing <alt>+<arrow-left> IS a functionality of the browser and should not conflict with the behavior when <arrow-left> is pressed alone. This commit fixes this problem by adding the condition that <alt> should not be pressed either.
2018-05-15Rename function parameter "event" to "e"Thomas Lange1-4/+4
2018-03-29Update Parsedown library to version 1.7.1v2.4.2Thomas Lange2-24/+195
This commit updates the Parsedown library to the latest version 1.7.1. The patch to prevent that tab indentations in code blocks are being converted to spaces (see 78c5974cd34559d0130d8be509935e2c992cd9ca) is already applied here. In addition, the patch file itself is now shipped within the same directory where the Parsedown.php resides.
2018-02-24Make some minor changes to the contentThomas Lange1-5/+4
2018-02-14Add configuration option "$ITEM.SINGLE_REDIRECT"Thomas Lange4-3/+36
Each option can be set to "TRUE" or "FALSE" (the default value is "FALSE"). For example, if you only have one user and "USER.SINGLE_REDIRECT" is set to "TRUE", then requests to "/user/" will be automatically redirected to "/user/username/".
2018-01-09Fix spelling mistake in commentsThomas Lange1-2/+2
2018-01-08Bugfix: Incorrect behavior of the "truncate" function in some circumstances:Thomas Lange1-2/+5
If the first word from $string was longer than $length characters, then the regular expression had not truncated the string at all (for example, a string with a total length of 2000 characters was displayed without any cut, but with the $replace string at the end). This bug has been reported by Markus Hackspacher (https://github.com/MarkusHackspacher).
2017-11-29The "cut" function has been optimized and renamed to "truncate". In ↵Thomas Lange1-7/+8
addition, the $replace parameter is now an empty string by default.
2017-11-28Bugfix: The "excerpt" function had returned a string with unnecessary ↵Thomas Lange1-2/+3
whitespace between the truncated text and the $replace string ("[…]") if the truncated text from the regular expression had contained whitespace at the end (before it was concatenated with $replace). This issue has been fixed by passing the truncated text directly after truncation to the "trim" function (before the truncated text is concatenated with $replace). In addition, the now unnecessary "trim" call within the "excerpt" function has been removed.
2017-11-24Fixed a spelling mistake in several comments:Thomas Lange6-8/+8
It's called "override" instead of "overwrite" in those contexts.
2017-11-20The rem units in media queries have been replaced by simple em units.Thomas Lange2-4/+4
2017-11-13The default value for "PATHINFO.PROT" is now "https" if ↵Thomas Lange1-2/+2
$_SERVER['REQUEST_SCHEME'] is not defined (https://github.com/Nerdmind/Blog/issues/8). In addition, the default value for "PATHINFO.HOST" is now "localhost" if $_SERVER['HTTP_HOST'] is not defined.
2017-11-04The Parsedown library has been patched to prevent tab indentations from ↵Thomas Lange1-21/+10
being converted to spaces: For example, if you had used the markdown syntax for displaying source code in your post, Parsedown had replaced your semantically correct tab indentations with hard spaces. This behavior meant that the code that was displayed after parsing was no longer exactly the code you inserted into the content editor. If someone had copied source code from your post into his IDE, then your tab indentations were gone because of the spaces. That's why I hacked the Parsedown library and created a patch: https://github.com/erusev/parsedown/issues/508
2017-11-02A new action link has been added to the item overview pages and the CSS was ↵Thomas Lange4-16/+31
optimized to give them a new look.
2017-11-02The item insert link have been removed from the search pages.Thomas Lange2-8/+2
2017-11-02The item overview links have been removed from the dashboard because there ↵Thomas Lange1-3/+0
are already such links within the navigation.
2017-11-02The "title" attribute has been added to the user link.Thomas Lange2-2/+2
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-22 14:34:35 +0000