Search Results (Searched for: you do not have)
16 Jun 2026 05:23 - 16 Jun 2026 05:29
Replied by lemur on topic TreeK. Tree-Shell for Kunena Forum
TreeK: a brief description
(Links to detailed instructions for working with the post tree and the modified Kunena interface are given below.)
The topic is presented in the window as a tree according to the following rules:
- each post is displayed as one row containing the post subject and, optionally, the author's name, creation time, and post index.
Additional useful information may be placed in and under the post row, for example symbols that help navigate the tree.
The latest post in the topic by creation time is shown in bold in the tree.
The way the tree is displayed is determined by the tree view settings. When the settings are changed, the tree view changes instantly. Registered users of the site can save individual tree display settings and, if desired, restore them in another session and even for other topics.
Since the "level" of each post is known (the distance from the root of the tree, a term explained in the theoretical part), this level is graphically expressed by the length of the indent from the left edge of the window. Literally, the indent of the post row from the left edge equals the "indent size" multiplied by the post level. There is also a setting that adds a grid to the window to show the tree structure more clearly.
The 💬 symbol, when hovered over, shows the beginning of the post text as a tooltip. All other TreeK buttons and symbols also have explanatory tooltips.
You can choose what is shown at the beginning of the post row in the tree: the post subject followed by the author, the author followed by the subject, or only the subject.
The display of the date and time, as well as the post index, can be enabled or disabled.
TreeK has important options for showing post excerpts. The "text excerpt" setting displays a text fragment from the beginning of the post under the first post row, with a specified number of characters. The "screenshot excerpt" setting shows a fragment from the beginning of the post under the first post row as a screenshot with a specified height in pixels.
Additional symbols can be enabled in tree rows to help users navigate the tree more quickly.
TreeK can copy the topic tree to the clipboard in three export formats: BBCode, HTML (where subjects contain links to the posts of the exported tree), and Text.
Many users can work with the same topic at the same time, especially shortly after the topic is created. Working with a topic means simply reading its posts, replying to existing posts or editing them, studying the tree, and so on.
If a post is added to the topic while a user is working with the TreeK tree, an information message about this appears over the tree window no later than within one minute.
***
TreeK is based on the standard packages of the Kunena forum and the Aurelia template, but it changes some of their files and also connects a number of its own files, including language files that provide TreeK localization. These modified and additional files and their functions are combined in the TreekView part of the Treek package.
The interface changes required for working with topic post trees provide:
- freedom to assign post subjects and fixation of the topic title;
- clickability of the number of replies in a topic on the Recent Topics tab and of the 🌳 button in topic posts.
The other additions and changes in TreekView are not mandatory, but from the developer's point of view they make working with the forum a little faster.
(The developer could not resist implementing some of his own views on this matter, since he had to study the Kunena code in depth anyway.)
For example, the following features have been added.
The topic title is now protected: it is set once when the first post is created and never changes from the frontend. (And if a user really made a tragic mistake in the topic title and wrote "My Best Tupic" instead of "My Best Topic" in the first post, the kind site administrator and the database are always nearby.)
The reply form has been slightly changed. In particular, the subject field name Thema has been replaced with Subject, because it should describe the idea of this reply. The reply form title has been made understandable and shows whose post, and exactly which post, the user is replying to.
The subject of every reply now begins with an up arrow (⇑). This is a link to the parent post. Clicking ⇑ takes the user to the post that was replied to.
Instead of words requiring localization, such as "replied to", TreekView uses a simple, understandable, and quickly learned system of arrows listed below. Clickable arrows are buttons because they trigger certain actions. Arrows may be visible in reply forms (Reply and Quick Reply) and in post subjects.
As mentioned above, the subject of the post being created can be arbitrary text. But to speed up work with the forum, the concept of a suffix has been introduced.
Suffixes
When replying to a message, special text related to the subject of the parent post can be added to the reply subject.
In TreekView, this special text is called a suffix. Suffixes help automatically preserve the link between the reply subject and the parent post subject, and make the topic easier to read because they help show which post was replied to.
The use of suffixes looks as follows.
When the reply form is opened, information about the parent post subject is automatically added to the subject field in the form "⇒ Parent subject" (the "⇒" arrow is a replacement for "Reply to").
If the user does not add new text to the subject to clarify the meaning of the post, the suffix becomes the subject of the created post.
If new text is entered in the Subject field and the suffix is not completely removed, it becomes part of the post subject together with the new subject text.
New text is entered in the Subject field to the left of the suffix. The cursor is positioned automatically, and it is impossible to place it inside the suffix.
The suffix cannot be changed by editing. However, if the new post subject becomes so long that the combined length of the new text and the suffix exceeds the subject length set in Kunena, the end of the suffix is gradually pushed out of the line. If the user decides to shorten their text, for example by deleting the end of their text with Backspace, the pushed-out end of the suffix returns accordingly. If the suffix is partially pushed out, it is included in the post subject in shortened form.
The suffix can be removed at any time by clicking the ⇏ button located to the right of the word Subject. The ⇏ button then changes to ⇍. Clicking ⇍ disables the addition of suffixes for the whole session. After that, the ⇒ button appears next to the word Subject; clicking it restores the use of suffixes.
The site administrator can disable the use of suffixes entirely, although this is not recommended.
If the parent's Subject already has the form "⇒ Reply to post", the child's suffix will become "⇒ ⇒ Reply to post", with two ⇒ ⇒ arrows. These two arrows remain in suffixes regardless of which generation in a chain of posts with suffix-only subjects the given post belongs to.
The administrator can change the arrow symbols in the language file, for example replacing "⇒" with "→".
(Adding no more than two ⇒ arrows gives us a reason to discuss the theory of working with posts; and where, if not on this forum, should theory be discussed?
The situation with posts in a topic can, forgive me, be compared with the situation among people. Just as in life someone dies, and someone divorces and takes the children with them, so in a topic a post can be deleted, and some part of a topic can be moderated and moved to another topic. This leads to important consequences for the TreeK tree-building algorithm, but, as stated above, we will not go into theory here.)
Let us note a few more interface changes that, in the developer's view, make the user's work with Kunena slightly faster.
Attachments
In post creation and editing forms (screenshots), there is an Attachments block. Although it is used relatively rarely, when an attachment really needs to be inserted into or removed from a message, users still have to spend time scrolling past this block every time.
In TreekView, the Attachments block is collapsed by default. Instead of the full block, the existing word Attachments is shown, followed in parentheses by the number of attachments if there are any, and then by the expansion symbol for this block: a black filled triangle ▼. This triangle has a tooltip: "Open attachments block". Clicking ▼ opens the Attachments block, and the user sees what is currently visible in the block.
The arrow then changes to ▲, with the tooltip: "Close attachments block". Clicking ▲ collapses the block.
The Action menu in a post.
The developer considered the drop-down Action "menu" at the bottom of a post to be another factor slowing work down.
TreekView restores a view that once existed in Kunena, where each option - Reply, Quote, and Edit - has its own button.
Some other small interface details have also been changed, for example the reply form title has been changed from <h1> to <h5>.
(Links to detailed instructions for working with the post tree and the modified Kunena interface are given below.)
The topic is presented in the window as a tree according to the following rules:
- each post is displayed as one row containing the post subject and, optionally, the author's name, creation time, and post index.
Additional useful information may be placed in and under the post row, for example symbols that help navigate the tree.
The latest post in the topic by creation time is shown in bold in the tree.
The way the tree is displayed is determined by the tree view settings. When the settings are changed, the tree view changes instantly. Registered users of the site can save individual tree display settings and, if desired, restore them in another session and even for other topics.
Since the "level" of each post is known (the distance from the root of the tree, a term explained in the theoretical part), this level is graphically expressed by the length of the indent from the left edge of the window. Literally, the indent of the post row from the left edge equals the "indent size" multiplied by the post level. There is also a setting that adds a grid to the window to show the tree structure more clearly.
The 💬 symbol, when hovered over, shows the beginning of the post text as a tooltip. All other TreeK buttons and symbols also have explanatory tooltips.
You can choose what is shown at the beginning of the post row in the tree: the post subject followed by the author, the author followed by the subject, or only the subject.
The display of the date and time, as well as the post index, can be enabled or disabled.
TreeK has important options for showing post excerpts. The "text excerpt" setting displays a text fragment from the beginning of the post under the first post row, with a specified number of characters. The "screenshot excerpt" setting shows a fragment from the beginning of the post under the first post row as a screenshot with a specified height in pixels.
Additional symbols can be enabled in tree rows to help users navigate the tree more quickly.
TreeK can copy the topic tree to the clipboard in three export formats: BBCode, HTML (where subjects contain links to the posts of the exported tree), and Text.
Many users can work with the same topic at the same time, especially shortly after the topic is created. Working with a topic means simply reading its posts, replying to existing posts or editing them, studying the tree, and so on.
If a post is added to the topic while a user is working with the TreeK tree, an information message about this appears over the tree window no later than within one minute.
***
TreeK is based on the standard packages of the Kunena forum and the Aurelia template, but it changes some of their files and also connects a number of its own files, including language files that provide TreeK localization. These modified and additional files and their functions are combined in the TreekView part of the Treek package.
The interface changes required for working with topic post trees provide:
- freedom to assign post subjects and fixation of the topic title;
- clickability of the number of replies in a topic on the Recent Topics tab and of the 🌳 button in topic posts.
The other additions and changes in TreekView are not mandatory, but from the developer's point of view they make working with the forum a little faster.
(The developer could not resist implementing some of his own views on this matter, since he had to study the Kunena code in depth anyway.)
For example, the following features have been added.
The topic title is now protected: it is set once when the first post is created and never changes from the frontend. (And if a user really made a tragic mistake in the topic title and wrote "My Best Tupic" instead of "My Best Topic" in the first post, the kind site administrator and the database are always nearby.)
The reply form has been slightly changed. In particular, the subject field name Thema has been replaced with Subject, because it should describe the idea of this reply. The reply form title has been made understandable and shows whose post, and exactly which post, the user is replying to.
The subject of every reply now begins with an up arrow (⇑). This is a link to the parent post. Clicking ⇑ takes the user to the post that was replied to.
Instead of words requiring localization, such as "replied to", TreekView uses a simple, understandable, and quickly learned system of arrows listed below. Clickable arrows are buttons because they trigger certain actions. Arrows may be visible in reply forms (Reply and Quick Reply) and in post subjects.
As mentioned above, the subject of the post being created can be arbitrary text. But to speed up work with the forum, the concept of a suffix has been introduced.
Suffixes
When replying to a message, special text related to the subject of the parent post can be added to the reply subject.
In TreekView, this special text is called a suffix. Suffixes help automatically preserve the link between the reply subject and the parent post subject, and make the topic easier to read because they help show which post was replied to.
The use of suffixes looks as follows.
When the reply form is opened, information about the parent post subject is automatically added to the subject field in the form "⇒ Parent subject" (the "⇒" arrow is a replacement for "Reply to").
If the user does not add new text to the subject to clarify the meaning of the post, the suffix becomes the subject of the created post.
If new text is entered in the Subject field and the suffix is not completely removed, it becomes part of the post subject together with the new subject text.
New text is entered in the Subject field to the left of the suffix. The cursor is positioned automatically, and it is impossible to place it inside the suffix.
The suffix cannot be changed by editing. However, if the new post subject becomes so long that the combined length of the new text and the suffix exceeds the subject length set in Kunena, the end of the suffix is gradually pushed out of the line. If the user decides to shorten their text, for example by deleting the end of their text with Backspace, the pushed-out end of the suffix returns accordingly. If the suffix is partially pushed out, it is included in the post subject in shortened form.
The suffix can be removed at any time by clicking the ⇏ button located to the right of the word Subject. The ⇏ button then changes to ⇍. Clicking ⇍ disables the addition of suffixes for the whole session. After that, the ⇒ button appears next to the word Subject; clicking it restores the use of suffixes.
The site administrator can disable the use of suffixes entirely, although this is not recommended.
If the parent's Subject already has the form "⇒ Reply to post", the child's suffix will become "⇒ ⇒ Reply to post", with two ⇒ ⇒ arrows. These two arrows remain in suffixes regardless of which generation in a chain of posts with suffix-only subjects the given post belongs to.
The administrator can change the arrow symbols in the language file, for example replacing "⇒" with "→".
(Adding no more than two ⇒ arrows gives us a reason to discuss the theory of working with posts; and where, if not on this forum, should theory be discussed?
The situation with posts in a topic can, forgive me, be compared with the situation among people. Just as in life someone dies, and someone divorces and takes the children with them, so in a topic a post can be deleted, and some part of a topic can be moderated and moved to another topic. This leads to important consequences for the TreeK tree-building algorithm, but, as stated above, we will not go into theory here.)
Let us note a few more interface changes that, in the developer's view, make the user's work with Kunena slightly faster.
Attachments
In post creation and editing forms (screenshots), there is an Attachments block. Although it is used relatively rarely, when an attachment really needs to be inserted into or removed from a message, users still have to spend time scrolling past this block every time.
In TreekView, the Attachments block is collapsed by default. Instead of the full block, the existing word Attachments is shown, followed in parentheses by the number of attachments if there are any, and then by the expansion symbol for this block: a black filled triangle ▼. This triangle has a tooltip: "Open attachments block". Clicking ▼ opens the Attachments block, and the user sees what is currently visible in the block.
The arrow then changes to ▲, with the tooltip: "Close attachments block". Clicking ▲ collapses the block.
The Action menu in a post.
The developer considered the drop-down Action "menu" at the bottom of a post to be another factor slowing work down.
TreekView restores a view that once existed in Kunena, where each option - Reply, Quote, and Edit - has its own button.
Some other small interface details have also been changed, for example the reply form title has been changed from <h1> to <h5>.
10 Jun 2026 22:31
08 Jun 2026 15:51
06 Jun 2026 21:03 - 06 Jun 2026 21:05
06 Jun 2026 18:19 - 06 Jun 2026 18:23
In fact these errors are coming because (Cut, Copy...) are not defined in the config.xml
Replied by xillibit on topic sceditor update pack
I have tested your new file but it's the same.
I don't see the reason for this errors, (I don't have them) -Can-you provide a fix for that ?
the array keys are not new, only the strings in $editorButtons have changed a bit (mostly lowercase)
I just looked at the github file and mine, and the only difference are the new additions what I have added for CKEditor,
so I just deleted them and now the line numbering corresponds each other, so they should be identical (beside the string changes)
check the new file
In fact these errors are coming because (Cut, Copy...) are not defined in the config.xml
I have removed the bits for undo which will be in a new PR and i had found weird that there is some space left on the right :
as far as I see, you have added the new famfamfam.png, but not the new css code for those kunena icons in the default.cssJust applied your changes for the issue reported by rich : github.com/Kunena/Kunena-Forum/commit/c2...66e5c9c15f4967410283
(the only change I see is the cutout my left-side buttons option, but not the new position definitions for the icons)
06 Jun 2026 15:02
06 Jun 2026 09:23 - 06 Jun 2026 09:44
06 Jun 2026 00:30 - 06 Jun 2026 00:54
05 Jun 2026 18:47
Replied by xillibit on topic sceditor update pack
I have added your changes about undo plugin in this pull request :
github.com/Kunena/Kunena-Forum/pull/10103
I think i have missed somthing because the result is not what expected :
I think i have missed somthing because the result is not what expected :
03 Jun 2026 17:02
02 Jun 2026 17:05 - 04 Jun 2026 12:59
sceditor update pack was created by joomod
what I have done (and hopefully fixed) is for sceditor and Kunena v7.0.5+ only (ckeditor will be next 
all files in the package are in the edited version, based on 7.0.5 and in their used folder structure
BUT
I have NOT included the minified versions of sceditor and bbcode, because I don't know
a secure online tool - so just keep the simply renamed full versions or the kunena team can minify it.
for a preview you may look here:
bg310.breastguide.org/index.php/de/forum...25-welcome-to-kunena
Part of the message is hidden for the guests. Please log in or register to see it.
updated: jquery poll detect and disable poll edit (if config poll edit = disabled)
new famfamfam.png and default.css including, using kunena icons
- edit the setup call to use the bbcode settings from the config to en/disable buttons.
- add confidential | hide | spoiler - now can be used in sceditor
- added the undo plugin (with buttons)
- added the language support within sceditor
- little restyling of the editor layout (fixed buttons - undo/redo, cut/copy/paste, source etc on the left side)
- added the poll edit suport in sceditor (if poll exists, data are fetched)
- the main work: image size (as included in 7.0.5) and fetching image attributes if img selected
(also added alt and float attribute for images)
all files in the package are in the edited version, based on 7.0.5 and in their used folder structure
BUT
I have NOT included the minified versions of sceditor and bbcode, because I don't know
a secure online tool - so just keep the simply renamed full versions or the kunena team can minify it.
for a preview you may look here:
bg310.breastguide.org/index.php/de/forum...25-welcome-to-kunena
Part of the message is hidden for the guests. Please log in or register to see it.
updated: jquery poll detect and disable poll edit (if config poll edit = disabled)
new famfamfam.png and default.css including, using kunena icons
30 May 2026 14:53
28 May 2026 17:00 - 28 May 2026 17:52
17 May 2026 19:04 - 17 May 2026 19:31
17 May 2026 16:16
Replied by kboth on topic Kunena Poll does not work
Thank you very much. I carried out this initial test on my test system. Apart from the fact that there is no image on the button, creating a poll there worked fine. I was just confused because the poll isn’t displayed until you’ve submitted the topic. I then found that in the documentation. I find that inconvenient, especially as you can’t make any corrections either...
In the production system, it looks normal, meaning the button does have the icon. Otherwise, it works exactly the same in PROD as it does in TEST.
(My test system is a copy (using Akeeba) of the PROD system. -- My main focus was actually on testing the update to PHP 8.5—first in TEST, then in PROD
)
Best regards
Karlheinz Bothmann
In the production system, it looks normal, meaning the button does have the icon. Otherwise, it works exactly the same in PROD as it does in TEST.
(My test system is a copy (using Akeeba) of the PROD system. -- My main focus was actually on testing the update to PHP 8.5—first in TEST, then in PROD
Best regards
Karlheinz Bothmann
Time to create page: 0.311 seconds