Hi,

That is not enough to go on. I need details in order to help.

Could be a mod I guess - it would be nice to have an option on the admin settings page to lock down access of all pages and redirect to a specified  "lockdown" page upon attempted login.

If I'm updating the large files on the server and someone attempts a download, they'll get a partial ZIP file or an error.

Trying to make sense of this.  I am still confused.  In the file config_inc.asp.  I found the setting for "uploaddirectory".  That entry looks like this [UploadDirectory = CmdGetConfiguration("UploadDirectory")].  I assume there is a config file where the value of upload directory is located. 

The settings in the config_inc.asp file have not been changed.  they are set to the way it was delivered.  Is there a document that gives instructions as to what and where the config settings are to be changes?

We have a site that currently runs ASPProtect and would like to install a second instance of it.  The reason is that the current one is set up to manually authorize new users (it is for applying discounts to the Trade), but we want a second instance that will allow new users to register freely (this is for personalization). 

Has anyone set up such a goofy scenario themselves?  Is this even possible?

Thank you!

As an update to this thread I fixed the "upload_post.asp" page quite some time ago but forgot to post the updated file here.

So here it is.

2005-09-16_165913_upload_post.zip

It's just a generic error that means one of 1000 different things is wrong.. there is a lot of information on in in these forums as well as links to articles about it.

http://support.cjwsoft.com/forum/forum_posts.asp?TID=27& PN=1

usually it means permissions to the database folder are incorrect or the physical path you are specifying for your dsn-less connection is invalid..

everything has to be perfect

Can I have the logon be in a top frame while having the protected pages displayed in a main frame?

Using frames with forms based authentication is not the best thing to be doing. Your much better off not using frames and using includes files to do a virtual frames sort of thing (search google) but if you are going to use frames I would suggest password protecting the frameset page as well as any pages it contains.

If you want to have a login form in a non protected top frame all the time.. that posts to a lower frame that is password protected.. you would do this
http://support.cjwsoft.com/code/moreinfo169-1.htm
but change the target of the form to one of your frames

personally though I think that would be a somewhat goofy setup to have going on


Also, how will it behave if a user moves in between a protected page to a public page and back to the protected page again?

As long as they have cookies enabled which is required for session variables to work... then you will have no issues because once they come back to a page they have permission to they will just be allowed in without login.. at least while that session is still active.. or for a longer time if they choose the remeber me option which keeps track of them with a cookie .

Really, the best thing to do is expirment and see how things behave.

Great Thank you!

As of thus far the program is working rather nicely.

I am very impressed :)

Christopher,

Thank you again Sir. Your quick responses and helpful demeanor add greatly to the value of your software.

There is no way I'm going to spend hundreds of dollars for a thumbnail creation program. Mine is a family web site and all out of my pocket.

Is there any free products that work with Gallery that will create the thumbnails? If not can I create them on my own and link them to the pics? There are tons of Perl based freebies out there.

Steve

I know what is happening.. its the old single quote thing messing up the query string..
but it shouldnt be happening with the newer code as I fixed it.

If you like I can go in and reproduce/fix the issue. I can not think of any other way I can help you as other users have not reported the issue.

Chances are if it is happening in one situation it will happen again in the future.. it really all depends on the passwords being used and your encyrption key... other passwords may produce the issue even if the password is correct

basically once the password gets encrypted it by chance has a single quote in it... then it messes up the query

I take care of the situation by replacing the single quote with a double quote but it looks like you found a situation where that didn't work out

humm, I dont know.

If you want me too I would be glad to go into your web site and troubleshoot. If so PM me the info I need and I will take a look and see if I can figure it out.

CJW

let's try this... edit that page with a text editor like notepad...

Carefully replace any instance of "Cint" with "CDbl".. I may have missed some of those when testing the last time I edited the code.

ok

The Read-only attribute i was referring to is at the windows explorer level when looking at the folder properties under the general tab. 

ASPNET and IUSR have full access to the _database folder as you suggested - Yet still I get the permission error noted above.

