Category: Article

In general, wiki syntax is not parsed in notification mails. For example, the "New article post" notification email includes the full body of the newly posted article. However, Tiki includes the full wiki coding/syntax within the body of the message, and sends the mail message as plain text. Tiki should either:

1. Send the message as parsed HTML

or

2. Strip all formatting and send only the text.

In order to avoid duplication of effort, It would be very nice to be able insert a calendar item when editing an article in Tiki.

I imagine that as a new option in article edit form, for any article type or just some type, like "event", or so. You should be able to select the date or dates to insert that info in the calendar feature, select which calendar, etc.

So that calendar and upcoming_events module is updated when a new article is posted with that option selected.

For WiKi pages I use the WYSIWYG (FCKEditor) but this is not an option for Articles. There you can only use the simpel Text Area and Quicktags. It's must better if you can use the WYSIWYG (FCKEditor) for every text input.

I discovered a problem where one of our users had created a page containing the words SeaMonkey in the description. When she later tried to link to this page with the syntax ((PageName|This is the link text)), the link broke, and tried to embed a link to create a new page titled SeaMonkey among other things. The cause of the problem, was that the description of the page she linked to, was inserted as the title of the <a>-tag.

PDF-generation does not work at all in Opera 9. The pdf generation page is shown, but when you click "create" nothing happens. I have check this for wiki pages and articles. I don't know if pdf-generation is available for other features.

When you display articles using the module articles (http://doc.tiki.org/Module-articles) the output gets alphabetically sorted by topic.

For several use cases it would be desirable if more control over the output be possible, like sorting by alternative fields (date/time of publication or expiry), or reverse sorting order, or some other even deeper sorting options.

To give an example:
When you use articles to show hints for upcoming TV shows, you will have date, time, channel and program name in the topic. Unless you are in Japan sorting alphabetically by a field starting with a date will NOT yield the desired sorting order.

In continental Europe dates start with the tens of the day of month, leading to the ones, then go on with the tens of the month itself, and so on. This will lead to a first of July being before a February 28th..

In Japan, dates begin with millenia, followed by centuries, and so on, thereby providing correct order through alphabetical sorting. But in UK and USA you run into the same problem once your dates start with spelled out months (resulting in April being the first).

e

{syntax type="tiki" editor="plain"}
Using Plugin Edit to amend a FancyTable in WYSIWYG submitting a change causes all line breaks in the table body to be removed.

The PluginEdit shows the field "Rows separated by >> in the header; for the table body, one row per line. Cells separated by | in both cases."

Creating a working FancyTable with table body rows like this:

row 1 cell 1 | row 1 cell 2
row 2 cell 2 | row 2 cell 2

after inserting with the plugin edit tool this changes to:

row 1 cell 1 | row 1 cell 2 row 2 cell 2 | row 2 cell 2

{syntax type="tiki" editor="plain"}
There is a serious error in the Wiki Syntax display in __Articles__.

When using PLAIN TEXT markers (np and /np), the preview shows the correct unprocessed text. But when saved, the actual file does not show the correct unprocessed text on display.

Theme: Five Alive

I verified that the marked plain text displays correctly as a WIKI PAGE. But it does not display correctly as an ARTICLE.

tiki-objectpermissions.php references tiki_p_admin_objects which is not defined. For that reason the test in line 11 fails and even admin does not have the permissioin the change permissions of article themes.

There may be cases when an article type doesn't call for the publication date to be displayed. But then the publication date input isn't on the edit screen. Then there is no way to control the display order of articles other than in the order they are created. For maximum editorial flexibility, the editor screen should allow publication date input even if the date isn't going to be displayed.

CREATE TABLE tiki_articles(

articleId int( 8 ) NOT NULL AUTO_INCREMENT ,
.
.
reads int( 14 ) default NULL ,
.
.
KEY reads( reads ) ,
KEY author( author( 32 ) ) ,
FULLTEXT KEY ft( title, heading, body )
) TYPE = MYISAM AUTO_INCREMENT =1

cause

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'reads int(14) default NULL,
votes int(8) default NULL,
points int(14) defaul' at line 28

RSS feed for Articles in tiki.org produces WSOD. Reproduced here:
https://tiki.org/tiki-articles_rss.php?ver=5

or
https://tiki.org/tiki-articles_rss.php?ver=5&css=y
(as indicated here https://profiles.tiki.org/RSS+Handler which used to be a valid url afair)

or
https://tiki.org/tiki-articles_rss.php?ver=2

However, it works well in themes.t.o:
https://themes.tiki.org/tiki-articles_rss.php?ver=5

I wanted to add that articles rss feed to the Admin UI backend rss module ( loaded from here https://profiles.tiki.org/Unified_Admin_Backend_Default_Dashboard_1 ), but there is no point if it triggers some error 500 or WSOD by any other reason.

Any tip anyone on how to solve? @ohertel maybe?

Updated from 9.3 to 12.3, now RSS Feeds for articles not working.
In any browser displaying blank page. Without any errors ( I have enable error reporting from admin > general).
This is RSS feed: http://e-republika.cz/tiki-articles_rss.php?ver=2
RSS feed for blogs works fine.
Version PHP: 5.5.18

{img fileId="977" thumb="y" rel="box[g]"}
{img fileId="978" thumb="y" rel="box[g]"}
{img fileId="979" thumb="y" rel="box[g]"}

The RSS feeds seem to have no permission checking. The feeds should only include information that is available to Anonymous.

Install:

tikiwiki 1.9.3.2
PHP 5.1.4 (Build 2600)
Apache 2.2.2
MySQL 5.0

When adding the following text to a page (text between but not including the "$" symbols) it will preview fine, but the Save operation causes an error with MySQL which shows up in the Apache logs as:
{CODE()}
[Thu Jun 22 17:04:50 2006] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Thu Jun 22 17:04:50 2006] [notice] Apache/2.2.2 (Win32) PHP/5.1.4 configured -- resuming normal operations
[Thu Jun 22 17:04:50 2006] [notice] Server built: Apr 29 2006 18:32:31
[Thu Jun 22 17:04:50 2006] [notice] Parent: Created child process 672
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Child process is running
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Acquired the start mutex.
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Starting 250 worker threads.
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Starting thread to listen on port 80.
{CODE}

Here is the text you can try:


$

))Cohen-Steiner(( “Restricted delauney triangulations and normal

cycles”. are estimates of

the principle curvature directions at the vertex. Once we have computed principle curvatures for every isosurface

vertex, we can use the jack triangle floodfiller to flood-follow lines of curvature. The complexity here is how to

sample the curvature fields to produce curves.

*)

$

Install:

tikiwiki 1.9.3.2
PHP 5.1.4 (Build 2600)
Apache 2.2.2
MySQL 5.0

Whwn adding the following text to a page (text between but not including the "$" symbols) it will preview fine, but the Save operation causes an error with MySQL which shows up in the Apache logs as:

[Thu Jun 22 17:04:50 2006] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Thu Jun 22 17:04:50 2006] [notice] Apache/2.2.2 (Win32) PHP/5.1.4 configured -- resuming normal operations
[Thu Jun 22 17:04:50 2006] [notice] Server built: Apr 29 2006 18:32:31
[Thu Jun 22 17:04:50 2006] [notice] Parent: Created child process 672
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Child process is running
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Acquired the start mutex.
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Starting 250 worker threads.
[Thu Jun 22 17:04:51 2006] [notice] Child 672: Starting thread to listen on port 80.


