Opening xml files takes 90+ seconds!

Forum|Forum|8 years ago
August 23, 2017
1 reply
427 views

I'm trying to use Dreamweaver 2017 more, but it takes over 90 seconds to load an xml file. That's a MAJOR production issue for someone who works with thousands of these files!

If I fall back to 2015, the files open instantly!

Each file does have an external schemaLocation, in case that has something to do with it. I'm on a MacBook Pro running El Capitan.

Is there anything I can try to get these to load faster?

Thanks,

Rob

file xml

This topic has been closed for replies.

Correct answer Jon Fritz

There are a few things that can cause DW to slow down like that...

1. Code Errors, run the validator at http://validator.w3.org/nu to make sure you don't have any structural defects in your html. Little things like missing alt attributes or obsolete width attributes won't be an issue, but missing starting/ending tags can cause the newer version of DW to throw a fit

2. Protocol relative links (starting with // rather than http or https) to fonts or scripts in the head of a page can cause issues. Turn them into http and see if that changes anything.

3. Externally referenced scripts in general. Sometime, for reasons I've never been able to figure out, DW will just "not like" a script on a remote server. You can try commenting out all scripts with html comment tags and see if the pages open right. If they do, un-comment one at a time until you find the culprit. Make a copy of that file locally and link to it during development. Change the link to the remote file as a last step before uploading

Jon Fritz

Correct answer

Community Expert

There are a few things that can cause DW to slow down like that...

1. Code Errors, run the validator at http://validator.w3.org/nu to make sure you don't have any structural defects in your html. Little things like missing alt attributes or obsolete width attributes won't be an issue, but missing starting/ending tags can cause the newer version of DW to throw a fit

2. Protocol relative links (starting with // rather than http or https) to fonts or scripts in the head of a page can cause issues. Turn them into http and see if that changes anything.

3. Externally referenced scripts in general. Sometime, for reasons I've never been able to figure out, DW will just "not like" a script on a remote server. You can try commenting out all scripts with html comment tags and see if the pages open right. If they do, un-comment one at a time until you find the culprit. Make a copy of that file locally and link to it during development. Change the link to the remote file as a last step before uploading

R

rob_howardAuthor

Participant

Thanks, Jon! Unfortunately, external scripts are a must with what I do and valid markup is vital.

It's funny, cuz I came back here while waiting for an HTML file to load, which had an API URL, that I'm noticing is pointing to localhost:3000. It will often point to another production server.

Sounds like the external references are the culprit! I just created two basic files (xml & html) with no external reference and they both loaded instantly.

I'm way too busy to wait for files to load, so until DW 2017 can handle these like DW 2015, I'm stuck using Dreamweaver 2015 to remain productive.

Jon Fritz

Community Expert

I haven't switched over to CC2017 full time either, but CC2017.5 does seem better than the prior 2017 releases on this kind of issue. Make sure you've updated it all the way (check under Help > About Dreamweaver).

I don't know if I'd call it "stuck using CC2015", for me, CC2015 is a much more stable product and will likely stay on my machine for a few more years. I don't use GIT and wasn't all that impressed with the implementation of Brackets for the Code View interface, so there's not much in it that would convince me to deal with the "unintentional features" of CC2017.

I hold out hope though that they'll release a patch to clear up the issues I have with it. They've already released something like 4 patches for CC2017, so they're trying anyway.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded