Category: Administration

Actually the site close page and message are partially custom, not translatable and use discutable mechanism (URL parameters).

See: https://tiki.org/forumthread77173-Translation-for-tiki-site-close-page-tiki-error_simple-php

And : https://tiki.org/Roundtable-Meeting-2021-07

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

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

---
We need a mechanism to assure:
* Message customisation
* Translation
* ...

Even if everything is down (php and database).
---

We don’t have a lot to do to achieve customisation and translation.
We need to have fields for:
* Retry (refresh ?)
* User
* Password
* Login (button)

I suggest as first step having those field for easy customisation translation (one language). Adding a link to the "page" displayed so it easy to integrate one from a theme.


Related:
* https://www.wpexplorer.com/wordpress-maintenance-mode-coming-soon/
* https://wordpress.org/plugins/coming-soon
* https://wordpress.org/plugins/disable-site/
* https://www.drupal.org/docs/user_guide/en/extend-maintenance.html

With jQuery, this would be nice.

A lot of people who install this aren't doing it via Fantastico and trying to change email settings to suit your hosting provider is a pain. Editing the php.ini isn't always wise either because what works for one app will break another. I know that you can copy the php.ini to the directory, but that's something of a security risk. There's a reason that the default php.ini is stored outside the web root directory.

I know that I see a lot of users posting on the TikiWiki forums with questions about configuring SMTP.

After updating a Tiki21 that is using SMTP Google server has sending email option, Google throw an error an email are not sent.

{CODE(caption="log to catch the previous Git version of a working Tiki")}
Bernard$ git log
commit d002513ebdbe3721cc701dd58a6b47da59233bed (HEAD -> 21.x, origin/21.x)
Merge: 34566b8ecf 4a68067e0b
Author: Bernard Sfez <me@xxxx.xxx>
Date: Sun Mar 22 16:29:39 2020 +0000
{CODE}

{CODE(caption="The error")}
Warning