Here is the text you can try:


$

))Cohen-Steiner(( “Restricted delauney triangulations and normal

cycles”. are estimates of

the principle curvature directions at the vertex. Once we have computed principle curvatures for every isosurface

vertex, we can use the jack triangle floodfiller to flood-follow lines of curvature. The complexity here is how to

sample the curvature fields to produce curves.

*)

$

{syntax type="tiki" editor="plain"}
After my last 29.x update I have a 500 error when I'm saving an article that is in french.
I have a English article, the translation, and I don't have the error so I tried to track the problem.

This sentence causes the 500:
"Tiki Wiki CMS est au cœur de plusieurs sites qui subissent les requêtes de crawlers d’IA, agressifs et voraces, capables de saturer les serveurs au point de rendre les applications lentes ou carrément inaccessibles comme nous l’avons montré dans un [article19-IA-des-crawlers-affames-qui-saturent-vos-serveurs-et-rendent-vos-sites-lents-ou-inaccessibles|précédent article]."

If I change for this sentence no error 500:
"Tiki Wiki CMS est au cœur de plusieurs sites qui subissent les requêtes de crawlers d’IA, agressifs et voraces. Ces derniers sont capables de saturer les serveurs au point de rendre les applications lentes ou carrément inaccessibles comme nous l’avons montré dans un [article19-IA-des-crawlers-affames-qui-saturent-vos-serveurs-et-rendent-vos-sites-lents-ou-inaccessibles|précédent article]."

I agree that this is crazy, but that's what it is...

PHP log says:
{CODE()}
[26-Nov-2025 18:21:16 UTC] PHP Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 134752405 bytes) in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:16 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[08S01]: Communication link failure: 1153 Got a packet bigger than 'max_allowed_packet' bytes in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:15 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:14 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:14 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:14 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:14 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:14 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:14 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:14 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'comment' at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\\\...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\\\',...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3\',`n...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3',`na...' for column `opensourcesolutions_tiki29`.`tiki_actionlog`.`comment` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:21:13 UTC] PHP Warning: PDOStatement::execute(): SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xC3' for column `opensourcesolutions_tiki29`.`tiki_objects`.`description` at row 1 in /home/opensourcesolutions/public_html/lib/core/TikiDb/PdoDb.php on line 109
[26-Nov-2025 18:20:51 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[26-Nov-2025 18:20:51 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[26-Nov-2025 18:20:51 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[26-Nov-2025 18:20:51 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[26-Nov-2025 18:20:37 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[26-Nov-2025 18:20:37 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[26-Nov-2025 18:20:37 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[26-Nov-2025 18:20:37 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[26-Nov-2025 18:20:37 UTC] PHP Warning: Undefined array key "key" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 26
[26-Nov-2025 18:20:37 UTC] PHP Warning: Undefined array key "itemkey" in /home/opensourcesolutions/public_html/tiki-read_article.php on line 25
[26-Nov-2025 18:20:34 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[26-Nov-2025 18:20:34 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[26-Nov-2025 18:20:34 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[26-Nov-2025 18:20:34 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[26-Nov-2025 18:20:29 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[26-Nov-2025 18:20:29 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
[26-Nov-2025 18:20:29 UTC] PHP Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 51
[26-Nov-2025 18:20:29 UTC] PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/opensourcesolutions/public_html/lib/wiki-plugins/wikiplugin_includetpl.php on line 44
{CODE}

Right now, the sefurl for article topics is:

articles?topicName=news to tiki-view_article.php

Possibly, articles/news should point to tiki-view_article.php?topicName=news

I think this might be common enough to be a core feature.

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))

!Summaries styles associated to levels in all hierarchical lists

!!Utility
When a hierarchy (summaries particularly) is displayed there is no style associated with the level.

Generally in all documents a different style is associated with level independently of the indentation.

!!the aim, a better readability.

This is en enhancement of style, but it is a very precise detail and a problem of esthetic's independently of the aim, a better readability.

!!constraints
So it should be optional and easy to modify into the style. Asssociated with the style not with the layout.css.

!!What's done
Efficient in my application since 5.3
Easy to enhance for 6.x and more 7.x

!!Changes
*tpl (two ones)
*styles

__Remark : __can be done independently, after the change into tpl, take effect when classes are defined into css
__Optionally :__ size of text by level and by default set in layout, colors or changes in text sizes or text styles into styles.
__Note:__ the name of the style is built automatically with a pattern, used for text and number (if option used), then the developer of style.css can easily add and/or find them for modification

trebly

(ref:B10125-06)

The way articles bloc are positioned changed in Tiki19.

It used to be :
||Title
Author date
Illustration | Content
More button||

It is now (tested on several themes);
{img fileId="1242" thumb="box"}

{syntax type="tiki" editor="plain"}
On Tiki30 the meta description is using the website default metatag description and not the Article specific description as in Tiki27, 28 and 29.

{img fileId="3266" thumb="box"}

{img fileId="3267" thumb="box"}

{syntax type="tiki" editor="plain"}
Displaying an image with an alt attribute is an accessibility problem, and the "article image" in Tiki's articles feature have no way of inputting the alt text. The page source shows -+ alt="" +- but it's empty because there's no form input when editing the article to specify it.

{syntax type="tiki" editor="plain"}
Hello Devs,

I did upgrade a site to 7.1 this weekend.

Using WYSIWYG/CKE I have the following prblem:

In some features of the Tiki 7.1 the output the editor is just the plain
HTML Source.

That means, not in Wikipages, but in the articles and in the calendar
events, there is not a nice text with formatting bold, italic, colors
and pictures etc, but only the plain HTML source code visible to the
website user/visitor.

The WYSIWYG/CKE editor works normal and I can see the content just
normal like ever, being in the editing mode. But when I save, I can just
see the source code, like it would be in codeplugin.

This affects as said articles and calendar (perhabs more, I will hope to
find out) but it does not affect wikipages by now.

And it affects existing articles and events aswell as newly edited.

(worked well in 6.x before)

Thx for reply and wish a nice sunday to all,
cheers
Torsten