| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Add a link to the current entity on the website and a link to the entity
delete form in the administration area's update.php templates.
|
|
|
|
|
|
Since the introduction of the category system, the application requires
MySQL >= 8.0, so we should update the links to the documentation of the
MySQL search functionality to match the minimum required MySQL version.
|
|
|
|
Don't check the return value of the Repository's "insert" and "delete"
methods in the administration controllers for creating and modifying
entities since a PDOException is thrown if an error occurs.
|
|
Print an error message for various actions in the administration area if
the security token is invalid, instead of silently preventing the user's
desired action to perform if the token is invalid for some reason.
This change applies for the delete actions on all entity types and also
for the login action and the database command execution form; the forms
for creating/modifying entities had already shown a CSRF error before.
|
|
Simplify the HTTP-POST parameter presence check in the administration
controllers for creating and modifying entities. Since we already use
fallback values for each attribute, we don't need a full param check.
|
|
Remove those "trim" calls and use "strpos" to check if the ETag value
generated by the system is contained somewhere in the "If-None-Match"
request header sent by the client (if present).
With this commit, the ETag header validation now also works with nginx.
The nginx web server prefixes the "ETag" header generated by the system
with the string "W/" which caused the previous validation code to fail.
Instead of using multiple "trim" calls or "preg_replace", we now use a
single, simple and fast "strpos" call to check if the system generated
Etag hash value is contained in the "If-None-Match" request header.
|
|
|
|
Move the logic for generating the error pages into the Application class
to remove this ugly "require" call in the error403 and error404 methods.
|
|
|
|
|
|
Posts in a category are paginated, so display the number of the current
page in square brackets within the categories <title> element.
|
|
|
|
Reduce some boilerplate code in the index.php by using a foreach loop to
register the routes for the various item controllers.
|
|
Do not force the recreation of the Language object in the migrations.php
file anymore by changing the include position of the migrations.php (and
the functions.php) in the application.php file a bit to the top.
|
|
|
|
|
|
|
|
Show a message in the administration area's post and page search form if
the search query returned no results.
|
|
Do not rely on the "$POST['GUID']" template parameter anymore and create
the GUID for the feed item manually in the feed item's template file.
The application internal function "generatePseudoGUID" has been removed
and the function "generateItemTemplateData" will not return the "GUID"
part anymore (which was only used by the feed item template anyway).
For backward compatibility, the "$POST['GUID']" template parameter will
still be present in the feed item template, but not in other templates!
|
|
Remove the configuration option "POST.FEED_GUID" that contained the name
of the columns from the database which were passed to the SHA1 function
for generating the pseudo GUID for the items in the RSS feed.
|
|
In addition to the last commit, use the correct configuration option in
the code to check if single items should be redirected.
|
|
Rename the config options "(CATEGORY|PAGE|POST|USER).SINGLE_REDIRECT" to
to "(CATEGORY|PAGE|POST|USER).REDIRECT_SINGLE".
|
|
|
|
Add a quick link to the post search in the administration area with the
category of the item preselected to search only posts in this category.
|
|
|
|
Add a user and category filter option for the post search in the
administration area. Filter on default theme is followed later.
|
|
Move the methods for the search functionality of the abstract Repository
class into a separate trait and use it in the Page and Post repository.
The reason because of this is that only the Page and Post repositories
having a search functionality, while the other repositories have not.
|
|
Catch possible PDOException on search requests with queries like "*" and
pass the exception message to the template for displaying.
|
|
Add pagination for search results in the admin and default theme.
|
|
Escape possible percent characters ("%") in the URL params for sprintf.
Otherwise the pagination template breaks if URL params which contain a
percent sign are merged into the pagination URL.
|
|
|
|
|
|
|
|
Do not redefine properties that are already defined in the Entity class.
|
|
Rename the repository classes and append the name with "Repository" to
prevent naming confusions with the entity classes.
|
|
|
|
This commit implements a new feature called *content functions* that is
similar but much more powerful than the already existing *content tags*
which you may have already used (`{POST[1]}`, for example).
You now can also add your own *content functions* to do some interesting
things like embedding a YouTube video or other things to prevent typing
repetitive lines of text or code in your entities content.
Read the corresponding wiki page to learn more about this:
https://github.com/Nerdmind/Blog/wiki/Content-functions
|
|
|
|
Classes:
* Parsers\ArgumentParser
* Parsers\EmoticonParser
* Parsers\MarkdownParser
Interfaces:
* Parsers\ParserInterface
|
|
This commit adds the configuration option "WRAP_EMOTICONS" to supersede
the configuration options "(CATEGORY|PAGE|POST|USER).EMOTICONS".
If the value of "WRAP_EMOTICONS" evaluates to TRUE, the emoticons found
in the content of an item will be wrapped into a "<span>" element which
gives the user a description of the emoticon in the "title" attribute.
|
|
Reduce the redundant mapping logic in the repository classes by using
the new methods "fetchEntity" and "fetchEntities".
|
|
Make the function parseUnicodeEmoticons significantly faster by using
a single regex operation to match and process all unicode emoticons.
|
|
This commit drops support for parsing plain text ASCII emoticons like
":)" or ":P" to its unicode equivalent. Please use unicode emoticons
directly (like those already proposed in the admin form templates).
|
|
* Add noisy background images
* Rename SCSS/CSS file "main" to "bright"
* Remove uppercase text-transform for headings
* Replace hardcoded font sizes with SCSS variables
* Decrease font size for category link in post item template
* Move right-floated ID before the heading in the HTML markup to ensure
it does not moves to the second line if the heading text is too wide.
|
|
|
|
|
|
|
