tikiwiki-devel

Re: [Tikiwiki-devel] Patches ?

[Tom <to...@le...>]

On Mon, Nov 11, 2002 at 04:11:38PM -0300, Garland Foster wrote:
> Thanks for the patches, 2 of them were "undiscovered bugs" and I've
> corrected them :-) thanks!

Glad to be of help.

> About tables, maybe you want to change your version to be compatible with
> 1.2 tables:

That looks much better. I will most likely upgrade to 1.2 anyways, and
port my other changes over, then think about which ones to propose as
changes to you.


I have one question about the admin user: He doesn't belong to any
groups and thus has no permissions, nevertheless he can do anything. Is
he a super-user because of his ID or name? I ask because I prefer to
delete him, and wouldn't want any clown who registers as "admin" to
become root. :)


> So thanks a lot and buckle up for 1.2 :-)

Looking forward to it. I have a few features from tavi that I miss and
which I'll most likely port over. Monospace text and the ability to say
"do NOT turn this into a WikiName" are two I can think of right now.


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <to...@le...>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

Re: [Tikiwiki-devel] Patches ?

[Garland F. <gar...@fi...>]

----- Original Message -----
From: "Tom" <to...@le...>
To: <tik...@li...>
Sent: Wednesday, November 13, 2002 6:47 AM
Subject: Re: [Tikiwiki-devel] Patches ?


> On Mon, Nov 11, 2002 at 04:11:38PM -0300, Garland Foster wrote:
> > Thanks for the patches, 2 of them were "undiscovered bugs" and I've
> > corrected them :-) thanks!
>
> Glad to be of help.
>
> > About tables, maybe you want to change your version to be compatible
with
> > 1.2 tables:
>
> That looks much better. I will most likely upgrade to 1.2 anyways, and
> port my other changes over, then think about which ones to propose as
> changes to you.
>
>
> I have one question about the admin user: He doesn't belong to any
> groups and thus has no permissions, nevertheless he can do anything. Is
> he a super-user because of his ID or name? I ask because I prefer to
> delete him, and wouldn't want any clown who registers as "admin" to
> become root. :)

The user named 'admin' is granted the permission tiki_p_admin which is a
"master" permission
that automatically gives to the group all the permissions in Tiki, the best
way to 'delete' the
admin user is to give him a very long/obscure password.
And in 1.2 users can't register as 'admin' so you will be able to delete
admin without trouble.

>
>
> > So thanks a lot and buckle up for 1.2 :-)
>
> Looking forward to it. I have a few features from tavi that I miss and
> which I'll most likely port over. Monospace text and the ability to say
> "do NOT turn this into a WikiName" are two I can think of right now.

Well, please comment us what are the features that you miss, about
monospaced text
Tiki formats monospaced text if you start the line with a whitespace, do you
need another
syntax for monospacing text?
What is the syntax to preven a name from being wikified?
Other ideas?

>
>
> --
> http://web.lemuria.org/pubkey.html
> pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <to...@le...>
>      Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Are you worried about
> your web server security? Click here for a FREE Thawte
> Apache SSL Guide and answer your Apache SSL security
> needs: http://www.gothawte.com/rd523.html
> _______________________________________________
> Tikiwiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

[Tikiwiki-devel] Patches ?

[Tom <to...@le...>]

sorry for the delay - lost of tikiwiki-devel mails were caught by my
spamassassin, even though I have the limit fairly high. I'll include
the reason block here. Apparently osirusoft's relay list is the main
reason:

> SPAM: Content analysis details:   (8.5 hits, 7 required)
> SPAM: SUBJ_ENDS_IN_Q_MARK (-0.1 points) Subject: ends in a question mark
> SPAM: TO_LOCALPART_EQ_REAL (0.5 points)  To: repeats local-part as real name
> SPAM: CLICK_BELOW        (1.5 points)  BODY: Asks you to click below
> SPAM: DOUBLE_CAPSWORD    (1.1 points)  BODY: A word in all caps repeated on the line
> SPAM: RCVD_IN_OSIRUSOFT_COM (2.0 points)  RBL: Received via a relay in relays.osirusoft.com
> SPAM:                    [RBL check: found 41.122.232.24.relays.osirusoft.com., type: 127.0.0.4]
> SPAM: RCVD_IN_RFCI       (0.5 points)  RBL: Received via a relay in ipwhois.rfc-ignorant.org
> SPAM:                    [RBL check: found 78.0.232.24.ipwhois.rfc-ignorant.org., type: 127.0.0.6]
> SPAM: X_OSIRU_SPAM_SRC   (3.0 points)  RBL: DNSBL: sender is Confirmed Spam Source



On Wed, Nov 13, 2002 at 11:25:09AM -0300, Garland Foster wrote:
> Tiki formats monospaced text if you start the line with a whitespace, do you
> need another syntax for monospacing text?

It would be nice if it were possible to include it within a line, to
have commands to be type stand out or such.


> What is the syntax to preven a name from being wikified?

Two backticks if I remember correctly `` - though the syntax is pretty
arbitrary. If you go along with my other proposal (forcing wikinames),
how about this:

((something)) - turns something into a WikiName
))something(( - prevents something from being wikified

that'd be at least somewhat consistent, with square brackets for
external links and round brackets for internal ones. or use single
curly brackets for wiki/internal links.

-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <to...@le...>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

RE: [Tikiwiki-devel] Patches ?

[Marc L. <ma...@pi...>]

[ML] How about the same syntax for external than internal? And have
tikiwiki [ML] detect if it's an internal or external link? (if a text
starts with [ML] http:// or ftp:// it should automatically make a
hyperlink, if not it's [ML] an internal link. 

[ML]  References (Internal):
[ML]    NOW: JoinCapitalizedWords
[ML]    We could add: [Three Word Page]   (like PHP Wiki) If the page
[ML]    doesn't exist, a    question mark appears.

[ML]  References (External):
[ML]    NOW:  [URL] or  [URL|link_description] or
[URL|description|nocache]. [ML]    We could add:  http://www...
(auto-detect)

[ML]  I personally find that [link_description|URL] is more intuitive
than [ML]  [URL|link_description]. What do you guys thinks?








> What is the syntax to preven a name from being wikified?

Two backticks if I remember correctly `` - though the syntax is pretty
arbitrary. If you go along with my other proposal (forcing wikinames),
how about this:

((something)) - turns something into a WikiName
))something(( - prevents something from being wikified

that'd be at least somewhat consistent, with square brackets for
external links and round brackets for internal ones. or use single
curly brackets for wiki/internal links.

Re: [Tikiwiki-devel] Patches ?

[Tom <to...@le...>]

On Thu, Nov 14, 2002 at 07:14:43PM -0500, Marc Laporte wrote:
> [ML] How about the same syntax for external than internal? And have
> tikiwiki [ML] detect if it's an internal or external link? (if a text
> starts with [ML] http:// or ftp:// it should automatically make a
> hyperlink, if not it's [ML] an internal link. 

If you rely on http:// or ftp:// then you can't have relative links (I
use those a lot, because Tiki is bright enough to not cache them and
because it allows me to move around the whole wiki) and you can't have
other protocols (remembering that there's also https is easy, but what
about links to freenet:// or who-knows-what the Tiki users want to put
in there? For example, I have a few cases where I link to the LAN file
server with file:///var/nfsmount/...)


> [ML]  I personally find that [link_description|URL] is more intuitive
> than [ML]  [URL|link_description]. What do you guys thinks?

URL|desc is consistent with the way it's done in HTML and every other
Wiki I know. Though in the end, I don't think it matters much.


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <to...@le...>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5