Great program is CCount however I've noticed a problem with the script.
It allows a person to simply modify the URL to view all click counter re-directs simply by changing the: URL /click.php?id=(ID).
It would be great to introduce a password on selected links while creating and/or editing link entries, you could have a predefined password failure redirection page too.
I'm sure it wouldn't be too harder feature to add to an otherwise fantastic bit of software. I look forward to it, it in my case is an essential addition for my software download monitoring.
Password protection on links
Password protection on links
World's shortest poem: We, see.
No reply, is people on holiday?
I posted the last comment/suggestion a while ago and have not had as yet a reply, wasup?
World's shortest poem: We, see.
It is probably a bit harder to realise than you imagine.
And since nobody had a solution to your question, nobody reacted.
For instance, i have read your request. But it would no be contribute to just state that i can not do this for you. So when you do not get a response it is best to assume that nobody is able to help you.
Greetings,
Henrie
And since nobody had a solution to your question, nobody reacted.
For instance, i have read your request. But it would no be contribute to just state that i can not do this for you. So when you do not get a response it is best to assume that nobody is able to help you.
Greetings,
Henrie
I do not monitor the Gbook forums regularly anymore since I do not use the Gbook script myself anymore for a long time. But it helped me a lot in learning to understand php.
re; Secure Click counter: Update
Thanks for commenting on my suggestion, however knowing just how good Klemen is at creating unique and effective software & the accompanying updates. I have faith that such an idea could be implemented.
One could implement an in-line text file password database incorporating an .htaccess file set that would allow a user to select a pre-defined password while generating a new click-link.
So when the respective ccount link is selected the click.php ID argument is passed through the password check include (if/when enabled), and redirects the user if the password doesn't match the links stored password.
I believe ccount is an amazing counting/re-directing solution, and any ideas should be encouraged to advance this already brilliant product.
Having a ccount (secure) I think would be a great addition to the PHPJunkYard collection. Don't you agree?
One could implement an in-line text file password database incorporating an .htaccess file set that would allow a user to select a pre-defined password while generating a new click-link.
So when the respective ccount link is selected the click.php ID argument is passed through the password check include (if/when enabled), and redirects the user if the password doesn't match the links stored password.
I believe ccount is an amazing counting/re-directing solution, and any ideas should be encouraged to advance this already brilliant product.
Having a ccount (secure) I think would be a great addition to the PHPJunkYard collection. Don't you agree?
World's shortest poem: We, see.
A solution that I have been playing with is in the works, as I have never liked just simple sequential ID's my self my idea is to accept custom ids that follow no sequence unless you want them to, so what I have done is to mod the script to allow for custom id codes like 1056, 425 I think this is a cool idea to toss around in my opin as I am not so sure about PW protected redir links ...
I think PW is kind of over kill, its just a redir its not a link to the MINT any way if you like this idea I may post it I had to think how to make this work as the way it is by defualt this is not possable but I feel I now have some code in testing that works as both custom id input via another custom ID field or the way Klem intended it to work without breaking the script.
So with this idea we can have the best of both worlds.
DC
I think PW is kind of over kill, its just a redir its not a link to the MINT any way if you like this idea I may post it I had to think how to make this work as the way it is by defualt this is not possable but I feel I now have some code in testing that works as both custom id input via another custom ID field or the way Klem intended it to work without breaking the script.
So with this idea we can have the best of both worlds.
DC
To Code Or Not To Code That Is The Question?
Was my post of any help to you? if so please do [url=http://www.clickcraft.net/slice_donations.php][b]Buy Me A Slice[/b][/url] ...
Was my post of any help to you? if so please do [url=http://www.clickcraft.net/slice_donations.php][b]Buy Me A Slice[/b][/url] ...
Re; custom id codes
I think that's not a bad idea, however the reason I originally suggested an optionally set password protected link was so that when one wants to count say the downloads of a piece of software, however it's not so easy to protect or even restrict access to the link/download.
two methods could be used with the existing script without much in the way of modification to the current package.
One: Where the script is currently formatted thus: ccount/click.php?id=1
the script with customisable generate ID's as suggested, would indeed affect a code like link. less chance of landing on just randomly guessed ID's.
Two: Having an (optional) password set when admin creates the ccount link, would prevent a user from guessing link ID's, as the wrongly entered ID gets redirected to a pre-defined page/link. The password could either be entered separately via the ccount script, or entered as part of the ccount link ID.
So far I have toyed with using two ccount scripts to protect software download locations, the first script acts as a public link and counter, and the second script redirects the clicked link to a hidden location. Unfortunately this approach still doesn't prevent a user from randomly entering the first ID. Hence the requirement for a password.
two methods could be used with the existing script without much in the way of modification to the current package.
One: Where the script is currently formatted thus: ccount/click.php?id=1
the script with customisable generate ID's as suggested, would indeed affect a code like link. less chance of landing on just randomly guessed ID's.
Two: Having an (optional) password set when admin creates the ccount link, would prevent a user from guessing link ID's, as the wrongly entered ID gets redirected to a pre-defined page/link. The password could either be entered separately via the ccount script, or entered as part of the ccount link ID.
So far I have toyed with using two ccount scripts to protect software download locations, the first script acts as a public link and counter, and the second script redirects the clicked link to a hidden location. Unfortunately this approach still doesn't prevent a user from randomly entering the first ID. Hence the requirement for a password.
World's shortest poem: We, see.
I will probably be posting my mod for custom ID's you can then try and play with that if you like, But do keep in mind that CCount is a text based flat file script so it shouldn't really be used to track masive amounts of links as text based scripts can get corrupted if the data write fails to complete on a large file containing a ton of data. If you are tracking large amounts of links your best bet is a MYSQL based script.
I am just letting you know this incase you were not aware.
UPDATE: I have posted my mod.
viewtopic.php?p=13360#13360
DC
I am just letting you know this incase you were not aware.
UPDATE: I have posted my mod.
viewtopic.php?p=13360#13360
DC
To Code Or Not To Code That Is The Question?
Was my post of any help to you? if so please do [url=http://www.clickcraft.net/slice_donations.php][b]Buy Me A Slice[/b][/url] ...
Was my post of any help to you? if so please do [url=http://www.clickcraft.net/slice_donations.php][b]Buy Me A Slice[/b][/url] ...