Category: Administration

To reproduce this bug:
1) Open Admin Groups Page
2) Number of Displayed Rows will default to 10
2) Change "Number of Displayed Rows" to 20
3) Hit Enter.
4) Additional Rows will display.
5) Add a Group.
6) Hit Save
7) Number of lines displayed changes back to 10.

Thanks for looking at this. dthacker.

{syntax type="tiki" editor="plain"}
On tiki29 a new fields parameter was added, see: https://doc.tiki.org/PluginList#Additional_parameter
This addition work well.

However I've noticed a visual issue when you use the debug template.
To reproduce, login and go to : https://dev.tiki.org/tiki-pluginlist_experiment.php

And test the following, __without__ the fields parameter. It should look as expected.
{CODE()}
{LIST()}
{filter field="tracker_id" content="5"}
{filter field="tracker_status" content="c"}
{output(template="debug"}
{LIST}
{CODE}

Adding the fields parameter and you will see all output object stacked one on each other.
{CODE()}
{LIST()}
{filter field="tracker_id" content="5"}
{filter field="tracker_status" content="c"}
{select fields="tracker_status"}
{output(template="debug"}
{LIST}
{CODE}

{syntax type="tiki" editor="plain"}
When accesing admin panel I get:

Warning: tempnam() [function.tempnam]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/httpd/wladcy.mage.pl/httpdocs:/home/httpd/wladcy.mage.pl/wladcy.mage.pl:/home/wladcy/:/tmp:/usr/share/pear:/var/lib/php/session/:/home/kloxo/httpd/script) in /home/wladcy/wladcy.mage.pl/lib/init/initlib.php on line 135

Related:
http://drupal.org/project/usage/

[wish1416|Reporting errors (to tikiwiki.org) system (like Firefox Talkback)]

"Orphan pages" is a VERY useful tool if your users are actively creating new pages. It helps the admin keep everything accessible and tidy and structured.

But to my regret, it is viewable to all, which is no good idea. Sometimes the admin may decide to not make a new page publicly viewable for some reasons, by simply not indexing it, but via orphan pages everyone can still see and view it, unless that particular page gets explicitly blocked.

Therefore I propose that orphan pages be either coupled to tiki_p_edit (only users with that right can make practical use of orphan pages anyhow (preferred) or have adjustable permissions of its own so I can limit it to registered users.

And btw, I my opinion orphan pages should not list the start page as orphan, because that one has to be orphan. Or make that adjustable as well...

Thanks
Hman

{flash type="url" movie="display540" width="633" height="571"}

Active Directory doesn't allow for anonymous searches of its structure. Instead, an username and password for an account with search access must be given when connecting.

I upgraded one of my subdomains from tikiwiki 3.3 to tikiwiki 4.1. After the upgrade admin can login but with an error message "Permission denied. You cannot view this page."

For other users it seems functioning alright. Only admin can do nothing.

Since recent update on Tiki23 when I have a "feature" error permission the feature is not displayed as it used to be and it show "%0"

{CODE()}
Required features: %0. If you do not have permission to activate these features, ask the site administrator.
{CODE}

{CODE(caption="on demo.tiki.org/trunk/")}ssh-w00ec615@dd29038:/www/htdocs/w00ec615/trunk$ php doc/devtools/prefreport.php > prefreport.csv
PHP Notice: Undefined variable: players in /www/htdocs/w00ec615/trunk/lib/wiki-plugins/wikiplugin_kaltura.php on line 46
ssh-w00ec615@dd29038:/www/htdocs/w00ec615/trunk$
{CODE}

(filed under Administration and All as I couldn't find Login/Authentication under Feature)

The authentication between Tiki and phpBB is no longer working.

This was originally reported for version 14.x - I am experiencing under version 20.x - making an assumption that all the versions inbetween have the same issue.

In terms of reproducing the issue:

* I have followed the steps needed to enable phpBB authentication via Tiki (from https://doc.tiki.org/phpBB-Authentication )
* I created a new user on the phpBB forum
* I was able to log in as the new user on the phpBB forum
* I then tried to log onto Tiki with that user, but I get a blank page (no error messages)
* logging back onto Tiki as admin, I do not see the same username that should have been created (meaning, no additional user has been created in Tiki as result)
* incidentally, I also tried to intentionally change the phpBB database credentials to something wrong, to see if it made any difference during the login process, it did not make any difference

In terms of Importance, it is difficult for me at this stage to appraise this since I am new to Tiki and it appears not many other people have reported this.
However, there are certain features in Tiki's own forum which may present challenges to forum managers (such as the current table structure for forum sections, as well as the inability to be able to sort forums arbitrarily, and lastly the ability to create sub-forums) so a solution such as phpBB would help. So I am classing as 7: it would stop some people to consider adopting Tiki because this feature is no longer working.

My versions:
* Tiki 20.x
* phpBB 3.2.7

Please see https://tiki.org/tiki-view_forum_thread.php?comments_parentId=56547 for details of original user who first logged the problem, as well as a screenshot of what I get in version 20.x

__Note:__ I am unable to use Tiki Show - I would need a phpBB database in there to demonstrate

If you need any other information please do not hesitate to get in touch.

My workplace as well as others I suppose blocks any url with "pics" in it. I have tried to change it myself to ïmg2" and found a few references in .php, .css and .js files but couldn't find many of them even searching the MySQL database.

Please consider changing the name of the pics directory to something else that wouldn't likely get blocked by corporate proxies.

Thanks!

{syntax type="tiki" editor="plain"}
Tiki has the option to interact with Google Analytics.

Now the first court rulings are there: Google Analytics directly violate the GDPR, therefore they are illegal throughout the EU. Fines are VERY heavy, so this must not be taken lightly. The fines range up to 20 million Euro or 4 percent of a year's turnover (sic! Not profit!), whichever is HIGHER.

Yes, Analytics is optional, and it's the decision of an admin, correct.

But IMHO Tiki should inform the admin when he/she activates this, that compliance with current law must be observed, and that Analytics can be (very) problematic in this regard. And to be on the very safe side, IMHO there should be a checkbox that spells out as confirmation "Yes, I am aware of the compliance issues imposed by this".

I suggest a plugin/mod configuration tool, where Admins can specify the __name of a plugin__ and a __list of parameters__ to be provided to the plugin. There is no way for Administrators to configure plugins. Every incantation of a plugin must specify all needed information. A configuration tool would allow control over all invocations of a plugin, or specifying non-public configuration details.

I believe that at present adding configuration options for a plugin requires the plugin to include code for admin pages. This tool would be available for use with any plugin with chooses to look for the passed parameters.

For example, a SHOWIMAGE plugin's configuration parameters could specify the default (or mandatory) image source to use, the default image size, and decoration options. By altering the configuration parameters the appearance of all invocations would be changed.

TW5.0beta1
http://dev.tikiwiki.org/Hello+World#To_create_a_new_plugin seems to be outdated. the plugin cannot be installed i the prescribed way.
By the time a php plugin file with a "wikiplugin_" prefix is saved to the lib/wiki-plugins folder, the Administration/Editing, plugins gives an empty pages. So do all the pages containing the new wiki plugin. Nothing is listed as a plug-in to be installed.

Two smaller corrections
* The sample code containing an extra '}' (last but one in wikiplugin_helloworld_info())
* The name to save the plugin must be lib/wiki-plugins/wikiplugin_helloworld.php instead of lib/wiki-plugins/wikiplugin-helloworld.php.

The plugin SQL can not retrieve data returned from a SELECT which is in a stored procedure. Stored procedures can be more secure than granting database read access to the TikiWiki server.

With MySQL, data can be retrieved from a stored procedure if the "mysqli" interface is used instead of "mysql", and if the client_multi_results flag is set before calling NConnect().

if( $dbdriver == 'mysqli' ){
$dbsqlplugin->clientFlags = 131074; // set client_multi_results
}

The iframe plugin page on tiki.org needs its own plugin approved:

http://doc.tiki.org/tiki-index.php?page=PluginIframe#Example

Preferences report reports "" when you run it on a multitiki based installation
{CODE()}
root@server:/var/www/tiki18farm# php doc/devtools/prefreport.php > prefreport.csv
root@server:/var/www/tiki18farm# cat prefreport.csv
Cannot initiate database. Tiki is not installed.
{CODE}

Or autodetect that it's on a multitiki install and prompt the user which tiki you want to have your report on (like with TRIM).
or just report them all, with suffixes corresponding to the multitiki names in the installation.

I tagged it also against "Community projects" after the discussions we had in the TAG meeting from today: https://tiki.org/20180808-TAG-Meeting.

On a fresh install, I enabled image galleries without realizing that neither GD or ImageMagick libraries had been installed. I was able to create a gallery and attempt an upload of images, which failed with a vague "Upload can not be processed". It was only after visiting the second admin screen (http://localhost/tiki-admin.php?page=gal) that I was able to see that the proper libraries were not installed.

Hello,

My english is very basic.

I am working into corporative network with proxy server conection. This conection required User and Password. But into TikiWiki's Proxy Configuration is not requiered.

For this reason I am not conect to download profiles from http://profiles.tiki.org/profiles.

I can not install de Profiles. How I can resolve it?

Help me,


Bye.

{syntax type="tiki" editor="plain"}
When i try to add{CODE(wrap="0",ishtml="0",ln="0",wiki="0",rtl="0",cpy="0")} {poll}{CODE} without id= to a user module in order to display random active polls (which i have previously created, activated and checked countless times) i get the following error when i edit the user module again. Using ckeditor, the sourcecode still shows {CODE(wrap="0",ishtml="0",ln="0",wiki="0",rtl="0",cpy="0")}{poll}. {poll id=n} {CODE}is working as it should.
{CODE(wrap="0",ishtml="0",ln="0",wiki="0",rtl="0",cpy="0")}
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


http://tiki.org"(external link) />

FehlerFehler


missing poll ID for plugin POLL


Close Window

{CODE}
// Removed some empty lines from the code view

The login settings page should be refactored to eliminate the presentation of unneeded configuration options.

Based on my research, it looks like this feature was supposed to be removed. See http://dev.tikiwiki.org/tiki-index.php?page=Hello+World&highlight=CSRF

dthacker

Since upgrading from LTS18.7 to 18.8, we are now unable to remove specific versions of a wiki page.
So whilst we can edit a page to hide profanity, obsenity and the like, we can not physically remove that version of the page.

This might also mean a site would be unable to fully comply with a "right to be forgotten" style request.

As an admin or suitably privildges user, go to page history, add tick in box for the version to be deleted. Then from the drop down menu at the foot of the page select Remove and click on the OK button.

The "Please confirm" pop up is shown and then click on Delete button.

The Error message "No version were selected. Please select one or more versions" is shown at the top of the History screen. The screen shows a selection tick against the version it's just failed to delete.

This bug seems closely related to at least two other recently filed bugs ....
[https://dev.tiki.org/item8065-Wiki-pages-cannot-be-deleted] and
[https://dev.tiki.org/item8128--No-users-were-selected-error]

Currently, there are four preference filters available in the Control Panel interfaces: "Basic", "Advanced", "Experimental" and "Unavailable".

As a user new to Tiki, I have on several occasions noted features that looked interesting, but which I have not enabled as I have subsequently found it is planned to deprecate them. In some cases this was obvious (e.g. a 'warning' icon with the deprecation message on hover next to the feature checkbox), in others it wasn't (i.e. I only found out about it from doc.t.o or related places).

On the assumption that it will help with planned deprecations if new installations don't enable and start using deprecated features, I would propose that a "Deprecated" preference filter be added, that relevant controls be assigned to it, and that it be disabled by default in new installations.

I understand the criteria for such might be controversial (indeed, I hope I'm not reigniting a heated discussion by posting this!) and so would understand if this is WONTFIXED. I also recognise that it is less appropriate for a new user to suggest criteria here than for those that have had Tiki installations for some time and/or are directly involved in development, which is why I haven't listed any in this initial report.