Category: Wiki (page view, edit, history, rename, etc)

{syntax type="tiki" editor="plain"}
The style= attribute passed to {DIV} and other wiki plugins is silently dropped.
I believe (I'm not pro understanding git) it comes from here: https://gitlab.com/tikiwiki/tiki/-/commit/7b9d81b6f30c7532bee770079ddeead22838a3f1

In lib/wiki-plugins/wikiplugin_div.php, the function wikiplugin_div() initializes $style = '' before calling extract($params, EXTR_SKIP). Because EXTR_SKIP skips extraction when a variable already exists, the style parameter from $params never overwrites the empty $style variable.

At lib/wiki-plugins/wikiplugin_div.php
I changed :
{CODE()}
function wikiplugin_div($content, $params)
{
$style = '';
extract($params, EXTR_SKIP);
{CODE}

For

{CODE()}
function wikiplugin_div($content, $params)
{
extract($params, EXTR_SKIP);
$style = $style ?? '';
{CODE}

refreshed the cache en the issue was fixed.

To insert a special character within tiki-editpage.php in 1.9DR4 you have to use templates/tiki-special_chars.php which cannot be accessed because of .htaccess settings.
a better solution because that little bloody window is a pain anyway (and inserts the characters always in the end of the editing window:

I have done a fix, by including the following lines (see solution) after the table row with the smileys and cutting the link to tiki-special_chars from below the quicktags:

Special characters is now via a popup. This is bad because the one click javascript insert doesn't work. "Basic" special characters should be integrated in the template.

Could (should?) be contextual to language. Current page? User language(s)? What if use speaks many?

It could also be a drop down-menu like with available languages. Go edit a page on wikipedia to get an idea.


wikipedia's Basic" special characters:

Additional French special characters:

Additional Spanish special characters:

We should let our translators edit this according to their local needs.


Related:
http://sourceforge.net/tracker/index.php?func=detail&aid=1185212&group_id=64258&atid=506848

Insert Wiki Link popup has scroll bars in IE7 messing up view

When inserting an 'internal link' the objects offered are limited to Wiki objects only. (WYSIWYG editor). It would be good to have other objects included also.

I posted this on the Features/Usability forum pn tw.o, but it seems to be coming down to a bug or a setting.

We've been wrestling with Internal Server Error 500 for several months. We are transferring the content of a static HTML site to a TW site.

At first, we thought it had to do with the length of documents or reserved words or special characters. All of that may still be true, but what I find after exploring the Web a little is that it has to do with script failure. Apache thinks something is screwy in the content being fed to it.

Most recently, I tried to get the TW sql module to work. I set up the DSN per the instructions on doc.tw.o , assigned permissions to a group,then created a test page. I inserted one line,

OPEN CURLY BRACE SQL CLOSE CURLY BRACE (db=>memberlist) SE (NO SPACE)LECT count(*) FROM members OPEN CURLY BRACE SQL CLOSE CURLY BRACE,

then hit Preview and got Error 500 immediately. (Obviously, I've substituted words for characters like the curly brace and space. I did that so I wouldn't get Error 500 when I up load this message. And, yes, I know "up load" is one word, but if I use one word, it is likely to fail.)

We have previously gotten the Error 500 message when words like 'up load' and 'se lect' (as noted above) were in the text of the page. When those words are removed or altered, the page up loads.

It tends to happen more often when pages are long (that may be psychological. You remember the BIG failures.) which, of course, just means the odds are greater that a reserved word is used, if that's the case.

When I tried to up load the above example to tw.o, it failed three times until I had all the curly braces and suspect words broken up. I know others are having this same issue. Here's chibaguy from tw.o on his experience up loading in response to my message. (I've edited for brevity)
---------------------
chibaguy on Fri 16 Nov, 2007 08:08 CET

I tried once to reply to your post and got the 500 error when I had "se lect" in the text (with no space), and then the submit went smoothly when the space was added. A few minutes later I submitted that test post, with "se lect" intact and it also went fine. Meanwhile I found 469 instances of the word at this site, including in wiki pages and forum posts, so obviously a lot of the time having "reserved words" in posts doesn't stop the submit.
...
I've also gotten the 500 error here trying to submit a post, once in a while, but waited a little while and then could submit exactly the same post with no error.
...
I rarely get the error at other Tiki sites I use pretty intensively, but am not sure if my pattern of use just avoids the pitfalls.

-- Gary
------------------------

ricks99 on tw.o leapt on the cut and paste scenario, offering that it might be a text encoding conflict. I've had it fail, as above, with directly entered content as well as pasted content. I'm on a Mac and our host is using *nix.

Note that I'm not saying some text encoding issue isn't a part of it. In fact, I kind of suspect there is more than one culprit.

When I get one of these errors, I start reducing the up load by halves, previwing a portion at a time, until I get failure. Once I get failure, I always get failure.

We've up loaded (copy/paste) pages of documents in which one line would cause the failure. Removing the one line makes it OK. Taking the suspect portion and the remaining text and putting it into a comment page works, too.

My suspicion is that there may be a combination of "suspect" words that crosses a threshold and drops the error message on us. Maybe there's a setup issue?

I'd really like to use the SQL plugin. It would solve several problems for us. Thanks,

Bill

------

This is the third in a series of "HOW DOES IT WORK" articles describing the various systems of the TD Vixens. The first two described the engine cooling and coach heating systems. This article will describe the engine fuel system.

By Tom Picking
ENGINE FUEL & ELECTRICAL

When I first got my Vixen it was hard to start. The problem got worse until I was afraid to go anywhere. I spent several weeks studying the system and talking to other owners about what might be wrong. I tried many "fixes" hoping they would solve the problem but nothing helped. I learned a lot about the system over those weeks with the help of several people and only after fully understanding "HOW IT WORKS" was I able to find and correct the problem. VIN 0050 is stock with 110,000 miles and starts easily even after being idle for weeks. Yours should, too!

The BMW engine's Bosch fuel injection pump, in my opinion, is a work of art! It is completely mechanical using no electricity (except for the fuel shut off valve) or electronics. It is a very complex system and adjustment or repair of the fuel injection pump should be left to professionals. But if we understand howthe total system works, we should be able to determine if the problem is in the pump or some other component of the system that we can fix ourselves.

In order for a diesel engine to start and run it needs three things: Air, fuel, and heat. It is also very important to make sure that no air can mix with the fuel until the fuel gets into the combustion chamber.
AIR AND HEAT

When the starter cranks the engine, air is sucked in and compressed by the pistons. When air is compressed, it gets very hot, hot enough to ignite fuel if it is present. On very cold days the engine and the air being drawn in are much colder making it difficult for the air to reach the temperature required for ignition. This is where glow plugs come in. They are actually small electrical heaters inside each combustion chamber. They look something like a spark "plug" and when turned on they get so hot they actually "glow". The glow plugs only come on during the initial start up sequence and the amount of time you should wait before trying to start the engine is determined by the engine electronics based on the temperature of the engine. Maximum ON time is about 15 seconds. The "WAIT TO START" light on the dash indicates the glow plugs are being commanded on and the engine should not be cranked till they have had a chance to do their job. If the glow plugs are not working, the engine will still start (except on very cold days) but only with increased cranking times.
AIR AND FUEL

Air in the fuel before it is injected into the engine is a bad thing. The injector pump must be able to develop very high pressure in order to force the fuel into the combustion chamber and if air is mixed with the fuel, this high pressure cannot be achieved.

The injector pump is actually two pumps in one. The first is a low pressure priming pump that floods the primarypump chamber. Any air in this chamber is forced out of a drain line at the top of the chamber along with excess fuel flow from the priming pump. This drainline is common with the drain lines connected to the injectors in each cylinder. If any of these lines leak while the engine is off air will enter the system and fuel will drain backward through the fuel line and empty the primary chamber of the injector pump. The result is hard starting (delayed while the priming pump is filling the primary chamber) but otherwise a normal-running engine.

If there is a leak in the fuel line or the fuel filter between the injector pump and the fuel tank, air will be drawn in by the suction of the injector pump and, depending on the amount of air, the engine may start but will not run correctly under load or high speed. As reported by Charles Rausch (TD 0106) in December's issue of Fox Prints, this same symptom can be experienced if there is a severe restriction in the fuel line such as a clogged fuel filter or a clogged fuel tank filler cap air breather vent.

You can inspect the fuel entering the pump by checking the clear (after 12 years mine is yellow) plastic line connecting the fuel filter and the pump. If you see bubbles in this line while the engine is running or cranking there is a fuel line problem. If you see a large bubble in the line after the engine has been off for several minutes, this is an indication of a drain line problem and that fuel is draining backwards through the fuel line to the tank. If you tap the line, with an indication of air in it, you can watch which side the air bubbles up. That will cut the investigation in half.

Between the tank and the injector pump is a fuel filter. The stock filter has a special manual priming pump built into the head of the filter. Turning the selector head of the filter pump to "RUN" bypasses the internal check valve and makes it easier for the engine injector pump to draw fuel. Turning the head of the filter pump to "PUMP" allows manual operation. The engine will run just fine with the filter pump selected to either position if all the rest of the system is in good condition. Diesel fuel is notorious for dirt and water. The fuel filter is your protection against dirty fuel.

After I learned all of the above, my Vixen still would not start! The problem was that it was not getting fuel because of an electrical problem!

The ignition switch mounted on the steering column (a standard GM part) has several electrical contacts that perform various functions depending on the position of the key in the ignition. One of the functions is to energize the fuel shutoff solenoid valve that allows the flow of fuel to the injector pump. One of the first things I did was to check the voltage to the solenoid valve with the key in the ON position, it was OK. What I didn't realize until several weeks later is that a different set of contacts energize this valve when the key is in the START position. These contacts were defective and when the key was in START and the engine was cranking, the solenoid valve was off and no fuel was available!!!!! This condition can be measured with a voltmeter which eliminates the guess work. A new ignition switch solved the problem.

((doc:InterTiki)) permits to share login, preferences and groups between various Tiki sites.

We need the Sister Wiki too!
http://www.wikimatrix.org/wiki/feature:SisterWiki
Continue discussion here: ((Sister Wiki))

((doc:backlinks)) are very cool. But what about backlinks from other sites?

We could use list from:
http://doc.tiki.org/External+Wikis


Related:
[wish2086|Backlinks between trackers and wiki pages (and maybe forums)]
[wish1768|Tracker plugin to get title and make link to tracker item]

{syntax type="tiki" editor="plain"}
It seems to be an error only by the first settings (creation) of a wiki page, maybe depending on the staging and approval system:

* Every time a new wiki page is created initially in the staging version the creators name is correctly shown under "created by" and "creator" (in the listing of the wiki pages and below the page in the collaborative-listing of creator and contributors).

* Then after approval

** the page description disappears (I mentioned this in another posting before) and

** the creator of the page is changed, I mean: __instead of the user's name (who created the page)__ now __there is shown the IP of the approver__.

* So

** below the page and in the page listing the IP (of the approver) is shown as creator,

** and in the history the "user" of the page and the "comment" are changed.

Please see the screenshots I attached, for better explanation of this. The page in the three screenshot was created by admin and approved by admin. But it's the same, if created by an user:

__Always the name of the creator of a wiki page is not correctly shown in each area (wiki page listing, below the page and in the history).__

* By edit of an existing page, this doesn't occure! - You see in the screenshot, that in the second and third version of the page there are correctly shown the "user" with his name and "comment" with an comment, that the page was approved by named approver.

If you try to name a page starting with "tiki wiki" (dash for space) tiki will see this as an action and refuse to comply.

IE: I tried "tiki wiki help" (spaces are replaced by dashes) and got the following error"
~pp~Action not found (help in wiki) (404)~/pp~

That’s a bit... ?

It is not possible using the HTML plugin or the wiki syntax to have bootstrap modals as explained at : https://getbootstrap.com/docs/4.0/components/modal/

The page turn black/faded and the modal is displayed below the modal-backdrop (without the modal id).

Note: I have the feeling it was possible in the past (19, 20, 21). May be it is a recent change that has been merged into Tiki 21.

{syntax type="tiki" editor="plain"}
A user with the right perms access to the Wiki list pages (tiki-listpages) and there can "copy" a page to a new page. (it should be called "duplicate" IMO)

The same user should be able to do it from a page itself with an item in the "More" or the "wiki actions bar" dropdown.

{syntax type="tiki" editor="plain"}
When a group, including anonymous, can view pages, the group can view the page listing at tiki-listpages.php.

Actually we switch to enable or disable the option for this at tiki-admin.php?page=wiki -> Page listing but it is quite radical. If the "Page listing" is disabled even "admin" doesn't have access anymore to the page listing.

It should be possible for a webmaster to decide which group can see the page listing and which cannot.

I suggest adding such permission.

The more button display should be controllable by admins without using css.
See : ... I can’t find the discussion using the forum search tools ?

As reported here:
https://bugzilla.mozilla.org/show_bug.cgi?id=398767

{THUMB(image=>img/wiki_up/2008-01-17_low-tech-image_picker_TikiWiki.jpg,url=#)}{THUMB}
{THUMB(id=13,url="show_image.php?id=13")}{THUMB}
{THUMB(id=16,url="show_image.php?id=15")}{THUMB}


Some ideas of nice links to have:

Thumbnail with link:
{img src=images/code.png}%%% {CODE()}
{THUMB(id=13,url="show_image.php?id=13")}{THUMB}
{CODE}


[tiki-upload_image.php|You can test some experimental stuff here] (upload a pic and see the suggested wiki markup to copy in a ((test)) page.)


Nelson Ko and Marc Laporte were planning to work on tiki at ((tw:TikiFestToronto)) but something else came up so it's still on todo list :-)

Sometimes, we end up with some strange characters in pages names (accents, punctuation, etc). While it generally works, people should keep URLs with simple characters (like in emails) for nice readable URLS.

For example:
((I know this is all wrong, but fear it might be right - Alain Désilets))

Full page mode would be quite important

** Need to evaluate usefulness with Alain Désilets
** LP says it's doable (from back-end perspective)

Coordinate with other work on:
http://wiki-translation.com/

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

Hi,

After upgrading my web site from tiki 7.0 to 7.2, I've noticed that the "View edit icons" (feature that show/hides the plugin edit icons) button has disappeared.

Regards,
Yannick

{syntax type="tiki" editor="plain"}
If a wiki page is RENAMED it no longer appears in the Last Changes list.

I've tested this against our own system [http://thereevesproject.org] running 4.3 (yes I know we need to upgrade) and also against 7.1 running over at opensourcecms.com. Suspect it applies to intervening versions as well.

On 4.3 module last_modif_pages does correctly continue to list the renamed page, using its new name. (This aspect not tested on 7.1)

If you use the plugin edit icon to edit a plugin on a page, after submitting the changes, the 'List Authors' setting for the page reverts to the default, losing whatever setting it had before.

To reproduce:

Have some pages with backlinks

Then, rename DOMpdf to dompdf and the backlinks to dompdf will be broken.

{syntax type="tiki" editor="plain"}
Hi,

!!!This problems concerns quite all table and forms (in tables or not) with fixedwidth themes.
This is the reason while it appear in so many functions.

!!!As for most of tables in many functions, with "twist" (no other style tested) the tables of the middle (C2) either overlap C3 or are behind C3 and sometimes C2. They just have a little part outside the 990px large (in twist as the width is written into css it can't be changed by prefs).

__~~#F00:The corresponding functions are then completely unusable.
~~__

Here I write this for the example elementary function "add an element to a structure" givin in screenshots joined documents

Three scrennshots proposed are :
#What a user see
#The limit of the div as shown by firebug
#The whole div zone hidden

{syntax type="tiki" editor="plain"}
After clicking "create new wiki page", i typed a name for this site containing a forbidden char (in this case "&"). I prompted this entry (not knowing this char is forbidden) to add content to this page.

the "invalid character" field popped up and forced me to rename the page. looked similar to the normal "rename page" input, but without a button to "save" the change.

unfortunately, the save button was also missing in the editor field for my new page and "previewing" the new site didn't change anything in this behaviour.

so in the end - content as well as the page were lost.

please add "save" buttons to this areas.

We already have categories, etc.

A user typo whilst creating a structure can create a new page which then isn't (easily) accessed.

Whilst creating a new structure and adding pages with aliases using the "Tree" feature, if hyphen space greater-than rather than simply hyphen greater-than is entered the new page is created without an alias but with a longer that expected page name.

For example
Test_01 -> Page1 creates new page called Test_01 and alias Page1 as expected.
But
Test_02 - > Page2 creates a new page called "Test_02 - > Page2" with no alias.

Accessing this page and removing it is challenging :-))

--(Can't currently create a show instance for you, no database connection available, but I can reproduce this on the demo 18x/system)--

Using the Structures "next page" button from page Test_01 causes a wiki error "Page not found" for "Test_02 - Page2" (sic without greater-than sign).

Likewise wikilink from toc generated on pages within the structure also results in "Page not found".

Adding the plugin listpages with options find="Test_0" to the root of the structure shows the pages as expected.

Note the wikilink URLs generated by toc and listpages are different, but wikilink from listpages also results in the same "Page not found error" for the same page "Test_02----Page2"