Crash when updating site cache? MM_Username1?

Question

Hi,
All of a sudden, tonight, DW8.0.2 will no longer open or load
one of my
sites, crashing when "Updating Site Cache". The site is ASP
linked to an SQL
database.
Checking the file that the cache gets to, I notice that the
problem file is
within a sub-directory of the site, called "/admin". Thing is
though, it's
not always the same file, but it IS always a file within the
/admin
sub-directory.
Within this sub-directory I altered, by hand, the Login User
code and
Restrict Access to Page code to create and use the session
variable
MM_Username1 as opposed to the default MM_Username.
Could this be the reason for the sudden trouble with the site
cache? I am
puzzled because the site was working fine for a few weeks
now, with this
sub-directory included, and I didn't create the MM_Username1
issue today
either, it has also been working fine for a good few weeks
now. I've also
not added anything new to the site, that I am aware of.
When I remove the sub-directory from the site, the Updating
Site Cache works
fine, so I am 100% sure there is a problem with the files
within this
sub-directory. How will I know which one though?
I've tried this, as recommended by Adobe, but I still get a
freeze-up when
re-creating the cache:
1. Try renaming the Dreamweaver user configuration folder, so
that
Dreamweaver will automatically generate a new user
configuration folder the
next time Dreamweaver launches. The Configuration folder is
located here:
C:\Documents and Settings\<username>\Application
Data\Macromedia\Dreamweaver
8\Configuration
2. Recreate your Dreamweaver user settings in the registry as
follows:
Launch the Registry Editor by clicking the Start button,
choose Run, then
type "regedit". In the Registry Editor, navigate to this
folder:
HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
Rename the "Dreamweaver 8" key to "DreamweaverOLD", so that
Dreamweaver will
automatically generate a new user settings key the next time
you launch it.
3. Recreate your Dreamweaver site definitions in the registry
as follows.
The steps below will delete your site definitions in
Dreamweaver.
4. Launch the Registry Editor by clicking the Start button,
choose Run, then
type "regedit". In the Registry Editor, navigate to this
folder:
HKEY_CURRENT_USER\Software\Macromedia\Common\8\Sites
Rename the "Sites" key to "SitesOLD", so that Dreamweaver
will automatically
generate a new Sites key the next time you launch it.
Any further advice?
Regards
nath.

Answer 1

Found it! Jeesh.
I had a querystring value in my UPDATE redirect URL which was
coded
incorrectly!!!
I am frustrated that, rather than just highlighting the error
or, at the
very least, producing an error when opening the specific
file, this type of
thing crashed the entire DW programme.
The time I spent in Notepad today changing MM_Username1 back
to
MM_Username!! Turns out that was nothing to do with it.
<groan> Yeah,
that's right, laugh it up! :o)
Anyway, solved now. A misplaced ", %, ), (, <, >, &
etc can cause you no
end of grief! :o(
Nath.
"tradmusic.com" <[email protected]> wrote in
message
news:[email protected]...
> Hi,
> All of a sudden, tonight, DW8.0.2 will no longer open or
load one of my
> sites, crashing when "Updating Site Cache". The site is
ASP linked to an
> SQL database.
> Checking the file that the cache gets to, I notice that
the problem file
> is within a sub-directory of the site, called "/admin".
Thing is though,
> it's not always the same file, but it IS always a file
within the /admin
> sub-directory.
>
> Within this sub-directory I altered, by hand, the Login
User code and
> Restrict Access to Page code to create and use the
session variable
> MM_Username1 as opposed to the default MM_Username.
> Could this be the reason for the sudden trouble with the
site cache? I
> am puzzled because the site was working fine for a few
weeks now, with
> this sub-directory included, and I didn't create the
MM_Username1 issue
> today either, it has also been working fine for a good
few weeks now.
> I've also not added anything new to the site, that I am
aware of.
>
> When I remove the sub-directory from the site, the
Updating Site Cache
> works fine, so I am 100% sure there is a problem with
the files within
> this sub-directory. How will I know which one though?
>
> I've tried this, as recommended by Adobe, but I still
get a freeze-up when
> re-creating the cache:
>
> 1. Try renaming the Dreamweaver user configuration
folder, so that
> Dreamweaver will automatically generate a new user
configuration folder
> the next time Dreamweaver launches. The Configuration
folder is located
> here: C:\Documents and
Settings\<username>\Application
> Data\Macromedia\Dreamweaver 8\Configuration
>
> 2. Recreate your Dreamweaver user settings in the
registry as follows:
>
> Launch the Registry Editor by clicking the Start button,
choose Run, then
> type "regedit". In the Registry Editor, navigate to this
folder:
> HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
> Rename the "Dreamweaver 8" key to "DreamweaverOLD", so
that Dreamweaver
> will automatically generate a new user settings key the
next time you
> launch it.
>
> 3. Recreate your Dreamweaver site definitions in the
registry as follows.
> The steps below will delete your site definitions in
Dreamweaver.
>
> 4. Launch the Registry Editor by clicking the Start
button, choose Run,
> then type "regedit". In the Registry Editor, navigate to
this folder:
>
> HKEY_CURRENT_USER\Software\Macromedia\Common\8\Sites
>
> Rename the "Sites" key to "SitesOLD", so that
Dreamweaver will
> automatically generate a new Sites key the next time you
launch it.
>
> Any further advice?
> Regards
> nath.
>