I wonder if this could this be a FrontPage problem. I deleted the skins folder and re-ftp'd the original one that only contains default and Solid Black. I logged in and tried to change it back to default but it won't. I'm going to try making this folder a Frontpage subweb to see if that makes a difference.

Al

Different Versions of the Access Database

Below is a zip file with many alternate versions of the Access Database provided to help with installation and general usage.

2005-02-20_155310_ASPProtect_Database_Versions.zip

ASPProtect.mdb is saved as an Access97 database (password "temp")
ASPProtect_access2000.mdb is saved as and Access 2000 database (password "temp")
ASPProtect_access2000.mdb is saved as and Access 2002-2003 database (password "temp")
ASPProtect_access2002_no_password.mdb is saved as and Access 2002-2003 database with no password set on it

Try to use the newest version as server odbc drivers sometimes have to use the newest version for everything to work correctly. No password version is provided because sometimes there are issues connecting to a database with a password set on it.

Default username for access databases is of course "admin" but you really dont use that except in the data connection information.

Okay,  I deleted out the aspprotect folder and started over.  I also took out the dsn connection to the ecommerce database and deleted out the subweb that had it, I decided to use another provided where the database is resident on thier servers not mine.

I broke my txt file into groups and it's loading sort of.  The first 1000 users uploaded fine...the second said it timed out, but when I looked at the access database it showed 2000 people.   The login still times out and every page seems to load incredibly slow still.

When I enter www.vickerylightning.com/aspgallery/dataconn_inc.asp on the screen it says "Not a valid bookmark"

as far as that goes I have no idea.. I have never seen that message before but you are not suppose to run that page by itself regardless.. it is an include file not meant to run on its own

Thanks for that. The upload size is just as effective and possibly a better solution to maintain server space.

What about individual gallery permissions. So only 1 member can post in only 1 gallery. I have a forum of 500 plus members so if they want to add a gallery than setting a permission would be idea for each gallery.

Hi, I haven't heard anything from you.

Has this issue been resolved ?

Thanks

you do not run "check_user_inc.asp" by itself

Pages you protect include that file at the top.. when they someone goes  to a protected page if not logged in a user then sees a login prompt..

after loggin in they see that same page as normal

its an automated process..

now, that being said if you really want to you a specify a page to be redirected to after the 1st login when you edit a users info. You can also redirect anyone anywhere like using a simple ASP redirect statement in your code.

Personally I feel that redirecting people all over the place is poor site design. ASP is all about dynamic code and ASPProtect is all about dynamically tailoring pages to the current logged in users... so why redirect people all over the place.. it justs complicates things because you still need to password protect the places you send them to.... which means twice the work and twice the confusion.


Also, here is a Version 6 thread about redirecting manually that still applies to version 7.

http://support.cjwsoft.com/code/moreinfo17-1.htm

Great software.

How easy would it be to copy the email address entered at registration directly into the login id field so that the user's email address is automatically used as the login id? 

Also, where in the code can I turn off the random password generator - I'd rather force people to pick something they can remember themselves.

Thanks,

Nick

Kurt,

There really is no default width in general.

The thing to remember is that the default.asp page includes a lot of different pages.. and some of those pages also include pages.

Now all of this gets wrapped by the header and footer include files so in a sense what you do there can effect everything inside to a certain degree.

Now there are some widths set here and there for different tables and what not on certain pages, but its really the kind of situation where you just have to dig around in the code and experiment until you eventualy find what you are looking for and get the desired result.

I'd love to tell you there is easy way to just set a width, but it is not that simple.

Maybe someday it will be. Just not in the current version.

CJW

Your users with Internet Explorer may have received the "Page Expired" error.  For ASPProtect users, it happens when  the user is not logged on and tries to invoke the target page. check_user_inc.asp puts up the login form, and IE sees it as part of the target page.  Any later attempt to Back up and reload from cache gives the errror. 

DONE IT

DON'T WORRY!

DON'T ASK HOW, BUT NOW IT WORKS!!

THANK YOU IF IT WAS YOU, OR THANK YOU GOD IF IT WAS ME!!!