Category: 8.x

When we have the ability to close repetitive remarksboxes and save some user space it would be nice to allow users to tick a checkbox and opt-out to not show that remarksbox up on next page reload again...

{syntax type="tiki" editor="plain"}
Using the split-plugin in cooperation with the sort-plugin would run in some trouble.

In tiki5 the combination of this:

{CODE()}

{SPLIT()}

-=A=-
{SORT(sort->asc)}
((AC))
((AG))
((AA))
{SORT}

---

-=B=-
{SORT(sort->asc)}
((BB))
((BA))
{SORT}

---

-=C=-
{SORT(sort->asc)}
((CX))
((CD))
{SORT}

{SPLIT}
{CODE}


will work fine. You will get three columns and every entry is sorted and seperated fine.

After tiki5 this code-creation doesn´t work any more, the entry´s wouldn´t seperate by CR , only by SPACE. Anything is in one row.


This appears to be a basic parser problem in the way nested plugins are parsed. Same issue affects the FANCYTABLE plugin - see [http://dev.tiki.org/item4216]

When you try to access a wiki page which doesn't exist, Tiki offers you a list of similarly named pages, to search for that word, to create the page, etc.

__Good.__

When you try to access other contents in Tiki (articles, blog posts, etc.) that don't exist (either have been deleted, moved, not yet published, protected, etc.), you get a Tiki error message.

__Good as well.__


But what if you try an URL which is just not possible?

Ex.: If you migrated from another system to Tiki and you are still getting hits with the previous URLs?

Of course, you could check your access logs and add nice redirects. But how can we make this easier for site admins?


The bundled _htaccess file (which you need to rename .htaccess to make active) has an example line:
{img src=images/code.png}%%% {CODE()}
ErrorDocument 404 /tiki-index.php?page=Page+not+found
{CODE}

__This is good.__

Now, how could we use this to provide the Tiki admin with a top-x error pages? And thus, it would help to detect broken links, etc.

Could .htaccess include some configuration info from Tiki? So a Tiki admin could add configuration information without using FTP, all in Tiki, possibly with a secret "system" wiki page.

Great inspiration:
https://github.com/h5bp/html5-boilerplate/blob/master/dist/.htaccess

- Imagine you have a record with ten fields, but you only have a 'n' in the last column. It is not easy to select this column.
- Since each field contains a separate field, it suggests that each brings you to some different page.
- If one link of a record is active, the record is not selected.

{syntax type="tiki" editor="plain"}
The plugin section of the wiki help is listing the plugins aplhabetically based on their english name. When it is translated to another language the sorting remains based on the english name, it is quite confusing and looks a bit chaotic in other languages in my opinion. Is there a specific reason why the code here is written this way? If not, can this be fixed for Tiki 4? I dont know how to do it but would appreciate it :)

{syntax type="tiki" editor="plain"}
A wiki link in combination with a equation tag parses falsely.
This editor entry

{CODE()}((Fire weather index|{EQUATION()}FWI{EQUATION})){CODE}

displays the text output:

<img src="lib/equation/pictures/564a4dc730e638713aa76bb604088f85.png" alt="§7008f9602faf2722caf095a92ed8d624§" style="vertical-align:middle">§1a7e9ee2385aa1db7956a7f63689955f§

In HTML code:

<a class="wiki" title="Fire weather index" href="tiki-index.php?page=Fire+weather+index">&lt;img src="lib/equation/pictures/564a4dc730e638713aa76bb604088f85.png" alt="§7008f9602faf2722caf095a92ed8d624§" style="vertical-align:middle"&gt;§1a7e9ee2385aa1db7956a7f63689955f§</a>

The same in version 4.2 which is correct:

<a class="wiki " href="tiki-index.php?page=Fire+weather+index" title="Fire weather index"><img align="absmiddle" alt="FWI" src="lib/equation/pictures/04d4e88879dbf4f876f4b62fea56172f.png"></a>

{syntax type="tiki" editor="plain"}
Main bug.

A new user can't at all connect and get a blank screen.
This without crash.

If the user have an analyser he will find that tiki has sent this code

{CODE(caption="The page sent content")}<html><header</header><body></body></html>{CODE}

At the end of the installer when launch is run we can get a crash with an exception :

__"Session already opened"__

This has been reported since two years may be six times.

I have not made various test, so may be it depends of the context which is :

#Data upgraded from existing connection
#Run without inhibiting installer

This should not have effect. So I don't understand why others don't seem to observe the problem that I had always.

I need to run again directly index.

A proposal of enhancement :

If the tracker can be edited a tab can remain but why not display too the familiar standard edit icon used for content edit allowed ?

It is sure that not everything can be edited, but it is the edition of a tracker.

{syntax type="tiki" editor="plain"}
If I upload a large transparent PNG as an avatar which Tiki must resize, it ends up with a black background instead.

{syntax type="tiki" editor="plain"}
If one is typing in the login hover and mouses out, no more typing is entered until one hovers over the login again.

When trying to create a Wiki Link using the WYSIWYG, the auto page find doesn't work anymore making it almost impossible to link to another wiki page without knowing exaclty the page name

{img src="https://img.skitch.com/20111124-r2ai2a29x2xyriua1mu3a3996h.jpg"}

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.

We have a site_closed preference which is very useful.

However, this permits only the admins to access the site.


What if we want a read-only mirror?

It would be nice to a have a preference for this, along with a message to users: "This site is in read-only" and admins could change this message to indicate where the live site is.

Perhaps it could be interesting to check if the mysql user is "read only" as well...

This could also be interesting if a project is completed and we want to keep a site an an archive but no longer have any changes.

Things like tiki-logs, date of last login, etc. will need to considered.

