[PHP] Re: Inline Frame and php

2005-03-07 Thread f00l
Hi,
Would I be right in assuming that the top frame has the search button but 
when searching, the results appear on a new window? or the main window?

Greg

Todd Cary [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 My client insists on using inline Frames that uses my php pages.  As an 
 example, this is on one page:

 IFRAME target=_top frameborder=0 
 SRC=search.php?search_text=?echo($search_text);? WIDTH=592 HEIGHT=282
 /IFRAME

 This works well with the control being given to search.php.  What I do 
 not understand is that within search.php, I have a statement that is 
 suppose to pass control to anther page.  The line is

 header(location: http://192.168.0.23/mypath/mypage.php;);

 Rather than going to the page, it opens mypage.php in the inline frame.

 Is there a way to leave the inline frame?

 [Excuse my nomenclature e.g. control, leave]

 Todd 

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP] Shoutbox without sql dbase

2005-03-07 Thread f00l
Hi all,
I was wondering if anyone has come across (or even using) a shoutbox that 
doesnt require an sql dbase. While it isnt hard to access one id prefer to 
write everything to a file (wanting to learn how to write, append etc files)
I tried one but for some reason the script processing turned into some 
random java script about symwindow openning etc   -has anyone heard of this 
or know what it means?

Thanks all

Greg 

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] Semi-OT: Anti-password trading/sharing solutions

2005-03-07 Thread f00l
Come here to get help, not abuse
for what its worth:
sql dbase with fields
usernamepassiptime
if duplicate username/passowrd then check that IPs match and dont do 
anything
if IPs  match then kick both users off / disable username/password

go figure the code out yourself
here is the idea which is the most you have got out of anyone

Dan [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 Richard Lynch wrote:
 Dan Trainor wrote:

 I'm not quite sure why you chose the PHP community as a recipient --  
 There
 are quite a few Apache modules out there.

 And Modules such as mod_auth_mysql and mod_auth_ldap (?) and, really, any
 old mod_auth_XYZ module would be a closer match for what you want, I
 think.

 I know absolutely nothing about how ProxyPass, iProtect, and PureMember
 work, however, so perhaps there is something about them that just screams
 use PHP to do this  [I doubt it though]

 It seems to me, however, that you're still a bit off-target on
 PHP-General, as your target audience is not those who use PHP, but those
 who wrote it and maintain it, particularly the Apache Module part of it.

 I believe, in fact, that the Apache Module part of it boils down to the
 code Rasmus Lerdorf wrote ages and ages ago, and that mostly Rasmus (I
 think) has maintained since then.

 Perhaps with Apache 2, somebody else stepped up to write/maintain that
 code, and I'm under-informed.

 Or maybe Rasmus hasn't touched that code in ages, and somebody else is
 doing it now.  Apologies to those individuals who I've slighted by not
 naming them at this time.

 At any rate, you're trying to get in contact with a handful of people by
 sending email to thousands.  Bad Idea #1.

 NOTE: Contacting Rasmus directly and offering him $$$ to do this would
 maybe not be a Bad Idea.  Asking him to do it for free would be really
 stupid.

 Next, let's look at your proposal:

 You want something that Member Sites need, to avoid the theft/sharing of
 username/passwords.

 So, in particular, only for-pay Member Sites need this, mostly, as 
 there's
 not much point in stealing/sharing a username/password if you can just 
 get
 one for free.

 So, basically, it's a for-profit motivator that drives this request.

 Yet nowhere do I see an offer of recompense for the developers who write
 this software for you.  Bad Idea #2.

 I highly recommend you figure out what it would be worth to you and some
 of your colleagues/friends to have an OpenSource solution to rival the
 current proprietary technologies.

 Take up a collection or form a very loose consortium with some of your
 colleagues to fund the project.

 Then write up a specification for what you want done, and make an offer 
 to
 PAY somebody and fund the resources needed to get the project from its
 current state (gleam in your eye) to a usable state.

 You could and probably should still make it OpenSource -- Perhaps with
 Funded by:  attributions on all source code and materials to plug your
 consortium and its members -- and then when it's at the stage of
 usefulness that you need, you will probably find that some people are
 willing to maintain it for little or no money at all.

 Right now, though, you've got a lot of people seeing:

 I want you to work for me for free so I can save thousands of dollars
 every month

 That ain't gonna happen, dude.

 People wrote PHP and Apache and other OpenSource software because THEY
 needed it for THEIR own use, and were willing to give it to you for FREE
 because they knew that giving away 10,000 free copies would get them one
 (1) more Developer to help build/improve the software.

 They did *NOT* do it because they wanted you to be able to run your
 company on free software.

 Which is not to say that they *MIND* that you can do that -- Only that
 they're not going to just up and code something just because *YOU* happen
 to need it to run your company more efficiently.

 You've got zero incentive for the Developer here -- They don't need the
 Module you want, and you're not paying them.  [shrug]



 Go ahead and look at my first email.  For some reason you didn't get the 
 idea that I was looking for solutions.  Ideas.  I wasn't looking for 
 anything solid.

 The reason why I wrote to the PHP community was to get some ideas. Aside 
 from the two people who have sent me hatemail today, the PHP comunity is 
 very intelligent, very clever, and might have worked on something like 
 this in the past.  That's the information that I was after.

 Rasmus?  Waht's he got to do with anything?  Sure, I value and credit the 
 work he's put into PHP, but I really think that using his name in this 
 context has no point.

 Who asked anyone to write any software for me?  Again, let's focus on the 
 primary purpose of this email - to gather information so that I can do 
 some further investigation.

 You know, you're right.  It's stupid for me to think that Open Source 
 software is used in for-profit situations.  PHP, Apache, MySQL, 

Re: [PHP] Pop-up message

2005-03-07 Thread f00l
not knowing much about php myself but you could ask phpBB  about their 
private msgs. i cant recall whther it is a mod that pops the window up on 
receiving a msg or whether the user is online (probably configurable). But 
as far as direction, that is where i would be heading :)
Greg

