PhotoPost Community - View Single Post

dr-agon · April 5th, 2006, 01:03 PM

OK, thanks for your commitment to seeing this through, Chuck. Here's the story of where I'm at and how I got there...

...I tried what you suggested, to try relaxing the options. The way I lock the whole site out to non-members is to set the default "Can View Forum" permissions for the "Unregistered / Not Logged In" to No. So, I changed this to Yes, and tried again..no difference.

At this point my wife began to get fed up with my whining and sat down with me for some debugging (she used to be a Unix programmer), and in the course of that discussion, it was identified that when I switched the integration of PP with my VB3 test instance, instead of the live one, I didn't change the User database setting in config-inc. This is what led to be a strange login loop that was making it so tough to get into the PP admin! I fixed the config file, and now I can get into PP admin via the Admin link on the PP home page (i.e. so long as I log into the user front end first).

I still cannot log straight into PP admin directly from adm-index.php (displays a blank screen), but I figure that maybe it was never intended to get directly into admin without first logging into the front end, in a VB integrated configuration. In any case I'm happy going via PP home page.

In summary, the key to the problems I was having was down to the relative URLs in the VB3 STANDARD_ERROR and headinclude templates.

Thanks again, Chuck.

April 5th, 2006, 01:03 PM	#15 (permalink)
dr-agon Junior Member Verified Customer Join Date: Apr 2006 Posts: 8	All resolved...with a little help! OK, thanks for your commitment to seeing this through, Chuck. Here's the story of where I'm at and how I got there... ...I tried what you suggested, to try relaxing the options. The way I lock the whole site out to non-members is to set the default "Can View Forum" permissions for the "Unregistered / Not Logged In" to No. So, I changed this to Yes, and tried again..no difference. At this point my wife began to get fed up with my whining and sat down with me for some debugging (she used to be a Unix programmer), and in the course of that discussion, it was identified that when I switched the integration of PP with my VB3 test instance, instead of the live one, I didn't change the User database setting in config-inc. This is what led to be a strange login loop that was making it so tough to get into the PP admin! I fixed the config file, and now I can get into PP admin via the Admin link on the PP home page (i.e. so long as I log into the user front end first). I still cannot log straight into PP admin directly from adm-index.php (displays a blank screen), but I figure that maybe it was never intended to get directly into admin without first logging into the front end, in a VB integrated configuration. In any case I'm happy going via PP home page. In summary, the key to the problems I was having was down to the relative URLs in the VB3 STANDARD_ERROR and headinclude templates. Thanks again, Chuck.