[Tikiwiki-users] Cache in modules admin

[Patrick Van der Veken <patrick@ku...>]

What is the cache parameter used for in the Assign Modules screen? I can'=
t get=20
it to accept anything other than 0.

Regards,
--=20
Patrick Van der Veken
KUDOS BVBA - Baan/UNIX Consultancy
patrick_at_kudos.cx - patrick_at_baanboard.com
http://www.kudos.cx - http://www.baanboard.com
--
Sending unsolicited commercial e-mail to this account incurs a fee of
500 EURO per message, and acknowledges the legality of this contract

[Tikiwiki-users] Cookies - self-made menu forgets folding state

[Oliver Scheck <oliver.scheck@me...>]

Hi everybody,

our self-made tiki menu suffers from state amnesia. As I understand the 
folding state is persisted in cookies. I see it in the standard menue - 
which works fine - , I see the javascript code (setCookie()) there, but 
I don't see in out menu.

The brower is allowed to accept cookies, so that I can rule out as a 
source of trouble. Does that have something to do with settings? Or is 
that a bad template, where the respective javascript code comes from.

Thanks for help
Oli

[Tikiwiki-users] Error when sending pages

[Patrick Van der Veken <patrick@ku...>]

Hi,

Does anybody know why this error is happening? (Tiki 1.6.1):

Warning: fsockopen() [function.fsockopen]: php_hostconnect: connect faile=
d in=20
/opt/baanportal/web/tiki/lib/xmlrpc.inc on line 413

Warning: fsockopen() [function.fsockopen]: unable to connect to localhost=
:80=20
in /opt/baanportal/web/tiki/lib/xmlrpc.inc on line 413

Regards,

--=20
Patrick Van der Veken
KUDOS BVBA - Baan/UNIX Consultancy
patrick_at_kudos.cx - patrick_at_baanboard.com
http://www.kudos.cx - http://www.baanboard.com
--
Sending unsolicited commercial e-mail to this account incurs a fee of
500 EURO per message, and acknowledges the legality of this contract

[Tikiwiki-users] Re: [Tikiwiki-devel] Poll before changing

[Luis Argerich <luis@fu...>]

Yap we can provide a
"blog calendar" module
and a
"mini-calendar calendar" module

And admin can choose which one he wants to use in his site.

Very good idea.

----- Original Message -----
From: "Marc Laporte" <marc@...>
To: <tikiwiki-devel@...>; "'tikiwiki-users'"
<tikiwiki-users@...>
Sent: Tuesday, May 27, 2003 12:48 PM
Subject: RE: [Tikiwiki-devel] Poll before changing


> Hi!
>
> This behavior seems to be used mostly for blogs. Since we will no doubt
> attract/convert many blog sites, maybe we can keep it and call it blog
> calendar?
>
> M ;-)
>
> --
> Marc Laporte
>
>
> -----Original Message-----
> From: tikiwiki-devel-admin@...
> [mailto:tikiwiki-devel-admin@...] On Behalf Of Luis
> Argerich
> Sent: May 27, 2003 9:00 AM
> To: tikiwiki-devel@...; tikiwiki-users
> Subject: [Tikiwiki-devel] Poll before changing
>
> Hi list,
>
> I'd like to poll the list before introducing some changes that may change
> how some things before 1.7, since we really want to keep backward
> compatibility and prevent unexpected changes to our users I prefer to ask
> before.
>
> - Mini-calendar behaviour
>     Currently it is used to display articles, and other objects as they
were
> in a previous date (or future date if admin). Seems like nobody is using
> this and the calendar is generating some confusions articles not
appearing,
> etc.
>     Proposed change: The mini-calendar will be used to control the tiki
mini
> user calendar a link in a day will take the user to that they in his mini
> calendar. A control MIGHT be added in the articles listing and others to
see
> articles and other objects in a previous or future date
>
> If someone has a reson to keep the old behaviour please raise your hand
and
> we'll listen.
>
> Luis.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> Tikiwiki-devel mailing list
> Tikiwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> Tikiwiki-devel mailing list
> Tikiwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>

[Tikiwiki-users] RE: [Tikiwiki-devel] Poll before changing

