Tiki Wiki CMS Groupware

Hi!

I have Tiki 1.9.7 working fine on MySQL 3.x   

I am pretty sure if someone tried to use Tiki 1.9.7 on php 4.1, he would 
get some errors on some features. I think the general requirement will 
go to PHP 4.3 (mose?)

"For PHP 5.0, you must use Tiki 1.9.1 (or higher) with the MySQLi 
extension":      huh?  PHP5 + MySQL doesn't work?

-WikiGraph? for creating and manipulating graphs./    Use GraphViz    
->  I would take this out of there. It is a 3rd paty mods

Keep up the great work!

M ;-)



  

Dave Thacker wrote:
> Starting today, I'm auditing the install section of the Docs, and making 
> changes where needed.  In part 1 I'll deal with supporting apps,  Part 2 will 
> deal with specific configuration parameters made outside the install program.  
> Please note any changes that need to be made, especially changes that need to 
> be made for 1.10:
>
> Install Requirements
> TikiWiki can run on any webserver (such as Apache) that supports PHP and meets 
> the following recommended requirements:
>
>     * 128MB RAM
>     * 60 megs free storage 
>
> TikiWiki requires an active database connection. The database can be installed 
> in the same physical location of the webserver (localhost). TikiWiki supports 
> the following databases:
>
>     * MySQL 4.0.x (or higher)
>           o For MySQL 4.1.x, you must use Tiki 1.9.x
>           o For MySQL 5.x, you must use Tiki 1.9.3+. See MySQL5external link 
> for details. 
>
> (Editor's note:  I'd really like to get version numbers on the DBMS's below, 
> as well as dropping any that haven't been certified recently)
>     * Postgres
>     * Oracle
>     * Sybase
>     * MSSQL 
>
> PHP
> TikiWiki requires PHP 4.1+, version 4.2+ is recommended For PHP 5.0, you must 
> use Tiki 1.9.1 (or higher) with the MySQLi extension
>
>
> Optional Software or Libraries
> Some TikiWiki feautures require the following additional software or 
> libraries:
> Feature	Additional Requirements
> -Image processing, used for thumbnail generation, dynamic chart generation, 
> and to prevent bot/automatic registration.	
>      Use either GD Library 1.5 (or higher) or ImageMagick. ImageMagick is   
> included, by default with PHP 4.3+
>
> -WikiGraph? for creating and manipulating graphs./	Use GraphViz
>
> -Webmail/	PHP 4.2+
>
> -PDF Genration/	php-xml
>
> -Manage and display maps as a GeoCMS (Geospastial Content Management System)./	
> Mapserver 4.6+
>
> -Rewrite Tiki's default URLs	Use the Apache Rewrite Rules to create shorter, 
> or custom, URLs.
>
> Thanks for your help.   
>
> Dave
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Tikiwiki-devel mailing list
> Tikiwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>

I get the same error with HEAD and cannot edit wiki pages due to the 
resulting error.  Maybe I still need to learn something about cvs (most 
likely!)

\\Greg

Dave Thacker wrote:
> cvs checkout: existing repository /cvsroot/tikiwiki/tiki/lib/fckeditor does 
> not match /cvsroot/tikiwiki/_fckeditor
> cvs checkout: ignoring module fckeditor
>
> Still getting this.  My checkout string is:
> cvs -z3 co -d tiki-1-10 tikiwiki
>
> Do I need to do a separater checkout of fckeditor?
>
> Dave
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Tikiwiki-devel mailing list
> Tikiwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>

The error is:

cvs checkout: existing repository /cvsroot/tikiwiki/tiki/lib/fckeditor 
does not match /cvsroot/tikiwiki/_fckeditor
cvs checkout: ignoring module fckeditor


\\Greg

Greg Martin wrote:
> I get the same error with HEAD and cannot edit wiki pages due to the 
> resulting error.  Maybe I still need to learn something about cvs (most 
> likely!)
>
> \\Greg
>
> Dave Thacker wrote:
>   
>> cvs checkout: existing repository /cvsroot/tikiwiki/tiki/lib/fckeditor does 
>> not match /cvsroot/tikiwiki/_fckeditor
>> cvs checkout: ignoring module fckeditor
>>
>> Still getting this.  My checkout string is:
>> cvs -z3 co -d tiki-1-10 tikiwiki
>>
>> Do I need to do a separater checkout of fckeditor?
>>
>> Dave
>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Tikiwiki-devel mailing list
>> Tikiwiki-devel@...
>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>>
>>   
>>     
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Tikiwiki-devel mailing list
> Tikiwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>

le Thu, Dec 28, 2006 at 09:09:23AM -0500 par Greg Martin :
> The error is:
> 
> cvs checkout: existing repository /cvsroot/tikiwiki/tiki/lib/fckeditor 
> does not match /cvsroot/tikiwiki/_fckeditor
> cvs checkout: ignoring module fckeditor

- that error comes from the fact that fckeditor, like smarty or adodb,
is now in a separate cvs module. 

What you have to do is :

cvs /path/to/tiki_workdir/
rm -rf lib/fckeditor
cvs up fckeditor


cheers,
mose

On Thu, Dec 28, 2006 at 05:06:27PM +0100, mose wrote:
> le Thu, Dec 28, 2006 at 09:09:23AM -0500 par Greg Martin :
> > The error is:
> > 
> > cvs checkout: existing repository /cvsroot/tikiwiki/tiki/lib/fckeditor 
> > does not match /cvsroot/tikiwiki/_fckeditor
> > cvs checkout: ignoring module fckeditor
> 
> - that error comes from the fact that fckeditor, like smarty or adodb,
> is now in a separate cvs module. 
> 
> What you have to do is :
> 
> cvs /path/to/tiki_workdir/
> rm -rf lib/fckeditor
> cvs up fckeditor

Doesn't work for me:

pinfu# pwd
/home/www/lojban/tiki
pinfu# rm -rf lib/fckeditor
pinfu# cvs up fckeditor
rlpowell@... password:
cvs update: nothing known about fckeditor
pinfu# cvs up lib/fckeditor
rlpowell@... password:
pinfu# find lib/fckeditor
find: lib/fckeditor: No such file or directory

I can't edit anything:

The requested URL /tiki/lib/fckeditor/editor/fckeditor.html was not
found on this server.

-Robin

le Thu, Dec 28, 2006 at 01:02:26PM -0800 par Robin Lee Powell :
> On Thu, Dec 28, 2006 at 05:06:27PM +0100, mose wrote:
> > le Thu, Dec 28, 2006 at 09:09:23AM -0500 par Greg Martin :
> > > The error is:
> > > 
> > > cvs checkout: existing repository /cvsroot/tikiwiki/tiki/lib/fckeditor 
> > > does not match /cvsroot/tikiwiki/_fckeditor
> > > cvs checkout: ignoring module fckeditor
> > 
> > - that error comes from the fact that fckeditor, like smarty or adodb,
> > is now in a separate cvs module. 
> > 
> > What you have to do is :
> > 
> > cvs /path/to/tiki_workdir/
> > rm -rf lib/fckeditor
> > cvs up fckeditor
> 
> Doesn't work for me:
> 
> pinfu# pwd
> /home/www/lojban/tiki
> pinfu# rm -rf lib/fckeditor
> pinfu# cvs up fckeditor
> rlpowell@... password:
> cvs update: nothing known about fckeditor
> pinfu# cvs up lib/fckeditor
> rlpowell@... password:
> pinfu# find lib/fckeditor
> find: lib/fckeditor: No such file or directory
> 
> I can't edit anything:
> 
> The requested URL /tiki/lib/fckeditor/editor/fckeditor.html was not
> found on this server.

- sorry !

as it's a cvs module you need to checkout, not update :
in the above list of commands, replace
cvs up fckeditor
by
cvs co fckeditor 


cheers,
mose

On Thu, Dec 28, 2006 at 10:28:16PM +0100, mose wrote:
> le Thu, Dec 28, 2006 at 01:02:26PM -0800 par Robin Lee Powell :
> > On Thu, Dec 28, 2006 at 05:06:27PM +0100, mose wrote:
> > > le Thu, Dec 28, 2006 at 09:09:23AM -0500 par Greg Martin :
> > > > The error is:
> > > > 
> > > > cvs checkout: existing repository /cvsroot/tikiwiki/tiki/lib/fckeditor 
> > > > does not match /cvsroot/tikiwiki/_fckeditor
> > > > cvs checkout: ignoring module fckeditor
> > > 
> > > - that error comes from the fact that fckeditor, like smarty or adodb,
> > > is now in a separate cvs module. 
> > > 
> > > What you have to do is :
> > > 
> > > cvs /path/to/tiki_workdir/
> > > rm -rf lib/fckeditor
> > > cvs up fckeditor
> > 
> > Doesn't work for me:
> > 
> > pinfu# pwd
> > /home/www/lojban/tiki
> > pinfu# rm -rf lib/fckeditor
> > pinfu# cvs up fckeditor
> > rlpowell@... password:
> > cvs update: nothing known about fckeditor
> > pinfu# cvs up lib/fckeditor
> > rlpowell@... password:
> > pinfu# find lib/fckeditor
> > find: lib/fckeditor: No such file or directory
> > 
> > I can't edit anything:
> > 
> > The requested URL /tiki/lib/fckeditor/editor/fckeditor.html was not
> > found on this server.
> 
> - sorry !
> 
> as it's a cvs module you need to checkout, not update :
> in the above list of commands, replace
> cvs up fckeditor
> by
> cvs co fckeditor 

OK, it "works" now.

The new editor strips all line breaks out of the page as it was so
it's just one big mass of text.  I don't see how this can be of any
use.

Is this a bug or a mis-configuration or what?

Example:

* Lojban is designed to be used by people in communication with each other, and possibly in the future with computers. * Lojban is designed to be culturally neutral. * Lojban grammar is based on the principles of logic. * Lojban has an unambiguous grammar. * Lojban has phonetic spelling, and unambiguous resolution of sounds into words. * Lojban is simple compared to natural languages; it is easy to learn. * Lojban's 1300 root words can be easily combined to form a vocabulary of millions of* Lojban is designed to be used by people in communication with each other, and possibly in the future with computers. * Lojban is designed to be culturally neutral. * Lojban grammar is based on the principles of logic. * Lojban has an unambiguous grammar. * Lojban has phonetic spelling, and unambiguous resolution of sounds into words. * Lojban is simple compared to natural languages; it is easy to learn. * Lojban's 1300 root words can be easily combined to form a vocabulary of millions of

-Robin

le Thu, Dec 28, 2006 at 01:52:19PM -0800 par Robin Lee Powell :
> 
> OK, it "works" now.
> 
> The new editor strips all line breaks out of the page as it was so
> it's just one big mass of text.  I don't see how this can be of any
> use.
> 
> Is this a bug or a mis-configuration or what?

- this may be a bug, I didn't check yet all configuration cases
beetween use_html, feature_fckeditor and others. I don't consider
wysiwyg totally operational yet. Some fine tuning has to be finished
on this, but it's a huge chunk, and takes more time than what I
expected. But it's on the right way, for now.

cheers,
mose

On Thu, Dec 28, 2006 at 11:09:57PM +0100, mose wrote:
> le Thu, Dec 28, 2006 at 01:52:19PM -0800 par Robin Lee Powell :
> > 
> > OK, it "works" now.
> > 
> > The new editor strips all line breaks out of the page as it was
> > so it's just one big mass of text.  I don't see how this can be
> > of any use.
> > 
> > Is this a bug or a mis-configuration or what?
> 
> - this may be a bug, I didn't check yet all configuration cases
> beetween use_html, feature_fckeditor and others. I don't consider
> wysiwyg totally operational yet. Some fine tuning has to be
> finished on this, but it's a huge chunk, and takes more time than
> what I expected. But it's on the right way, for now.

OK, I think it's working better for me now.  I don't know what the
initial problem was, but a DB update seems to have fixed it.

It would be nice if "WYSIWIG optional" was the default, please.

Other than that, good work!

-Robin

-- 
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
Reason #237 To Learn Lojban: "Homonyms: Their Grate!"
Proud Supporter of the Singularity Institute - http://singinst.org/

On Thu, Dec 28, 2006 at 02:44:40PM -0800, Robin Lee Powell wrote:
> On Thu, Dec 28, 2006 at 11:09:57PM +0100, mose wrote:
> > le Thu, Dec 28, 2006 at 01:52:19PM -0800 par Robin Lee Powell :
> > > 
> > > OK, it "works" now.
> > > 
> > > The new editor strips all line breaks out of the page as it
> > > was so it's just one big mass of text.  I don't see how this
> > > can be of any use.
> > > 
> > > Is this a bug or a mis-configuration or what?
> > 
> > - this may be a bug, I didn't check yet all configuration cases
> > beetween use_html, feature_fckeditor and others. I don't
> > consider wysiwyg totally operational yet. Some fine tuning has
> > to be finished on this, but it's a huge chunk, and takes more
> > time than what I expected. But it's on the right way, for now.
> 
> OK, I think it's working better for me now.  I don't know what the
> initial problem was, but a DB update seems to have fixed it.

Then several minutes later it stopped again.

I have "Allow HTML" off, but the WYSIWIG editor is completely
failing.  It just shows the Wiki text, but in one big blob.  I have:

Content is parsed like wiki page:  	Checked
Content is partially parsed: 		Unchecked

Is there anything else I should be looking at?

How can I help debug this?  For the few seconds it worked, it was
kind of cool...

This is on lojban.org, if you want to look yourself.

-Robin

le Thu, Dec 28, 2006 at 03:11:14PM -0800 par Robin Lee Powell :
> On Thu, Dec 28, 2006 at 02:44:40PM -0800, Robin Lee Powell wrote:
> > On Thu, Dec 28, 2006 at 11:09:57PM +0100, mose wrote:
> > > le Thu, Dec 28, 2006 at 01:52:19PM -0800 par Robin Lee Powell :
> > > > 
> > > > OK, it "works" now.
> > > > 
> > > > The new editor strips all line breaks out of the page as it
> > > > was so it's just one big mass of text.  I don't see how this
> > > > can be of any use.
> > > > 
> > > > Is this a bug or a mis-configuration or what?
> > > 
> > > - this may be a bug, I didn't check yet all configuration cases
> > > beetween use_html, feature_fckeditor and others. I don't
> > > consider wysiwyg totally operational yet. Some fine tuning has
> > > to be finished on this, but it's a huge chunk, and takes more
> > > time than what I expected. But it's on the right way, for now.
> > 
> > OK, I think it's working better for me now.  I don't know what the
> > initial problem was, but a DB update seems to have fixed it.
> 
> Then several minutes later it stopped again.
> 
> I have "Allow HTML" off, but the WYSIWIG editor is completely
> failing.  It just shows the Wiki text, but in one big blob.  I have:
> 
> Content is parsed like wiki page:  	Checked
> Content is partially parsed: 		Unchecked
> 
> Is there anything else I should be looking at?
> 
> How can I help debug this?  For the few seconds it worked, it was
> kind of cool...
> 
> This is on lojban.org, if you want to look yourself.

- thanks for that detailed report.

There is some consistency to keep beetween use_html and wysiwyg
editing, that seem to require immediate attention. The
tiki-editpage.php is quite a mess, imho, and there is quite a bunch of
'exceptions' depending on this or that feature is enabled.

I'll reproduce your setup locally and I think I may be able
to find a quick solution at least for the carriage return issue.

fck produces an output without carriage return, which makes possible
to have it wiki-parsed (that interprets this for formatting), it's
convenient, but not in case of full wiki parsing.

more news very soon.


cheers,
mose

I have a problem withi this as well. When i try to edit a document, I 
get an error that says:
error loading: http://my.dom/setup_fckeditor.php

Problem is that my tiki path is http://my.dom/tiki/.... so the path to 
fcheditor.php is wrong. can I correct this somewhere? BTW, I disabled 
the wysiwyg editor and still get this error.

\\Greg

mose wrote:
> le Thu, Dec 28, 2006 at 01:52:19PM -0800 par Robin Lee Powell :
>   
>> OK, it "works" now.
>>
>> The new editor strips all line breaks out of the page as it was so
>> it's just one big mass of text.  I don't see how this can be of any
>> use.
>>
>> Is this a bug or a mis-configuration or what?
>>     
>
> - this may be a bug, I didn't check yet all configuration cases
> beetween use_html, feature_fckeditor and others. I don't consider
> wysiwyg totally operational yet. Some fine tuning has to be finished
> on this, but it's a huge chunk, and takes more time than what I
> expected. But it's on the right way, for now.
>
> cheers,
> mose
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Tikiwiki-devel mailing list
> Tikiwiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
>

le Fri, Dec 29, 2006 at 12:56:41AM +0100 par mose :
> le Thu, Dec 28, 2006 at 03:11:14PM -0800 par Robin Lee Powell :
> > 
> > Then several minutes later it stopped again.
> > 
> > I have "Allow HTML" off, but the WYSIWIG editor is completely
> > failing.  It just shows the Wiki text, but in one big blob.  I have:
> > 
> > Content is parsed like wiki page:  	Checked
> > Content is partially parsed: 		Unchecked
> > 
> > Is there anything else I should be looking at?
> > 
> > How can I help debug this?  For the few seconds it worked, it was
> > kind of cool...
> > 
> > This is on lojban.org, if you want to look yourself.
> 
> - thanks for that detailed report.
> 
> There is some consistency to keep beetween use_html and wysiwyg
> editing, that seem to require immediate attention. The
> tiki-editpage.php is quite a mess, imho, and there is quite a bunch of
> 'exceptions' depending on this or that feature is enabled.
> 
> I'll reproduce your setup locally and I think I may be able
> to find a quick solution at least for the carriage return issue.
> 
> fck produces an output without carriage return, which makes possible
> to have it wiki-parsed (that interprets this for formatting), it's
> convenient, but not in case of full wiki parsing.
> 
> more news very soon.

- maybe I found a way, but I need to test it more. Robin, can you test
adding in templates/setup_fckeditor.tpl :

FCKConfig.FormatOutput = true ;

I tested locally, reproduced the one-line wikipage problem, and this
seems to solve it, without breaking the rest. I need to test with
other configurations combination, therefore.


cheers,
mose

le Thu, Dec 28, 2006 at 06:15:38PM -0500 par Greg Martin :
> I have a problem withi this as well. When i try to edit a document, I 
> get an error that says:
> error loading: http://my.dom/setup_fckeditor.php
> 
> Problem is that my tiki path is http://my.dom/tiki/.... so the path to 
> fcheditor.php is wrong. can I correct this somewhere? BTW, I disabled 
> the wysiwyg editor and still get this error.

- the setup of wysiwyg editor is stored in a session var, for the sake
of switching optional wysyiwyg or not. I just committed a change that
resets that session var because when you disable wysiwyg, the var was
still setup to 'y'.


cheers,
mose

On Fri, Dec 29, 2006 at 01:37:50AM +0100, mose wrote:
> le Fri, Dec 29, 2006 at 12:56:41AM +0100 par mose :
> > le Thu, Dec 28, 2006 at 03:11:14PM -0800 par Robin Lee Powell :
> > > 
> > > Then several minutes later it stopped again.
> > > 
> > > I have "Allow HTML" off, but the WYSIWIG editor is completely
> > > failing.  It just shows the Wiki text, but in one big blob.  I
> > > have:
> > > 
> > > Content is parsed like wiki page:  	Checked
> > > Content is partially parsed: 		Unchecked
> > > 
> > > Is there anything else I should be looking at?
> > > 
> > > How can I help debug this?  For the few seconds it worked, it
> > > was kind of cool...
> > > 
> > > This is on lojban.org, if you want to look yourself.
> > 
> > - thanks for that detailed report.
> > 
> > There is some consistency to keep beetween use_html and wysiwyg
> > editing, that seem to require immediate attention. The
> > tiki-editpage.php is quite a mess, imho, and there is quite a
> > bunch of 'exceptions' depending on this or that feature is
> > enabled.
> > 
> > I'll reproduce your setup locally and I think I may be able to
> > find a quick solution at least for the carriage return issue.
> > 
> > fck produces an output without carriage return, which makes
> > possible to have it wiki-parsed (that interprets this for
> > formatting), it's convenient, but not in case of full wiki
> > parsing.
> > 
> > more news very soon.
> 
> - maybe I found a way, but I need to test it more. Robin, can you
> test adding in templates/setup_fckeditor.tpl :
> 
> FCKConfig.FormatOutput = true ;
> 
> I tested locally, reproduced the one-line wikipage problem, and
> this seems to solve it, without breaking the rest. I need to test
> with other configurations combination, therefore.

Tried both near the top and at the bottom; doesn't seem to help.

-Robin

Quoting Marc Laporte <marc@...>:

> In 60+ projects, I have never used it.
>
> I am not even sure to know what it does. :-)

