> It is not in the CVS, but rather in our Midgard
> database. Log in to http://admin.midgard-project.org to
> edit it.
I tried user: rparker
passwd: the same which I have for CVS but it fails to authenticate. Is
there a different passwd?
--
This is The Midgard Project's mailing list. For more i
On 19 Apr, Ron Parker wrote:
> Ack, don't ya hate it when you post an article and immediately see an
> edit?
Happens to me with the MWSs all the time...
> We'll touch it up; need a verb in a headline and need to markup the
> punctuation. Can I get this from the CVS? If not, we'll post the revis
> Ok, it is now in the 'Working on Midgard' section.
>
> http://www.midgard-project.org/article/1685.html
>
Ack, don't ya hate it when you post an article and immediately see an
edit?
We'll touch it up; need a verb in a headline and need to markup the
punctuation. Can I get this from the
Greetings!
On 18 Apr, Ron Parker wrote:
> Here's the style guide, it should be good enough to post on the site. Of
> course, it's open for the group's approval.
Ok, it is now in the 'Working on Midgard' section.
http://www.midgard-project.org/article/1685.html
> Ron Parker
/Bergie
--
Henry,
Here's the style guide, it should be good enough to post on the site. Of
course, it's open for the group's approval.
We'll be posting the final SiteGroups document in the next couple days. It
is an example of a document that uses the Midgard style.
Ron Parker
Mi-Recordz
www.mi-recordz.co
I have some scripts that I use to install a bunch of stuff including Midgard if
your doing it from source. The midgard.sh will give you a good idea of what it
takes. (http://pub.nebsites.com/scripts)
--- "Armand A. Verstappen" <[EMAIL PROTECTED]> wrote:
> "Scott Gruber" <[EMAIL PROTECTED]> wrote
"Scott Gruber" <[EMAIL PROTECTED]> wrote in message
000501bfa99a$aa3019c0$793fd3cf@scott">news:000501bfa99a$aa3019c0$793fd3cf@scott...
> i'm very interested to try out midgard, but wanted to get some sense from
> you guys about
>
> 1. how easy it is to set up (php and apache still essentially rema
On Tue, 18 Apr 2000, Miles Scruggs wrote:
> I finally completed the install for 1.4b3 after many tries. When it was
all
> said and done, no error messages and lib was compiled --with-sitegroups I
> did run the sg0migrate script and it ran find except for complaining about
> two tables that we
i'm very interested to try out midgard, but wanted to get some sense from
you guys about
1. how easy it is to set up (php and apache still essentially remain the
same right? i won't loose anything will I
2. i'd love to see sample sites running midgard to get a sense of
flexibility of info, nav a
On Tue, 18 Apr 2000, Miles Scruggs wrote:
> I finally completed the install for 1.4b3 after many tries. When it was all
> said and done, no error messages and lib was compiled --with-sitegroups I
> did run the sg0migrate script and it ran find except for complaining about
> two tables that wer
I finally completed the install for 1.4b3 after many tries. When it was all
said and done, no error messages and lib was compiled --with-sitegroups I
did run the sg0migrate script and it ran find except for complaining about
two tables that weren't there. the midgard.sitegroup looks like follo
Greetings!
There has been a two-week pause in the publication
of these summaries as I've been on vacation.
Because of that, this week's MWS is rather
populated with major announcements.
Current versions:
Stable: 1.2.5 (Mad Kin
On Tue, 18 Apr 2000, Fred Hirsch wrote:
> Three tables, member, person and possibly grp have some influence on
> this issue. In person I have two users... the admin and a test user
> with no admin privelages. In grp I have two groups, the admin group-1
> and a test user group-2. In member admin i
On Tue, 18 Apr 2000, Emiliano wrote:
> > problem. Could it be that an unencrypted password is not allowed foor the
> > root user? Wouldn't be too bad, I didn't mean to have the password
> > clear-text anyway, but if so, it should be documented.
>
> If this is so it is a bug which must be resolve
Thanks Armand, Henri and Emile for your help. Next time I will try
better to RTFM.. \\grins//
> You're using the beta on a production server? Ouch...
Best I can do, though to be honest, its not a fully public site/project,
it makes me no money, and installing Midgard is mostly a hobby for me.
On Tue, 18 Apr 2000, Armand A. Verstappen wrote:
> I think I just ran into the same problem on my test setup. Changing the
> '**password' to '[encrypted-pass]' using an sql-statement solved the
> problem. Could it be that an unencrypted password is not allowed foor the
> root user? Wouldn't be to
On Tue, 18 Apr 2000, Henri Bergius wrote:
> You log on using [username][delimiter][sitegroup] as the
> user ID. The password is same as usual.
Also, for non-SG0 sites things remain the same. Use the sg0migrate script
to move production content out of SG0 (which everything defaults to).
> You're
On Tue, 18 Apr 2000, Fred Hirsch wrote:
> I did compile midgard 1.4b3 with site groups enabled in midgard lib.
> The password which is set by default by the update script is
> **password. I assumed the ** was a means of denoting that the password
> was unencrypted. However, this seems to have so
Henri Bergius <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Admin has a plain password of "**password" assigned in the database,
> > while the test user has an encrypted password. No matter what I attempt,
> > I cannot logon to the admin ID using the given
On 18 Apr, Fred Hirsch wrote:
> I did compile midgard 1.4b3 with site groups enabled in midgard lib.
Ok, that is where the problem is.
> The password which is set by default by the update script is
> **password. I assumed the ** was a means of denoting that the password
> was unencrypted. Howev
Henri Bergius wrote:
> The new Midgard version has SiteGroups enabled by default,
> and so uses its login conventions. Here is what Emile wrote
> on it recently:
I did compile midgard 1.4b3 with site groups enabled in midgard lib.
The password which is set by default by the update script is
**p
On 18 Apr, Fred Hirsch wrote:
> Hallo,
Greetings!
> Got 1.4b3 installed with very few problems after upgrading from 1.26b2.
That is good to hear. I haven't yet had the time to
try the release myself...
> Admin has a plain password of "**password" assigned in the database,
> while the test use
Hallo,
Got 1.4b3 installed with very few problems after upgrading from 1.26b2.
I have encountered a problem with aspects of this install which I have
not seen in the past:
Has the method in which the admin password is encrypted changed? I
discovered this problem using the following procedure:
Greetings!
On 18 Apr, Miles Scruggs wrote:
> btw who do I talk to about maintaining a upgrade doc
> and some howto's, etc?
We're currently looking for adding a Documentation Coordinator
into our team. The office is pretty much similar to those of
the Branch Maintainers.
The Documentation Coordi
Hey gang,
I'm attaching a letter that addresses my general observations and opinions
about Midgard's documentation. I meant to send this to the group with mine
and Dana's FINAL rewrite of SiteGroups but that document is complicated
and we're working on it. We'll be posting SiteGroups in the next
>> 1.) On my first host I get two error messages that I can find.
>> a) In the style admin for any style I get this error at the bottom.
>> "Fatal error: Call to unsupported or undefined function
>> mgd_get_element_by_name() in code-init on line 12"
>>
26 matches
Mail list logo
