"Save" & insert snippet greyed out with framesets

[RobCatman]

[Topic edited for clarity.]

Using DW 19.0.1 build 11212

First,

Only on certain files, the "save" option (under File) is greyed out, I cannot ctrl-S.  I can exit DW and it asks if I want to save the changes before exiting.  I choose yes, it works, but I cannot save it normally.  This isn't on every file, only on certain ones.

Secondly, on the same files, I am unable to insert a snippet.  If I double-click on the snippet - Nothing.  If I right-click, "insert" is greyed out.

I've deleted the cache per other instructions I've found here but to no avail.

Any pro tips for this?

Thanks,

-=Rob=-

[Nancy OShea]

Validate code and fix reported errors.  See screenshot.

[RobCatman]

Nothing shows up.  This is existing code that is currently being used in production that I'm having issues with.

[Nancy OShea]

Can you show us the code?

[RobCatman]

Sorry, I can't.  An "error" pops up when I load the program, referring to not being able to find the file #variables.urlsearch# but that isn't truly an error as the variable gets resolved earlier in the program.

<frame name="browse" src="#variables.urlSearch#" scrolling="auto" >

[RobCatman]

Interesting development - If I comment out the following code, everything works fine.  This is all working great in PRD . The only issue I would see is the "UntitledFrame-3" piece as that doesn't exist, but if I remove it or replace it with a valid filename, I still don't have the option to save.  It seems strange to me that this happens as I can be in the middle of writing a program and save, close, reopen, and continue editing and saving.  Saving every-so-often should be a habit.  I don't get why it would STOP you from doing that.

<frameset cols="250,*" frameborder="1">

<frame name="browse" src="#variables.urlSearch#" scrolling="auto" >

<frameset rows="#getRecord.BottomFrame#,*" frameborder="0" framespacing="0">

  <frame name="bbar" target="bbar" src="bbar.cfm" scrolling="no" >

     <frame name="main" target="main" src="blankPage.cfm" border="0" scrolling="auto">

</frameset>

<frame src="UntitledFrame-3">

</frameset><noframes></noframes>

[Nancy OShea]

OMG!  You're using  FRAMES.   You realize FRAMES are dead, right?  HTML5 doesn't support them.  Dreamweaver doesn't support them.  Mobile phones don't support them. Some browsers have stopped supporting them.   MDN says don't use FRAMES.  So why are you still using FRAMES in 2019?

<frame> - HTML: Hypertext Markup Language | MDN

[RobCatman]

Hey, this isn't *my* code.  I've just been asked to make a simple change to it.  I'm not going to rewrite the whole thing.

Regardless, it works just fine.  It'd be nice to be able to turn off whatever is checking this so I can easily save my code.

[Nancy OShea]

Turn off Linting in your Preferences.  But a better approach is to use  <iframes> instead of frames.  DW doesn't support frames.  In fact, I don't know of any code editor that supports them.  Using frames is just bad practice all around.  Fix it or live with the consquences.  Your choice.

[RobCatman]

Yes, I've seen your many arguments on the support forums regarding frames.  I get it.

Again, I'm not going to rewrite the entire code for a simple one line change.  If a project comes up where we decide to convert, it will be addressed at that time.

I turned of Linting earlier and it didn't help.  Hardcoding the filenames fixed it (I did this as a test), but that's not an option.  For now, I'll use a workaround and exit to save and reopen DW.

Thanks for your time.

-=Rob=-

[Jon Fritz]

This issue exists as far back as at least DW CC 2015 build 7698, on Windows 10.

I'm guessing it's considered a feature by Adobe.

[RobCatman · Accepted solution]

Thanks for the polite response, Jon.  I'll use a workaround for now.