Unable to send mail
Array ( [0] => 5.7.8 Username and Password not accepted. Learn more at 5.7.8 https://support.google.com/mail/?p=BadCredentials e5sm15280421wru.92 - gsmtp )
{CODE}

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

Currently in trunk, some JS code is adding to most of the control panels elements:
{CODE()}style="display: none;"{CODE}
causing them to be hidden after page completes loading.
Makes using admin control panels impossible.

I suspect something to do with the filtering of showing Basic / Advanced preferences got broken as a side-effect of the Bootstrap 4 transition. {sign user="luci" datetime="2018-05-01T13:49:22+00:00"}

Using the default PHP namespace separator :_: causes a PHP warning.

PHP (5.4.11) NOTICE (E_NOTICE):
File: ...\lib\prefslib.php
Line: 59
Type: unserialize(): Error at offset 0 of 3 bytes

The preference is set correctly.

Same problem occurs to ::

The problem occurs in 11.x, 12.x ... and I assume both before and after.

I am not sure why unserialize is called there in the first place

The Admin>General page has a default message which spells "maintenance" incorrectly: "Site is closed for maintainance, please come back later."

Hello Friends,

I am not a technical person. After I installed latest version of TikiWiki using Fantastico I went to Admin Area and when I finished some modifications in Login Configuration Page I was suddenly kicked out (logged out) but even after several tries I was not able to login again.

Because of this problem I removed my site: http://hub.cc completely. I downloaded the latest version from site: www.tikiwiki.org and re-installed it using my FTP clients. But unfortunately once again faced the same problem.

I therefore request you to please check my site and guide to me how can I Debug this issue!

Many thanks and best regards

Kamaal Makrani

-----

Ths Strasa theme does not seem to work properly.

The content is against the LHS of the sceen rather than in the middle and the menu is off the bottom of the pages.

We have just done the upgrade from 10.0 to 11.0

We have adopted the tikinewt theme instead but would rather go back to the Strasa if we could.

tiki-backup.php was like performing surgery on yourself. It can work but it's risky.

For some reason, svn update FAILS to update on show.t.o instance linked to dev.t.o bug tracker item

Example:
https://dev.tiki.org/tiki-view_tracker_item.php?itemId=5493

Click at svn update.
It doesn't seem to update the instance, which still is at
Last update from SVN (12.5): Sunday 17 of January, 2016 15:28:05 CET - REV 57249 (MyISAM)

(as seen on http://xavi-9794-5493.show.tikiwiki.org/tiki-admin.php?page=general )

and to check the bug fix we need to update to r57742

---
I believe it to be a server-side issue, the AJAX request returns with a "504 Gateway Time-out" error, will ask the sysadmins... {sign user="jonnybradley" datetime="2016-03-14T18:59:33+00:00"}
---
update, the server side issue is fixed - was a disk space issue that was caught by monitoring but I had to figure out a way to delete instances logically from the oldest ones that are linked to closed tracker items. There is however still front-end issues (it seems that I have to click more than once for the user feedback spinner to appear, which is weird as well as it seems I have to scroll down {sign user="koth" datetime="2016-03-14T12:18:33+00:00"}

Why does this get deleted:

cvs update: warning: templates_c/.cvsignore was lost
U templates_c/.cvsignore
cvs update: warning: templates_c/.htaccess was lost
U templates_c/.htaccess
cvs update: warning: templates_c/README was lost
U templates_c/README
cvs update: warning: templates_c/index.php was lost
U templates_c/index.php



2009-04-17 It's better for branches/3.0 but it still happens somethinges. (ex.: in temp) Need to be able to duplicate and solve.

2009-04-19 Should be ok now.

tiki-admin.php?page=gal tells me if GD or Imagick is installed. Nice.

But sometimes, it's installed, but it doesn't work as it should. To rule out that the problem is with Tiki, here is an example of a simple php to test GD in real life. It would be nice to add to tiki-admin.php?page=gal

{img src=images/code.png}%%% {CODE()}
<?php
header("Content-type: image/png");
$im = @imagecreate(110, 20)
or die("Cannot Initialize new GD image stream");
$background_color = imagecolorallocate($im, 0, 0, 0);
$text_color = imagecolorallocate($im, 233, 14, 91);
imagestring($im, 1, 5, 5, "A Simple Text String", $text_color);
imagepng($im);
imagedestroy($im);
?>
{CODE}

Settings → Users → ''Add or remove from a group'' option from the right-hand spanner

On a new Tiki it opens the "Change group assignments for selected users" modal which helps place the user in groups and set the default group. ''This is fine''.

On a Tiki with a lot of groups, the modal fails to show up and the javascript console reveals that Tiki tries to send the huge list of groups using method GET.
Unsurprisingly, this is met with « 414 Request-URI Too Long »
__This is not fine__ :-(

No show instance with hundreds of groups is necessary : I hope this can be fixed by changing the GET query into a POST.

I was unable to change the general preferences in the general administration form.

The reason is a naming collision between the cookie variable "style" and the name of the "Change Styles only" submit button. The consequence is that the code for changing style is run every time (because the "style" variable is always set).

The associative array $_REQUEST consist of the contents of $_GET, $_POST, and $_COOKIE.

{syntax type="tiki" editor="plain"}
A 50 is added into the url

{CODE()}
User: admin
Site: https://example.com/50 or more unsuccessful login attempts have been made. Your account has been suspended. Contact your site administrator to reactivate it.
{CODE}

When a new admin start setting up his Tiki he will likely put his own logo.

However there 0 control on the page or in the code code to limit the logo size but the 1170px width for the first container.
So if the admin pick a high resolution logo, it can use the 1170px width.

Result is not what is expected.
Having the "non power user" user in a situation he have to resize the logo and reupload it is "passé".
We should have some logical limit. (optional, changeable, whatever)

{syntax type="tiki" editor="plain"}
Tiki and Pear::Auth (LDAP) authentication doesn't work together in
version 3.0. A tiki local user can't log in anymore if the Pear::Auth
method is set, except admin.

On my Mac OSX I’m using MAMP (like LAMP and WAMP) with the relevant PHP version for each Tiki and I can switch version. To set the PHP version of the CLI in my terminal I add a command at ~/.bash_profile
{CODE(caption="To set PHP7.4.9 in the PHP-CLI")}
export PATH=/Applications/MAMP/bin/php/php7.4.9/bin:$PATH
{CODE}

This is working fine and Tiki is happy.
However tiki-check.php is locked on looking at the PHP installed on my computer (and not used by the CLI). Tiki check should be able to report version of the "used" PHP-CLI.

{img fileId="1467" thumb="box"}
{img fileId="1468" thumb="box"}

On a tiki25 using tiki-check.php I see a new error that wasn't there (I'm not checking this page everyday so I don't know when it has been introduced) about Server compatibility:

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

I believe it is a false alarm introduced with changes
Everything is green (I have some of the few and usual yellow but no red) and my Tiki is working just fine.

My system:
PHP: 7.4.33
MariaDB: 10.5.18-MariaDB-0+deb11u1
Tiki Version: 25.2 (from git)
Server: Debian GNU/Linux 11 (bullseye)
Web Server: Apache
CPanel: Virtualmin

See: ((Database Redact))

Although it would be nice, this doesn't need to be automatic on a cron job like {wish id=4665}

Amette explained that he copies data to a new database and that he executes various operations on this database.

So in essence, a cloning command is necessary for this. And a clone and upgrade is needed for show.tiki.org

If clone and redact was available on the command line, as a cron job, it could be an extra parameter to a clone command. See: ((Command-line tool|#console.php_clone))

And when we'd become quite confident with our script, we could even make the backups available to the public, like Wikipedia does. This is one more reason why fully automated would be nice.

http://en.wikipedia.org/wiki/Sanitization_(classified_information)

1st use of this new process is to supply redacted copies of tiki.org, doc.tiki.org and dev.tiki.org to Matthieu Hermet to work on NLP with ElasticSearch.

This tracker item could not be found

Use case:
*Manage many sites/domains with one Tiki installation
*"Park" all the domains on top of each other and get Tiki to send people to the right page depending on the domain.
*Common user base & permissions
*Theme control to provide different theme per section/category/page
*Could be different domain per language

Ideas
*Maybe domains could be links to categories. Put a page in a category and it gets its theme from theme control center
*Modules per domain
*If on page for domain X, force/rewrite URL to that domain
For example
^www.musicband1.com/introband1
www.musicband2.com/introband2
www.musicband3.com/introband3

So if I go to:
www.musicband1.com/introband2
I am redirected to
www.musicband1.com/introband1^


Limitation:
*pagename collision. Ex: domain1.com/intro = domain2.com/intro
*Single shared search engine
*Meta-tags will be shared

Also need to think about the Use Case where different workgroups want different domains. (A bit like *tikiwiki.org sites)

With new Tiki4 Workspaces, we could associate the domain as a preference.

What happens if a wiki page is in many categories, and they have different domain names. How would the priority work? Random? An order? Same idea as default group?



Related:
((WikiFarm))
((TRIM))
((Workspace))

As of Tiki 1.9.7, only Tiki admins (full admins) can manage Tiki menus. Yet, this is often something we may want to delegate to editors.

tiki_p_admin_menu would be very useful

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.