Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Don't use the template function "escapeHTML" internally and replace all
occurrences outside of the template files with "htmlspecialchars".
|
|
The "getAll" method of the Entity class should return an array with real
attributes of the Entity object but not internally used properties.
|
|
|
|
|
|
Implement and use a better mechanism to detect changes of attributes of
the Entity objects by using a private variable which keeps track of the
changed Entity attributes ("properties") via the "set" method.
The "insert" and "update" method of the Repository now calls the method
"getModifiedKeys" of the Entity class to get a list of properties which
have been changed and builds the database query accordingly.
This makes the use of "FALSE" as default value for the Entity attributes
obsolete, so they have been set to the initial PHP default ("NULL").
|
|
|
|
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.
|
|
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.
|
|
|
|
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 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).
|
|
|
|
|
|
|
|
Reuse the already defined prepared statement in the update method of
the Category repository instead of creating a new one.
|
|
Fix a bug which was introduced with the commit mentioned below that
prevented the "$ITEM['BODY']['TEXT']()" function from returning the
pre-parsed body of the item, because the variable was not in scope.
See: bf57f3dcba5864b63882c273d25403c28637eeab
|
|
This commit removes the pages from the RSS feed. I decided so because a
page is a "timeless" object intended for things like the imprint, about
page, privacy policy and similar stuff. It also makes things easier.
The new primary feed URL is "/feed/" and shows only posts. The page feed
("/feed/page/") has been removed and will throw a 404 Not Found error.
The visitors who already subscribed to the old post feed ("/feed/post/")
are automatically 301-redirected to the new location ("/feed/").
The following system language variables have been removed:
* feed_name_items
* feed_name_pages
* feed_name_posts
The following configuration options have been removed:
* PAGE.FEED_SIZE
* PAGE.FEED_SORT
* PAGE.FEED_GUID
Furthermore, the template file "feed/item_post.php" has been renamed to
"feed/item.php" since there is now only one type of feed item. If the
system cannot find the "feed/item.php", it tries "feed/item_post.php"
instead (for backward compatibility with older themes).
|
|
If the migration table does not yet exist, the user sits *either* at 0,
1, 2, 3 or 4; not *between* 0 and 4 (which would be 1, 2 or 3).
|
|
This commit adds the timestamp of the last modified category to the HTTP
ETag response header. Additionally, the code has been optimized.
|
|
This commit adds and uses the new function createPaginationTemplate to
create the generic pagination template for various entity lists.
This function replaces the many old confusing functions:
* generateNaviTemplate
* generatePageNaviTemplate
* generatePostNaviTemplate
* generateUserNaviTemplate
* generateCategoryNaviTemplate
* generateCategoryPostNaviTemplate
|
|
The option CATEGORY.LIST_SORT is currently only used for sorting the
children categories of a category, not for sorting the categories on
the category overview page.
This is because the sorting of the categories in the category overview
is handelnd internally with a virtual table column "_depth" which sorts
the categories by name *and* its sub categories (like a tree).
Thus, there is currently no user option to sort the category overview.
|
|
If no category tree was found, the array is empty but isset evaluates
to true. This fixes the mistake and uses an empty check instead.
|
|
Add and use the function generateCategoryPostNaviTemplate to build the
pagination template for posts in a category. This fixes a mistake.
TODO: Get rid of that confusing function mess!
|
|
This commit implements a new category system to categorize posts. Each
category can have an unlimited number of nested children categories. A
single post don't necessarily need to be in a category, but it can.
Each category can have a full content body like posts or pages, so you
have enough space to describe the content of your categories.
Please note that you need to have at least the following MySQL/MariaDB
versions to use the category system, because it uses "WITH RECURSIVE"
database queries, the so-called "Common-Table-Expressions (CTE)".
MariaDB: 10.2.2
MySQL: 8.0
See: https://mariadb.com/kb/en/with/
See: https://dev.mysql.com/doc/refman/8.0/en/with.html
|
|
This commit updates the database schema and adds a new migration for the
upcoming category system. Please note that you need to have at least the
following MySQL/MariaDB versions to use the category system later:
MariaDB: 10.2.2
MySQL: 8.0
|
|
Explicitly check for boolean FALSE because the result can be string "0"
when directly upgrading from release v1.0 which has schema version "0".
|