Richard Lynch [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 Lester Caine wrote:
 At the risk of being shouted at because *I* know it's not a PHP problem!

 Actually, it's a client problem :-)

 I have a page that is being refreshed every 30 seconds or so, and
 displays a list of 'tickets' waiting to be dealt with on a list from a
 database query. No problems there, but a couple of sites now want me to
 add a pop-up warning when a ticket is added that has a staff ID matching
 the logged in user.

 Your first task is to convince the client what an incredibly stupid idea
 this is.

 And that it won't work with all the popup blockers.

 And if it did work, it would just annoy the [bleep] out of their users.

 I know I'm preaching to the choir, here, but I have to go on record with
 this statement.

 I can drive a sounder in the target browser, but need kicking in the

 A sounder?  You mean like make my browser make noise?  ICK!!!

 right direction for a method of adding a pop-up window. Ideally it needs
 to be browser agnostic, which is where the problem comes given the
 pop-up blockers and other 'toys' that are being added to the browser end
 of things.

 You're not going to defeat the popup blockers in the long run.

 You are better off using clean simple code in an onLoad in your body tag
 to open the new window.  Something like:
 body onLoad=window.open(URL);
 where the URL loads in that user's recently added items.

 Either the users will accept the popup and whitelist it in their popup
 blocker, or they won't.

 And if a lot of them don't accept it, as they shouldn't, that tells you
 right there what a dumb idea this was. :-)

 But running around to find code to defeat the popup blockers will be a
 total waste of time -- and you'll end up with something so hacked and so
 un-maintainable that you'll have to fix it every six months, even if the
 popup blockers don't find workarounds to block your workarounds that popup
 the windows that they don't want popped up.

 So can anybody point me in the right direction for a CURRENT method of
 achieving this, many of the bits I've found so far are somewhat
 antiquated, and fail in one way or another :(

 Perhaps it would be better to segregate the tickets into those associated
 with the User logged in, and those that are not.

 Or to at least sort them that way, regardless of their other sorting 
 options.

 For that matter, don't even *BOTHER* to show me items that aren't mine,
 unless I specifically ask for them.

 Build a system that detects tickets that sit un-assigned for too long, and
 randomly assigns them, or, better yet, assigns them based on factors such
 as:
 Ticket features (IE, interface tickets to interface team members)
 Productivity (IE, don't assign as many tickets to your slow team members
 as your fast ones)
 User Status (IE, if I'm on vacation, don't assign me anything)
 .
 .
 .

 That way, no tickets is left sitting there too long but nobody has to
 deal with tickets that aren't assigned to them.

 Just an idea.

 In general, though, I only mean:

 Come back at the client with more than just That's a dumb idea (which it
 is)

 Come back with a Here's a MUCH better way to do this proposal.

 That's a dumb idea just gets you more headaches.

 A solution for a better solution makes you look real smart. :-)

 Yes, this may turn out to be a waste of your time, because the client is
 REALLY dead set on these popups, and you'll end up being miserable about
 them not taking your proposal as well...  Time to start looking for a new
 client. :-v

 -- 
 Like Music?
 http://l-i-e.com/artists.htm 

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php