[Marc Laporte <marc@pi...>]

Hi!

This behavior seems to be used mostly for blogs. Since we will no doubt
attract/convert many blog sites, maybe we can keep it and call it blog
calendar?

M ;-)

--
Marc Laporte


-----Original Message-----
From: tikiwiki-devel-admin@...
[mailto:tikiwiki-devel-admin@...] On Behalf Of Luis
Argerich
Sent: May 27, 2003 9:00 AM
To: tikiwiki-devel@...; tikiwiki-users
Subject: [Tikiwiki-devel] Poll before changing

Hi list,

I'd like to poll the list before introducing some changes that may =
change
how some things before 1.7, since we really want to keep backward
compatibility and prevent unexpected changes to our users I prefer to =
ask
before.

- Mini-calendar behaviour
    Currently it is used to display articles, and other objects as they =
were
in a previous date (or future date if admin). Seems like nobody is using
this and the calendar is generating some confusions articles not =
appearing,
etc.
    Proposed change: The mini-calendar will be used to control the tiki =
mini
user calendar a link in a day will take the user to that they in his =
mini
calendar. A control MIGHT be added in the articles listing and others to =
see
articles and other objects in a previous or future date

If someone has a reson to keep the old behaviour please raise your hand =
and
we'll listen.

Luis.



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Tikiwiki-devel mailing list
Tikiwiki-devel@...
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

[Tikiwiki-users] Poll before changing

[Luis Argerich <luis@fu...>]

Hi list,

I'd like to poll the list before introducing some changes that may change
how some things before 1.7, since we really want to keep backward
compatibility and prevent unexpected changes to our users I prefer to ask
before.

- Mini-calendar behaviour
    Currently it is used to display articles, and other objects as they were
in a previous date (or future date if admin). Seems like nobody is using
this and the calendar is generating some confusions articles not appearing,
etc.
    Proposed change: The mini-calendar will be used to control the tiki mini
user calendar a link in a day will take the user to that they in his mini
calendar. A control MIGHT be added in the articles listing and others to see
articles and other objects in a previous or future date

If someone has a reson to keep the old behaviour please raise your hand and
we'll listen.

Luis.

Re: [Tikiwiki-users] Articles not listing

[Patrick Van der Veken <patrick@ku...>]

On Tuesday 27 May 2003 01:38, jordane@... wrote:
> Hi there, I just got tikiwiki 161 installed and working, but I'm having=
 a
> small problem. I am running MySQL 4.0xx and everything seems to be fine=
,
> but when I create a new article it wont list in the CMS home page. In f=
act
> its just blank in the CMS homepage. The menus are still on the side and=
 all
> that, but the middle is just blank. Now I check the "submitted articles=
"
> part and there's no articles waiting to be submitted, and I check the
> database with phpMyAdmin, and the articles that I wrote are definatly i=
n
> there. So maybe tiki's not pulling the articles out properly.
>
> thx
> Jordan

A similar thing happened to me. In my case it had to do with the use of d=
ates.=20
If you are using the mini-calendar then Tiki won't list the article if it=
 has=20
been published in the 'future'. Try creating an article dated 'yesterday'=
=2E

Regards,
--=20
Patrick Van der Veken
KUDOS BVBA - Baan/UNIX Consultancy
patrick_at_kudos.cx - patrick_at_baanboard.com
http://www.kudos.cx - http://www.baanboard.com
--
Sending unsolicited commercial e-mail to this account incurs a fee of
500 EURO per message, and acknowledges the legality of this contract

Re: [Tikiwiki-users] PhpWiki import

[Bob Apthorpe <apthorpe+tikiwiki@cy...>]

Hi,

On Tue, 27 May 2003 16:46:45 +1200 "Rasheed Abdal-Aziz"
<hypergee@...> wrote:

> Thank you for your reply Bob - I will get onto it tonight. I have a concern,
> we have multiple phpwiki's running.. (clients, admin, knowlege base) and
> these will all need to be brought in :/  So firstly i need to see if tiki
> supports access rights to different sections of the wikki, and if i can
> indeed import all three without clobber

