| Author |
|
research
New User
Joined: May/31/2006
Location: United States
Online Status: Offline
Info: 2
|
| Added: May/31/2006 at 4:59pm | IP Logged
|
|
|
We have an issue with the Microsoft FrontPage "Edit button" -- it does not work in the password protected area of our website.
It is fuctional on the unprotected area of our web, but when we switch
to the password protected area, the Edit Button is "dimmed" and will
not work. Since we have hundreds of pages to update, this is a
big problem.
Before we began using ASPProtect as our user manager, we had no problem
accessing the protected area (we used a different application) with the
Edit Button.
If anyone else has encountered this or has a soltution to the problem please let us know.
Thanks!
__________________
N.Ray
|
| Back to Top |
|
| |
cwilliams
Admin Group
CJWSoft Web Software Developer
Joined: April/06/2004
Online Status: Offline
Info: 1769
|
| Added: June/01/2006 at 12:33am | IP Logged
|
|
|
Hi,
I have seen that happen before with a lot of my sites using various types of asp code. Not always password protected pages. To be honest I have never understood or been able to find out why it happens. Frontpage extensions can act pretty random at times regarding that. I have even noticed pages doing it randomly with no changes to the code.
I have no solution except that you cant do that anymore. Personally when editing my own sites I use a page with the edit button to get quick access to the site then navigate where I need to once in. Either that or file open website...
__________________
Best Regards,
Christopher Williams
www.CJWSoft.com
|
| Back to Top |
|
| |
cwilliams
Admin Group
CJWSoft Web Software Developer
Joined: April/06/2004
Online Status: Offline
Info: 1769
|
| Added: June/04/2006 at 3:04pm | IP Logged
|
|
|
I quite accidently found a possible fix for you while working on one of my own sites and wondering why the edit button was not showing.
If you remove this section of code from the "dataconn_inc.asp" file then the edit button may work again
<%
response.expires = 0
response.expiresabsolute = Now() - 1
response.addHeader "pragma","no-cache"
response.addHeader "cache-control","private"
Response.CacheControl = "no-cache"
%>
The downside is that code is there for a reason. It prevents browser caching which under a forms login scenario can cause trouble..
For example it can sometimes show a cached version of the login page when you navigate back to it even after you logged in...
__________________
Best Regards,
Christopher Williams
www.CJWSoft.com
|
| Back to Top |
|
| |
research
New User
Joined: May/31/2006
Location: United States
Online Status: Offline
Info: 2
|
| Added: June/05/2006 at 3:28pm | IP Logged
|
|
|
Thanks for the info and it appears that you are correct since the EDIT
button is now working. We will have to see if any secondary problems
arise with the browser caching-- but so far, so good.
I ran across many others who have this problem while surfing for an answer so I'll pass it on..
good job.
__________________
N.Ray
|
| Back to Top |
|
| |
Active Info
Memberlist
Search
Help
Register
Login
Info: MS Frontpage EDIT BUTTON