Marc! It is this eph... erm, thingy... ah, forget it, kill it! :-p

Oliver

le Thu, Dec 28, 2006 at 05:46:51PM +0100 par rom@... :
> Quoting Marc Laporte <marc@...>:
> 
> > In 60+ projects, I have never used it.
> >
> > I am not even sure to know what it does. :-)
> 
> Marc! It is this eph... erm, thingy... ah, forget it, kill it! :-p
> 

- okay, that's enuf deathwish, I'll eradicate that thing from the
surface of tikiwiki.


cheers,
mose

le Thu, Dec 28, 2006 at 07:12:22AM -0600 par Dave Thacker :
> On Tuesday 26 December 2006 19:27, mose wrote:
> (stuff snipped....)
> >
> > I'm considering to 'kill kill' that code and replace it with a simpler
> > way to specify admin-defined fields for users. Do anyone use that
> > thing ? Do we need an upgrade code for migrating data using that code ?
> 
> As of 1200 UTC, I still have checkboxes on Admin::Login for 
> Use tracker for more user information:	
> Use tracker for more group information:
> 
> Are these what you were going to kill?

- certainly not. That works and is used in production. I talk about
something you will not see if you don't read the code.

cheers,
mose

le Thu, Dec 28, 2006 at 05:04:19PM +0100 par mose :
> le Thu, Dec 28, 2006 at 07:12:22AM -0600 par Dave Thacker :
> > On Tuesday 26 December 2006 19:27, mose wrote:
> > (stuff snipped....)
> > >
> > > I'm considering to 'kill kill' that code and replace it with a simpler
> > > way to specify admin-defined fields for users. Do anyone use that
> > > thing ? Do we need an upgrade code for migrating data using that code ?
> > 
> > As of 1200 UTC, I still have checkboxes on Admin::Login for 
> > Use tracker for more user information:	
> > Use tracker for more group information:
> > 
> > Are these what you were going to kill?
> 
> - certainly not. That works and is used in production. I talk about
> something you will not see if you don't read the code.

- ah no, that time I was talking about ephemeride, sorry, but you
snipped the part where I talked about it. That you could see and try
to use. What you can't see are custom user fields.


cheers,
mose

le Thu, Dec 28, 2006 at 05:11:37PM +0100 par mose :
> le Thu, Dec 28, 2006 at 05:04:19PM +0100 par mose :
> > le Thu, Dec 28, 2006 at 07:12:22AM -0600 par Dave Thacker :
> > > On Tuesday 26 December 2006 19:27, mose wrote:
> > > (stuff snipped....)
> > > >
> > > > I'm considering to 'kill kill' that code and replace it with a simpler
> > > > way to specify admin-defined fields for users. Do anyone use that
> > > > thing ? Do we need an upgrade code for migrating data using that code ?
> > > 
> > > As of 1200 UTC, I still have checkboxes on Admin::Login for 
> > > Use tracker for more user information:	
> > > Use tracker for more group information:
> > > 
> > > Are these what you were going to kill?
> > 
> > - certainly not. That works and is used in production. I talk about
> > something you will not see if you don't read the code.
> 
> - ah no, that time I was talking about ephemeride, sorry, but you
> snipped the part where I talked about it. That you could see and try
> to use. What you can't see are custom user fields.


- ok, I need a coffee.

mose