I'd be a happy person if I could find a wiki that gave users their own
namespace. I know that goes against the whole "peace, love, & wiki"
viewpoint but unless you only have three users in a cloistered
environment, you need access control and namespaces. We've tried faking
around it by prefacing wiki pages with our initials but that messes with
the the wiki's ability to detect links, defeating the whole point of a
wiki. I'm not sure there's a good solution to this (though I haven't
done any research in a while either...)

> I'll let you all know how i go

Before you do, a quick look at the code suggests a simple fix:

Change line 90 of tiki-import_phpwiki.php from

  $part["body"]=preg_replace("/\[([^\|]+)\|([^\]]+)\]/","(($1|$2))",$part["body"]);

to

  $part["body"]=preg_replace("/\[([^\|]+)\|([^\]]+)\]/","(($2|$1))",$part["body"]);

Also, IIRC Tiki is a bit more sensitive to spaces so you may want to
make these changes (untested) instead:

87,90c87,90
<         $part["body"]=preg_replace("/ (http:\/\/[^ ]+) /"," [$1] ",$part["body"]);
<         $part["body"]=preg_replace("/\[(http:\/\/[^\]]+)\]/","{img src=$1}",$part["body"]);
<         $part["body"]=preg_replace("/\[([^\|\]]+)\]/","(($1))",$part["body"]);
<         $part["body"]=preg_replace("/\[([^\|]+)\|([^\]]+)\]/","(($1|$2))",$part["body"]);
---
>         $part["body"]=preg_replace("/ (https?:\/\/\S+) /"," [$1] ",$part["body"]);
>         $part["body"]=preg_replace("/\[\s*(https?:\/\/[^\]\s]+)\]/","{img src=$1}",$part["body"]);
>         $part["body"]=preg_replace("/\[\s*([^\|\]]+)\s*\]/","(($1))",$part["body"]);
>         $part["body"]=preg_replace("/\[\s*([^\|]+)\s*\|\s*([^\]]+)\s*\]/","(($2|$1))",$part["body"]);

Notes: \S is a more robust version of [^ ]; the scattering of \s* should
strip out any extraneous spaces in the links. Also, I'm not sure if
anyone references stuff via https but it costs almost nothing to support
them if they do.

Also, sorry about bouncing mail from hypergeek.com.au from cynistar.net;
mail.hypergeek.com.au = ns2.webtrader.com.au = 216.110.37.234 which is
listed as an open relay with ORDB (within the last 2 days.) See
http://ORDB.org/lookup/?host=216.110.37.234 and
http://openrbl.org/ip/216/110/37/234.htm for more info. It appears
you're running IMail which ships as an open relay, though the fix should
be pretty simple - see
http://www.mail-abuse.org/tsi/ar-fix.html#ipswitch or
http://www.ipswitch.com/Support/IMail/guide/imailug7.1/Chapter%209%20security3.html

hth,

-- 
Bob Apthorpe

RE: [Tikiwiki-users] PhpWiki import

[Rasheed Abdal-Aziz <hypergee@hy...>]

Thank you for your reply Bob - I will get onto it tonight. I have a concern,
we have multiple phpwiki's running.. (clients, admin, knowlege base) and
these will all need to be brought in :/  So firstly i need to see if tiki
supports access rights to different sections of the wikki, and if i can
indeed import all three without clobber

I'll let you all know how i go


-----Original Message-----
From: tikiwiki-users-admin@...
[mailto:tikiwiki-users-admin@...]On Behalf Of Bob
Apthorpe
Sent: Tuesday, 27 May 2003 3:29 p.m.
To: tikiwiki-users@...
Subject: Re: [Tikiwiki-users] PhpWiki import

-- snip --

Re: [Tikiwiki-users] PhpWiki import

[Bob Apthorpe <apthorpe+tikiwiki@cy...>]

Hi,

On Tue, 27 May 2003 14:33:24 +1200 "Rasheed Abdal-Aziz"
<rasheed@...> wrote:

> Hi there list..
> 
> In the manual it says:
> 
> The format used to import and export Wiki pages in Tiki is compatible
> with the PHPWiki system so you can import pages from PHPWiki or from
> other Tiki systems. A link called _Wiki import dump_ can be used to
> import pages.
> 
> But I cannot find it anywhere in the app.. Am I missing something obvious?