Perhaps there could be a check: If current users has an edit/add permission (we'd have to make a list), then, he gets a warning that site is read-only (a message that the admin could change) and that any changes will be lost.

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

i've upgrade my site at 8 version.

now when i upload an image and i try to use with img placeholder appear the error "file is not an image"

i read that is couse by Ajax uploader, indeed i've activated this feature recently.
so i 've unactiveted this feature but the uploader is still in Ajax.

can anybody help me?

The tabs in the administrative interface use an onclick to run some AJAX code to change the interface. The problem is that they don't work in Chrome 17. They seem to work fine in Chrome 16.

More strangely, the method signatures of the tikitabs function actually appears quite different between the two browsers.

On Chrome 17 it is


function tikitabs(focus,max,ini) {
var didit = false, didone = false;
if (!ini) {
ini = 1;
}...

function tikitabs( focus, tabElement) {

The problem appears to be that the ini variable is not set, so it we set the ini to 1, then it skips down all the way to if (didone && ...) which gets bypassed, and we exit right away.

Why do you have different code for different versions of the same browser?

In 6.1 I successfully used this code:

{CODE()}{FANCYTABLE(colwidths="10%|7.5%|7.5%|7.5%|7.5%|7.5%|7.5%|7.5%|7.5%|7.5%|7.5%|7.5%|7.5%",colaligns="center",colvaligns="middle")}2011|{FILE(fileId=602)}Jan{FILE}|{FILE(fileId=603)}Feb{FILE}|{FILE(fileId=626)}Mar{FILE}|{FILE(fileId=625)}Apr{FILE}|{FILE(fileId=627)}May{FILE}|{FILE(fileId=624)}Jun{FILE}|{FILE(fileId=629)}Jul{FILE}|{FILE(fileId=630)}Aug{FILE}|{FILE(fileId=631)}Sep{FILE}|{FILE(fileId=632)}Oct{FILE}|...|...{FANCYTABLE}{CODE}

In 8.1 it now renders this result:

2011|[tiki-download_file.php?fileId=602|Jan~</td> <td class="odd" style=" width; background-color:"> 7.5%;">body2~Feb~</td> <td class="odd" style=" width; background-color:"> 7.5%;">body4~Mar~</td> <td class="odd" style=" width; background-color:"> 7.5%;">body6~Apr~</td> <td class="odd" style=" width; background-color:"> 7.5%;">body8~May~</td> and so on...

If I replace all but one instance of PluginFile the results are OK. If I add a second instance the results are as shown above.

{syntax type="tiki" editor="plain"}
In tra.php (8.1) it is necessary to check if an entry exists, the function used is always "getOne".

Unfortunately the instruction used {CODE()}! $tikilib->getOne(....){CODE} seems to return always true and generated the crash.

{syntax type="tiki" editor="plain"}
After 8.1 installation, I need a long time to be able to login as admin (not tested till now for other, two many problems to solve, test are programmed).
I was upgrading data from 7.2.

In fact the lonely way needs all these steps :
- clear all local cookies
- clear caches of server (temp/cache; module/cache)
- reinit as new (tiki.sql and some complements as the length of passw is we don't change the admin pass, no object, the SQL import file reset admin user and checks admin configuration)

Then when you login admin admin you are normally asked to set a new password, as for new installation. Everything seems OK, it is not true.
!!!~~#F00:__If you quit the browser you will be reconnected automatically even though "you have not checked remember me".
__~~
!!!~~#F00:But if you quit~~, for example to login for test with another login (the reason why for dev I don't check remember me) ~~#F00:and try to reconnect you get __"Invalid login or password"__ ~~

No other solution than a full reinit of admin login.
__
I checked :__
*clear local cookie alone : no result
*clear only tiki caches : no result
*clear cookies and cache (the db data are good for admin identification) : no result
*clear cookies, caches, reset admin as new install : OK

{syntax type="tiki" editor="plain"}
The default value for styles which supports "fixedwidth" parameter title "layout... " is 990px.

This option is useful and should be included in a module (I will do when if will function globally). Depending of the job done 990px on a 1920 is often a straight workplace.

If it is activated and you set any value you will get as the option "fullwidth".

This option make a wrong calculus of the real available width (a problem with js functions and margins) and generate a larger layout that the width of the display device.

Hi,
with 8.1 (and before) a __fixedwidth style__ (default 990px) like twist, __when it has to display a list like "wiki pages" overlaps the center column outside the layout of 450px.__

What do you think of this ?
Do any solutions have been studied ?
Do anybody works on this problem ?

The function has "no error bug" but it is not a professional way, a tester said to me whoa !!! you are going to try to propose this...

!!Working on :

Several solutions can be studied and combined :
# __embed these "tables" into tables__ so that they can't overlap but have hscroll (with all fields for selection). This is technically valid but __not at all sufficient because it is unusable__ quite heavy... but can be useful to have studied for later
# Add table with a minimum of 9 cells :
** Title and fields which fits the center column (col2) on span 2 c
** Empty
** second tr :
*** The title of element
*** content table with span 2 c and hscroll
** third tr
*** Footer span 2c (width of col2
*** Empty
# Cut the bottom of middle (col1,2,3) overlapping centered and use 100% width of screen, with automatic hscrool if too large with standard browser zooming
# The same hiding the "middle" (basic col 1,2,3) : needs to display the header with 100% width, and a new content header (enhance all styles to be able with good reliability to hide cols - a good check).
# use solution of "embed table" but with a "button to swap" to full width layout fitting the width of the screen
# option for automatic swap to full width when large tables are displayed
# swap fullscreen for tables described above
~~#090:
!!Waiting for ideas and project, thanks
~~

{syntax type="tiki" editor="plain"}
After a search (general by text) the beginning of text which is displayed is not decoded-re-encode for the context.
On the screenshot joined you can see parts of text with tiki tag (!! for h2), HTML tags, problem of encoding UTF8 probably or old text not re-encoded (not yet checked).

{syntax type="tiki" editor="plain"}
(Not yet checked for trunk)

After running installer with upgrade we get the message "Invalid database run installer..."

Running installer don't changes anything to database, but the message is still displayed.
It is a consistency "deadlock by soft".

The lonely thing generated by installer is a reset which needs to reset manually the admin account and clear all caches and cookies (see #4066 admin login problem).

~~#090:!!!Going on 12/06/2011~~

I need to check the soft.

The message is sent by "installer" $installer instance of class installer in installib
It checks before the validation of patches on db using $installer->recordPatch($patch) for each one.
recordPatch function in installer records the patch into tiki_schema as done with his full date.

The concerned (got by a var_dump) patch is "20110904_shoutbox_def_tweetid_tiki"
is not into the tiki_schema table.
So the test functions, but the tiki-install failed to make this patch on another version OK, as it is defined.

__~~#F00:When it runs now (installer at 8.1 level) it don't tries to make the upgrade. This is the deadlock.
__What is done if an old patch is not there !!!__

More there is no report at all.~~__

As the title describes :

In the panel of a tracker (Bugs and wishes tracker on dev.tiki.org) the tab title for "comments" don't gives any information if exists comments, while the numbers of uploads of files have the number of uploads.
It should be a progress to see into tabs headers if a tracker have generated and how many comments and with a symbol (stars ?) the volume of comments


This concerns tiki version 8.x and site dev.tiki.org