[BlueOnyx:00881] Re: problem with phpmyadmin signon
Stuart Clark (Datacenta)
stuart.clark at datacenta.net
Fri Mar 27 11:13:58 -05 2009
Message: 3
Date: Fri, 27 Mar 2009 14:46:56 +0100
From: Rickard Osser <rickard.osser at bluapp.com>
Subject: [BlueOnyx:00877] Re: FW: problem with phpmyadmin signon
To: BlueOnyx General Mailing List <blueonyx at blueonyx.it>
Message-ID: <1238161616.9218.30.camel at newly.osser.se>
Content-Type: text/plain
On Fri, 2009-03-27 at 12:57 +0000, Stuart Clark (Datacenta) wrote:
> Hi
>
> I just filed the following in a bug ticket.
>
> I have just installed the latest release and when trying to access the
> phpmyadmin through the gui there is a broken image box and all I get
is
> a constant clicking as though it is trying to submit constantly but I
> never get signed in. If I go directly to /base/phpmyadmin/signon.php I
> get the login screen but using the root and password does nothing. I
am
> also getting the following browser errors.
>
> Line: 121 Char: 1 Error: 'top.code.FormField?_textFieldSubmitHandler'
is
> null or not an object Code: 0 URL:
> https://10.0.0.198:81/base/phpmyadmin/signon.php
>
> Line: 1 Char: 33 Error: 'top.code' is null or not an object Code: 0
URL:
> https://10.0.0.198:81/base/phpmyadmin/signon.php
>
> Line: 172 Char: 2 Error: 'top.code' is null or not an object Code: 0
> URL: https://10.0.0.198:81/base/phpmyadmin/signon.php
>
> I am running Vista and IE7 I have tried with firefox 3 also and the
> login does not work
>
> Is this a bug or likely to be a configuration issue?
>Hi Stuart,
>a small question, did you set the password for mysql in the gui or from
>CLI?
Hi Rickard
I set the password through the GUI
--
Stuart Clark
Systems Administrator
---------------------------------------------------------------
Datacenta Hosting Ltd
Gild House, 72 Norwich Avenue West, Bournemouth, Dorset, BH2 6AW.
Tel: 01202 755 377 - Fax: 01202 755 301
www.datacenta.net - A Kimcell Company
---------------------------------------------------------------
Datacenta Hosting Ltd is a company registered in Scotland with
registration number: SC208801
Registered address: Crescent House, Carnegie Campus, Dunfermline, Fife,
KY11 8GR
VAT Number: 785629182
---------------------------------------------------------------
Charitable donations to Julia's House and Youth Cancer Trust were made
in 2008 in lieu of sending Christmas cards.
Think before you print! Save paper - do you really need to print this
email?
From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it]
On Behalf Of blueonyx-request at blueonyx.it
Sent: 27 March 2009 16:00
To: blueonyx at blueonyx.it
Subject: [SPAM (Bayesian)] - Blueonyx Digest, Vol 3, Issue 38 - Bayesian
Filter detected spam
Send Blueonyx mailing list submissions to
blueonyx at blueonyx.it
To subscribe or unsubscribe via the World Wide Web, visit
http://www.blueonyx.it/mailman/listinfo/blueonyx
or, via email, send a message with subject or body 'help' to
blueonyx-request at blueonyx.it
You can reach the person managing the list at
blueonyx-owner at blueonyx.it
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Blueonyx digest..."
Today's Topics:
1. [BlueOnyx:00875] Re: Feature Requests (Michael Stauber)
2. [BlueOnyx:00876] FW: problem with phpmyadmin signon
(Stuart Clark (Datacenta))
3. [BlueOnyx:00877] Re: FW: problem with phpmyadmin signon
(Rickard Osser)
4. [BlueOnyx:00878] Re: Feature Requests (Greg O'Lone)
5. [BlueOnyx:00879] Re: Feature Requests (Michael Stauber)
6. [BlueOnyx:00880] Re: Feature Requests (Greg O'Lone)
----------------------------------------------------------------------
Message: 1
Date: Fri, 27 Mar 2009 07:55:50 +0100
From: Michael Stauber <mstauber at blueonyx.it>
Subject: [BlueOnyx:00875] Re: Feature Requests
To: BlueOnyx General Mailing List <blueonyx at blueonyx.it>
Message-ID: <200903270755.51059.mstauber at blueonyx.it>
Content-Type: text/plain; charset="utf-8"
Hi Greg,
> What I'm thinking of is a way to set username prefixes for each site.
> I've been reading all that I can find about Sausalito, and after
> putting some thought to it, I'm going to need to change the
> userAddHandler.php file to make it work properly. I'm thinking that
> I'd rather it be done at the distribution level so that it doesn't
> screw things up later. So here's what's going through my mind:
>
> An optional VSite boolean property (userPrefixEnabled) which enables
> username prefixes for each site. False would leave the current
> behavior intact. userAdmin access only.
>
> An optional VSite alpha property (userPrefix) which would allow us to
> override the default prefix.
>
> in userAddHandler, if userPrefixEnabled is False, process as normal.
> If true, append the selected username to the aliases and set the
> username to Site##_### or userPrefix###. We'd need to look at the
> users in the site/users directory and find the highest existing user,
> but I don't think that would be too hard.
Yeah, that's a nice idea. I see some potential obstacles in the form of
that
Java script that suggests a username when you enter the full name. So
that
needs to be tweaked as well. But aside from that it's certainly doable
and
would be a nice addition.
--
With best regards
Michael Stauber
------------------------------
Message: 2
Date: Fri, 27 Mar 2009 12:57:03 -0000
From: "Stuart Clark (Datacenta)" <stuart.clark at datacenta.net>
Subject: [BlueOnyx:00876] FW: problem with phpmyadmin signon
To: <blueonyx at blueonyx.it>
Message-ID:
<4B406194C609944B915F8DDD33C70ED80208CEF9 at bluemountain2.mshome.net>
Content-Type: text/plain; charset="US-ASCII"
Hi
I just filed the following in a bug ticket.
I have just installed the latest release and when trying to access the
phpmyadmin through the gui there is a broken image box and all I get is
a constant clicking as though it is trying to submit constantly but I
never get signed in. If I go directly to /base/phpmyadmin/signon.php I
get the login screen but using the root and password does nothing. I am
also getting the following browser errors.
Line: 121 Char: 1 Error: 'top.code.FormField?_textFieldSubmitHandler' is
null or not an object Code: 0 URL:
https://10.0.0.198:81/base/phpmyadmin/signon.php
Line: 1 Char: 33 Error: 'top.code' is null or not an object Code: 0 URL:
https://10.0.0.198:81/base/phpmyadmin/signon.php
Line: 172 Char: 2 Error: 'top.code' is null or not an object Code: 0
URL: https://10.0.0.198:81/base/phpmyadmin/signon.php
I am running Vista and IE7 I have tried with firefox 3 also and the
login does not work
Is this a bug or likely to be a configuration issue?
Regards
Stuart
------------------------------
Message: 3
Date: Fri, 27 Mar 2009 14:46:56 +0100
From: Rickard Osser <rickard.osser at bluapp.com>
Subject: [BlueOnyx:00877] Re: FW: problem with phpmyadmin signon
To: BlueOnyx General Mailing List <blueonyx at blueonyx.it>
Message-ID: <1238161616.9218.30.camel at newly.osser.se>
Content-Type: text/plain
On Fri, 2009-03-27 at 12:57 +0000, Stuart Clark (Datacenta) wrote:
> Hi
>
> I just filed the following in a bug ticket.
>
> I have just installed the latest release and when trying to access the
> phpmyadmin through the gui there is a broken image box and all I get
is
> a constant clicking as though it is trying to submit constantly but I
> never get signed in. If I go directly to /base/phpmyadmin/signon.php I
> get the login screen but using the root and password does nothing. I
am
> also getting the following browser errors.
>
> Line: 121 Char: 1 Error: 'top.code.FormField?_textFieldSubmitHandler'
is
> null or not an object Code: 0 URL:
> https://10.0.0.198:81/base/phpmyadmin/signon.php
>
> Line: 1 Char: 33 Error: 'top.code' is null or not an object Code: 0
URL:
> https://10.0.0.198:81/base/phpmyadmin/signon.php
>
> Line: 172 Char: 2 Error: 'top.code' is null or not an object Code: 0
> URL: https://10.0.0.198:81/base/phpmyadmin/signon.php
>
> I am running Vista and IE7 I have tried with firefox 3 also and the
> login does not work
>
> Is this a bug or likely to be a configuration issue?
Hi Stuart,
a small question, did you set the password for mysql in the gui or from
CLI?
Best regards,
--
Rickard Osser <rickard.osser at bluapp.com>
BluApp AB
------------------------------
Message: 4
Date: Fri, 27 Mar 2009 09:58:04 -0400
From: "Greg O'Lone" <blueonyxlist at stretchedout.com>
Subject: [BlueOnyx:00878] Re: Feature Requests
To: BlueOnyx General Mailing List <blueonyx at blueonyx.it>
Message-ID: <D971E366-BAA5-49D1-BDCB-EA68EECB153F at stretchedout.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
On Mar 27, 2009, at 2:55 am, Michael Stauber wrote:
> Hi Greg,
>
>> What I'm thinking of is a way to set username prefixes for each site.
>> I've been reading all that I can find about Sausalito, and after
>> putting some thought to it, I'm going to need to change the
>> userAddHandler.php file to make it work properly. I'm thinking that
>> I'd rather it be done at the distribution level so that it doesn't
>> screw things up later. So here's what's going through my mind:
>>
>> An optional VSite boolean property (userPrefixEnabled) which enables
>> username prefixes for each site. False would leave the current
>> behavior intact. userAdmin access only.
>>
>> An optional VSite alpha property (userPrefix) which would allow us to
>> override the default prefix.
>>
>> in userAddHandler, if userPrefixEnabled is False, process as normal.
>> If true, append the selected username to the aliases and set the
>> username to Site##_### or userPrefix###. We'd need to look at the
>> users in the site/users directory and find the highest existing user,
>> but I don't think that would be too hard.
>
> Yeah, that's a nice idea. I see some potential obstacles in the form
> of that
> Java script that suggests a username when you enter the full name.
> So that
> needs to be tweaked as well. But aside from that it's certainly
> doable and
> would be a nice addition.
Michael,
Oops, right. I'm guessing we'd have to turn off the suggestion code if
the userPrefix was defined for a site. I've been playing around with
this on my test environment... trying to get it just right, but
haven't even approached the scenario of an existing user that already
fits the bill. I probably should look at the usernames of every user
on the box to check for duplicates (what a pain).
I'm juggling a few things right now, but I'll try to get back to this
soon.
Greg
------------------------------
Message: 5
Date: Fri, 27 Mar 2009 15:03:43 +0100
From: Michael Stauber <mstauber at blueonyx.it>
Subject: [BlueOnyx:00879] Re: Feature Requests
To: BlueOnyx General Mailing List <blueonyx at blueonyx.it>
Message-ID: <200903271503.44278.mstauber at blueonyx.it>
Content-Type: text/plain; charset="utf-8"
Hi Greg,
> Oops, right. I'm guessing we'd have to turn off the suggestion code if
> the userPrefix was defined for a site.
Depends. I'd prefer to adjust it to get it working for both scenarios.
> I've been playing around with
> this on my test environment... trying to get it just right, but
> haven't even approached the scenario of an existing user that already
> fits the bill. I probably should look at the usernames of every user
> on the box to check for duplicates (what a pain).
The existing code already handles cases such as "username already
taken", so
that should be no big deal.
--
With best regards
Michael Stauber
------------------------------
Message: 6
Date: Fri, 27 Mar 2009 10:32:38 -0400
From: "Greg O'Lone" <blueonyxlist at stretchedout.com>
Subject: [BlueOnyx:00880] Re: Feature Requests
To: BlueOnyx General Mailing List <blueonyx at blueonyx.it>
Message-ID: <C9748AC4-7689-4FEE-AA9A-E3DB9B7C21E7 at stretchedout.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
On Mar 27, 2009, at 10:03 am, Michael Stauber wrote:
> Hi Greg,
>
>> Oops, right. I'm guessing we'd have to turn off the suggestion code
>> if
>> the userPrefix was defined for a site.
>
> Depends. I'd prefer to adjust it to get it working for both scenarios.
>
>> I've been playing around with
>> this on my test environment... trying to get it just right, but
>> haven't even approached the scenario of an existing user that already
>> fits the bill. I probably should look at the usernames of every user
>> on the box to check for duplicates (what a pain).
>
> The existing code already handles cases such as "username already
> taken", so
> that should be no big deal.
Michael.
I wasn't thinking that the VSite administrator would have the ability
to edit the usernames if a prefix was set, but that's an interesting
point. I guess it could allow just about any suffix to be used,
although my original plan was to make it so conflicts did not happen
by assigning usernames numerically (SOS_001, SOS_002, SOS_003).
The problem I see with allowing the admins to change usernames is that
they could create their own conflicts (which is what I'm trying to
avoid). Imagine two sites, one with a prefix of SOS and one with SOST.
The first admin makes a user SOSTREBECA for a user named Tom Rebeca.
The second admin tries to create the same user SOSTREBECA for a user
named Rob Ebeca. It's not likely, but I'm all about idiot proofing.
There was a time when I "suggested" to admins that they use the first
8 characters of their domains and a 3 or 4 digit number to assign
usernames. Most of them were okay with the idea. The troublemakers are
the casual hosting customers who all want the "info" username...
I know that the current interface limits usernames to 12 characters
(or something like that). Do you know if this is a limitation of Linux
or Sausalito?
Greg
------------------------------
_______________________________________________
Blueonyx mailing list
Blueonyx at blueonyx.it
http://www.blueonyx.it/mailman/listinfo/blueonyx
End of Blueonyx Digest, Vol 3, Issue 38
***************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20090327/b6edb669/attachment.html>
More information about the Blueonyx
mailing list