It's not completely obvious...

> BTW, Tiki 1.6.1 - download not cvs.

Expand "Admin (click!)" and it's the link 4th from the bottom, between
"Referer stats" and "phpinfo". The link should look like:

http://www._your_domain_here_.com/tiki/tiki-import_phpwiki.php

I've used it, it works but not very well (my bad for not mentioning this
or suggesting a fix earlier; I've been busy.)

If you're importing pages from phpwiki, there are different options to
use if you're importing from a zip snapshot (only the most recent
version of each wiki page) or zip dump (all archived versions.)

The easiest method is to import from a zip snapshot and check Y on both
options:

Overwrite existing pages if the name is the same: [Y/N]

Previously remove existing page versions: [Y/N]

I had trouble importing from a zip dump where wiki pages were imported
in reverse chronological order, meaning older versions overwrote newer
versions.

The other major problem once I sorted all this out was that phpwiki's
link syntax conflicts with tiki's syntax:

phpwiki: [ display term | WikiPageName ], e.g.:

  [ class topics | ClassIdeas ]

tiki: (( WikiPageName | display term )), e.g:

  (( ClassIdeas | class topics ))

Unfortunately, tiki-import_phpwiki.php doesn't take this into account, converting
  
  [ class topics | ClassIdeas ] -> (( class topics | ClassIdeas ))

which is completely broken and a pain to manually undo if you're
importing a lot of pages. To be fair, it's probably a simple fix in the
import code. I haven't had time to dig into it to see how difficult it
is to fix.

I like phpwiki for its simplicity[1] and ease of setup but it doesn't
seem to be actively developed. I'm still trying to get my head around
tiki, especially access control. That tiki imports phpwiki content at
all amazes me so don't take my comments as too critical.

-- 
Bob Apthorpe

[1] I set up twiki first. I'm sure twiki is a much better wiki than
phpwiki, with many more features, more active development, better
back-end version control, etc. When I first set it up I was not a wiki
user, didn't really understand the power of wiki tools or how one used
them most effectively; a total wiki n00b.

Twiki bludgeoned me with a wall of busy, self-congratulatory kruft and
no simple instructions on how to actually _use_ the system. The
welcome-to-our-elitist-cult default installation so thoroughly turned me
off that I installed phpwiki instead. And a year or so later after
building a sizable wiki, I miss some of the features that are in other
wikis, including twiki, and I don't relish the thought of manually
converting the pages to another system that's actively developed, nor do
I have a lot of spare time to actively develop phpwiki. Tiki looks like
it does what I need and a lot more; it's been surprisingly easy to
configure considering all the options and functions.

[Tikiwiki-users] PhpWiki import

[Rasheed Abdal-Aziz <rasheed@si...>]

Hi there list..

In the manual it says:

 The format used to import and export Wiki pages in Tiki is compatible wi=
th
the
PHPWiki system so you can import pages from PHPWiki or from other Tiki
systems. A link called =93Wiki import dump=94 can be used to import pages.


But I cannot find it anywhere in the app.. Am I missing something obvious=
?

BTW, Tiki 1.6.1 - download not cvs.

Yours,
	Rasheed Abdal-Aziz

[Tikiwiki-users] Articles not listing

[<jordane@te...>]

Hi there, I just got tikiwiki 161 installed and working, but I'm having a small 
problem. I am running MySQL 4.0xx and everything seems to be fine, but when I 
create a new article it wont list in the CMS home page. In fact its just blank 
in the CMS homepage. The menus are still on the side and all that, but the 
middle is just blank. Now I check the "submitted articles" part and there's no 
articles waiting to be submitted, and I check the database with phpMyAdmin, and 
the articles that I wrote are definatly in there. So maybe tiki's not pulling 
the articles out properly.

thx 
Jordan

[Tikiwiki-users] Articles not listing

[<jordane@te...>]

Hi there, I just got tikiwiki 161 installed and working, but I'm having a small 
problem. I am running MySQL 4.0xx and everything seems to be fine, but when I 
create a new article it wont list in the CMS home page. In fact its just blank 
in the CMS homepage. The menus are still on the side and all that, but the 
middle is just blank. Now I check the "submitted articles" part and there's no 
articles waiting to be submitted, and I check the database with phpMyAdmin, and 
the articles that I wrote are definatly in there. So maybe tiki's not pulling 
the articles out properly.

thx 
Jordan

[Tikiwiki-users] Re: [Tikiwiki-devel] Tiki 1.6.1 released

[Luis Argerich <luis@fu...>]

Updated today in the SF site and home page.
Congratulations to Flo, Ross, Oliver, Ricardo and Joan for this release!
Specially to Flo who even did the whole pain-in-the-### release process.

Now let's head for 1.7!

----- Original Message -----
From: "Flo G." <flo@...>
To: <tikiwiki-users@...>; "Tikiwiki"
<tikiwiki-devel@...>
Sent: Sunday, May 25, 2003 10:41 PM
Subject: [Tikiwiki-devel] Tiki 1.6.1 released


>
> Hi Lists,
>
> Tiki 1.6.1 has just been released. It's a pure bugfixing release.
>
> The ones i remember are:
>
> * [FIX] many things in Image galleries that made life hard
> * [FIX] Error in install script (fgets parameter)
> * [FIX] bug in page history module
> * [FIX] missing addslashes
> * [FIX] renaming structure doesn't work
> * [FIX] sessions are not counted
> * [FIX] many many more i don't remember :-)
>
>
> Have fun.
>
> Flo
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> Tikiwiki-devel mailing list
> Tikiwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>

[Tikiwiki-users] Too many confused EOL/EOF characters in 1.6, 1.6.1

[Bob Apthorpe <apthorpe+tikiwiki@cy...>]

Hi,

There seems to be some confusion which format the Tiki files should be -
DOS or unix. I don't really care[1] which as long as it's consistent and
easily convertable. Sadly, it's not trivial to convert the files because
of mixed and inconsistent EOF and EOL characters. I use the following to
do a bulk 'dos2unix' on the tiki distribution:

find . -type f -print | xargs file | egrep LF | sed 's/:.*//' | \
egrep -v lang | xargs recode ibmpc..lat1

(note: using recode on tiki/lang seemed counter-productive...)

This fails on ~160 or so files because of mixed line endings (lots of
stray ^Ms in otherwise normal unix text files.) Here's an example:

$ recode ibmpc..lat1 tiki3/tiki-userfiles.php
recode: tiki3/tiki-userfiles.php failed: Ambiguous output in step `CR-LF..data'

Those get fixed with

find . -type f -print | xargs file | egrep LF | sed 's/:.*//' | \
egrep -v lang | xargs perl -pi.bak -e 's/\s*^M//'

where ^M (ctrl-M) is one character (ctrl-V to the rescue...)[2]

Depending on how much control you have over the CVS archive, you can
automate the EOL conversion process (among other things) in the
commitinfo file - see
http://cvsbook.red-bean.com/cvsbook.html#The_commitinfo_And_loginfo_And_rcsinfo_Files

I know it's a niggling concern, but could this be fixed for 1.6.2 or
1.7?

I've had php code fail before due to broken line endings and I've set up
CVS repositories to fix EOL issues -- hopefully this will help.

-- Bob

[1] Actually, I do. I'd prefer unix format because it simplifies my life
:) Seriously though, it might be useful to pick the one used most tiki
users, or ideally, provide a tarball of unix-formatted files for unix
geeks and a zip file of DOS-formatted files for those saddled with
Windows.

[2] The '-pi.bak' flag implies a 'while(<>) { ... }' loop around the
perl code (-p), puts the results in the original file after renaming the
original with a '.bak' extension (-i.bak) The net effect is bulk
in-place editing with backups.

[Tikiwiki-users] Error: function.file-exists

[Pieter Jansen van Vuuren <pieter@ps...>]

I get the following error when opening tiki-index.php 
 
 Warning: file_exists() [function.file-exists.html
<http://www.themarquee.co.za/phpmanual/function.file-exists.html>; ]:
Unable to access templates/styles/elegant/styles/elegant/tiki.tpl in
/data/web/acme/data/web/tiki/setup.php on line 55

At the top of the page and then when I log in as the admin I get
 
Warning: file_exists() [function.file-exists.html
<http://www.themarquee.co.za/phpmanual/function.file-exists.html>; ]:
open_basedir restriction in effect.
File(/home/web/acme/data/web/php/plugins/compiler.popup_init.php) is not
within the allowed path(s): (/home/web/acme/data) in
/data/web/acme/data/web/tiki/Smarty/Smarty.class.php on line 2618

Warning: file_exists() [function.file-exists.html
<http://www.themarquee.co.za/phpmanual/function.file-exists.html>; ]:
open_basedir restriction in effect.
File(/home/web/acme/data/web/php/plugins/block.popup_init.php) is not
within the allowed path(s): (/home/web/acme/data) in
/data/web/acme/data/web/tiki/Smarty/Smarty.class.php on line 2618

 ETC.......
 
Can anyone tell me what i'm doing wrong! 
 
I followed  Appendix B: Installing tiki under safe_mode in the manual,
although I have placed my tiki in a folder called tiki, do I can first
test it and make sure it works!
 
Thanks
 
Pieter

[Tikiwiki-users] Error Creating Tables

[Pieter Jansen van Vuuren <pieter@ps...>]

Hi,
 
I'm getting the following error when trying to run the tiki.sql
 
Warning: MYSQL error: DB Error: syntax error in query:
create table users_users( userId integer(8) not null auto_increment,
email varchar(200), login varchar(40) not null, password varchar(30) not
null, provpass varchar(30), realname varchar(80), homePage varchar(200),
lastLogin integer(14), currentLogin integer(14), registrationDate
integer(14), challenge char(32), pass_due integer(14), hash char(32),
created integer(14), country varchar(80), avatarName varchar(80),
avatarSize integer(14), avatarFileType varchar(250), avatarData
longblob, avatarLibName varchar(200), avatarType char(1), primary
key(userId) );
in /data/web/themarquee.co.za/data/web/tiki/tiki-install.php on line 24

when I run it with phpMyAdmin it tells me the problem is with 
 
, hash char(32), created integer(14), country varchar(80), 
 
My ISP is running MySQL 3.23.54
 
Cheers
 
Pieter
 

RE: [Tikiwiki-users] Problem with character encoding (bug)

[Inge Solvoll <inge@in...>]

This is correct, only external sources are affected. All other character 
encoding works.

When I browse my Tiki installation with IE6, the character encoding is set 
correctly to UTF-8, while most other pages use an ISO encoding I think.

Since it is impossible to control that the character encoding is UTF-8 for 
mailin from different clients, and external sources like javascripts, I 
think we should make an effort to solve this problem. I believe this will 
be an issue for all non-english users that use Tiki functionality that is 
affected by this problem.

I agree of course that UTF-8 is the right choice, but it doesn't solve the 
problem with external input from other encodings.

I believe the external text that is viewed wrong in my page has the 
encoding ISO Western European. Is it possible to build in functionality in 
Tiki that translates from this encoding and other common ones to UTF-8?

Inge


At 00:12 26.05.2003 -0700, you wrote:
>3. Wrong charset of input data. This is a bit of a guess regarding Inge's
>report, since it related to data entry from external sources. By now you can
>guess that such data needs to be UTF-8 encoded to be consistent with the
>rest of Tiki's data. I am not sure if Tiki validates external input to be in
>UTF-8 and convert it otherwise (my guess is that it is not). This is
>especially true for the mail-in option, because many mail clients are not
>necessarily configured to encode using UTF-8.
>
>I still think UTF-8 is a good choice, as it provides a common environment to
>all users and developers. Using local charsets would potentially cause more
>support problems, as some problems would be even more difficult to track.
>There may be some bug reports that need to be open regarding charset
>processing in mail-in etc., but the most important thing to remember about
>charsets and Tiki for now is that as long as EVERYTHING is UTF-8 encoded,
>everything is fine. You just need to make sure you are being consistent.

Re: [Tikiwiki-users] Tiki 1.6.1 released

[Flo G. <flo@bi...>]

On Mon, 26 May 2003, Oliver Scheck wrote:

> Hi Flo,
>
> is the release_tauceti_bugfix branch the basis for this release?

Yes

>
> Is there a roadmap out there describing the migration of an existing
> installation?
>
> The database schema has not changed, right? So I assuse I can just
> replace my old php and template files with the new ones.
>

Thats right. Just unzip with overwrite. Assure that you set the
file permissions and that nothing gets lost (backup your edited
templates ...). To be sure you can delete the temporary files in
templates_c (%%* and language directories en, de, sp,....) and
modules/cache/*.cache



> happy tiki'ing,
> Oliver


Have fun!

Flo

Re: [Tikiwiki-users] Tiki 1.6.1 released

[Oliver Scheck <oliver.scheck@me...>]

Hi Flo,

is the release_tauceti_bugfix branch the basis for this release?

Is there a roadmap out there describing the migration of an existing 
installation?

The database schema has not changed, right? So I assuse I can just 
replace my old php and template files with the new ones.

happy tiki'ing,
Oliver

RE: [Tikiwiki-users] Problem with character encoding (bug)

[Gil Dev <gildev@sh...>]

Hi Marc,

Let me summarize the charset issue once more.

In general Tiki is working with UTF-8 encoding, which enables it to process
and display characters from multiple languages (not just Western European)
within any site. This character set is a representation (encoding) of the
Unicode charset, and is usually considered the preferred charset of choice
for the web.

Problems with charset are usually encountered due to three reasons:

1. Wrong setting of HTTP headers, e.g. setting Apache's option
AddDefaultCharset in httpd.conf to ISO-8859-1, which would cause an override
on Tiki's specification for UTF-8. This would present Tiki's strings
incorrectly (everything but English within the ASCII range), and would send
back data to Tiki, which will not be UTF-8 encoded, thus polluting the DB.

2. Wrong charset of the language.php file. If a translation is not saved in
UTF-8 encoding, but rather in some language specific setting, then in the
case where everything else works fine, i.e. no wrong HTTP headers, etc., the
translation strings will not be displayed correctly, while the rest of the
site, as well as input processing will work fine. I emphasis that the
language.php file should be saved UTF-8 encoded, and this usually need to be
done and verified by the translator, who has the local charset installed on
its machine as well. A good tool to assist in doing this is SciTE editor,
for example.

3. Wrong charset of input data. This is a bit of a guess regarding Inge's
report, since it related to data entry from external sources. By now you can
guess that such data needs to be UTF-8 encoded to be consistent with the
rest of Tiki's data. I am not sure if Tiki validates external input to be in
UTF-8 and convert it otherwise (my guess is that it is not). This is
especially true for the mail-in option, because many mail clients are not
necessarily configured to encode using UTF-8.

I still think UTF-8 is a good choice, as it provides a common environment to
all users and developers. Using local charsets would potentially cause more
support problems, as some problems would be even more difficult to track.
There may be some bug reports that need to be open regarding charset
processing in mail-in etc., but the most important thing to remember about
charsets and Tiki for now is that as long as EVERYTHING is UTF-8 encoded,
everything is fine. You just need to make sure you are being consistent.

Gil

-----Original Message-----
From: Marc Laporte [mailto:marc@...]
Sent: Monday, May 26, 2003 2:56 AM
To: 'Inge Solvoll'; tikiwiki-users@...
Cc: gilshwartz@...
Subject: RE: [Tikiwiki-users] Problem with character encoding (bug)


Hi!

It's the same problem with French characters.

I've had success in the past by converting & uploading the language.php file
in UTF-8 format. However, Al did this for the demo site and it doesn't work.

Luc (from Tikiluc.com) found a solution:
http://alt.thetinfoilhat.com/tiki-view_forum_thread.php?forumId=6&comments_p
arentId=255

M ;-)

--
Marc Laporte


-----Original Message-----
From: tikiwiki-users-admin@...
[mailto:tikiwiki-users-admin@...] On Behalf Of Inge
Solvoll
Sent: May 25, 2003 4:25 PM
To: tikiwiki-users@...
Subject: [Tikiwiki-users] Problem with character encoding (bug)

The character encoding for country-specific characters gets messed up
sometimes in Tiki.

- When using the mailin-functionality, the Norwegian characters in the mail
are viewed incorrectly when inserted into the Wiki page.
- This also happens when I use this script for importing a news box from a
newspaper:
	<script src="http://www.vg.no/export/JS/jsalle.js"></script>;

I insert the script tag in a module that I've made. All non-english
characters are messed up.

Has anyone else discovered this problem? I don't think it is a problem with
my server configuration, because the character encoding is correct when the
text is inputted by the user directly and not imported.

Inge




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Tikiwiki-users mailing list
Tikiwiki-users@...
https://lists.sourceforge.net/lists/listinfo/tikiwiki-users

[Tikiwiki-users] Tiki 1.6.1 released

[Flo G. <flo@bi...>]

Hi Lists,

Tiki 1.6.1 has just been released. It's a pure bugfixing release.

The ones i remember are:

* [FIX] many things in Image galleries that made life hard
* [FIX] Error in install script (fgets parameter)
* [FIX] bug in page history module
* [FIX] missing addslashes
* [FIX] renaming structure doesn't work
* [FIX] sessions are not counted
* [FIX] many many more i don't remember :-)


Have fun.

Flo

RE: [Tikiwiki-users] Problem with character encoding (bug)

[Marc Laporte <marc@ma...>]

Hi!

It's the same problem with French characters.

I've had success in the past by converting & uploading the language.php =
file
in UTF-8 format. However, Al did this for the demo site and it doesn't =
work.

Luc (from Tikiluc.com) found a solution:
http://alt.thetinfoilhat.com/tiki-view_forum_thread.php?forumId=3D6&comme=
nts_p
arentId=3D255

M ;-)

--
Marc Laporte


-----Original Message-----
From: tikiwiki-users-admin@...
[mailto:tikiwiki-users-admin@...] On Behalf Of Inge
Solvoll
Sent: May 25, 2003 4:25 PM
To: tikiwiki-users@...
Subject: [Tikiwiki-users] Problem with character encoding (bug)

The character encoding for country-specific characters gets messed up=20
sometimes in Tiki.

- When using the mailin-functionality, the Norwegian characters in the =
mail=20
are viewed incorrectly when inserted into the Wiki page.
- This also happens when I use this script for importing a news box from =
a=20
newspaper:
	<script src=3D"http://www.vg.no/export/JS/jsalle.js"></script>;

I insert the script tag in a module that I've made. All non-english=20
characters are messed up.

Has anyone else discovered this problem? I don't think it is a problem =
with=20
my server configuration, because the character encoding is correct when =
the=20
text is inputted by the user directly and not imported.

Inge




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Tikiwiki-users mailing list
Tikiwiki-users@...
https://lists.sourceforge.net/lists/listinfo/tikiwiki-users

[Tikiwiki-users] Tiki sometimes displaying the wrong time zone

[Inge Solvoll <inge@in...>]

The time zone settings in my admin section are the following:

Server time zone: UTC : Coordinated Universal Time (UTC) GMT+00:00
Displayed time zone:  Europe/Oslo Central European Time (CET) GMT +01:00

But the displayed time actually switches between UTC and CET, it seems to 
be pretty random... I need it to be CET all the time, obviously.

I think I have read about something similar on the mailing lists before...

Inge

[Tikiwiki-users] Problem with character encoding (bug)

[Inge Solvoll <inge@in...>]

The character encoding for country-specific characters gets messed up 
sometimes in Tiki.

- When using the mailin-functionality, the Norwegian characters in the mail 
are viewed incorrectly when inserted into the Wiki page.
- This also happens when I use this script for importing a news box from a 
newspaper:
	<script src="http://www.vg.no/export/JS/jsalle.js"></script>;

I insert the script tag in a module that I've made. All non-english 
characters are messed up.

Has anyone else discovered this problem? I don't think it is a problem with 
my server configuration, because the character encoding is correct when the 
text is inputted by the user directly and not imported.

Inge