When updating my menu, which is a Library item, using Dreamweaver CS6, after the initial update sequence the program keeps trying continuously to update related files but will not complete the update. After I cancel the update it initiates the update again and again does not complete the update. The original complete update actually works but the continuous updating cycle make it so I have to close the program and restart to even work on the site.
Has anyone else experienced this?
I am using the Creative Cloud subscription for CS6. I am using the Windows 7 professional platform.
Here is the link: http://2ndlookgraphics.com/THE/index.html
This is a work in progress. The menu that I was experiencing the problem with is the top menu. This project was started in Dreamweaver CS5 and migrated to CS6. I did not experience this issue in CS5.
I'm not able to reproduce your symptoms. Here are my steps:
1. I restart DW (W7-64 but local DW, not Cloud-based)
2. I select my testing site
3. I open the topNav.lbi file from the Library folder of the site
4. I make a change to the navigation HTML and save the file
5. I am prompted as to whether I want to update the files that use this Library item and select Yes
6. DW scans for these files, and performs the update normally
Under any circumstances, DW should never scan RELATED files. I'm curious if that's what's really happening - are you sure?
As luck would have it, after 2 days of consistently having this problem, I open the site, make changes to the library item menu, save, update, view in browser, and everything works fine. I am not sure why it's OK now but was giving me such a problem before. Perhaps it is related to the issue of the Creative Cloud forcing me to constently activate my software or perhaps it was related to something else going on with my computer at the time. It is strange though that the issue existed over a 2 day period with complete shut downs of both the software and the computer bettween tries.
I would like to keep this thread open just in case the issue rears it's ugly head again.
Thank you for checking on this.
This issue reared its ugly head again today. Same issue of prompting to update files using a library item over and over with the only way to stop it is to close the program. This was an entirely different site, one I have been manageing for years using Dreamweaver through several versions. This was also migrated from CS5 to CS6. This does not happen every time I update a library item but when it does it is extremely irritating.
Has no one else experienced this issue?
cathykimball wrote:
This would not help with the many existing websites that I manage.
May I ask why?
cathykimball wrote:
I doubt the clients would OK time spent re-doing a site because a Dreamweaver function that has always worked great starts acting wacky with new and improved version.
There's not much involved in switching from a Library item to an SSI.
Once the SSI is setup, it's a single identical line of code per Library item in each page. Can be done with a sitewide Find & Replace.
same issue. and it doesn't seem to matter what kind of library/include/language, it is slogs away after every line change or save. horrible. PHP, JavaScript, HTML, ASP, doesn't matter. everything stops while DW scans for whatever
...almost unusable on larger projects because of the time it takes to scan everything. i have a sinlge page test with one inlcude: 18sec scan everytime i change something. doesn't even wait for the F5 update keypress. have gone back to DW5 until a patch fix comes out. ![]()
WR!
Has anyone addressed this issue. It is making Dreamweaver almost impossible to use. windows pop up all over my screen and the only way to get out of it is to force close the program.
It looks like I will have to go back to Dreamweaver CS5 also until such time this obnoxious bug has been exterminated. I just hope CS5 wil work with the sites that I have started in CS6.
Please anyone here who is associated with Adobe. Give this some attention!
Adobe engineers don't lurk in these user-to-user forums. Use the link below to file an official bug report.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Nancy O.
Same issue here:
Steps to reproduce bug:
1. Save a library item that is referenced in a simple html file
2. When saving the template it correctly asks me if I want to update the above HTML file. When I click update it immediately comes up with a second update box without saving the library item again. It is instant.
3. Above HTML is never actually updated.
Expected results: It should only me once per save to update files that the library items are referenced in. CS5.5 did not have this problem.
The only solution I found was to remove the library item from the HTML template and re-add. That fixes it which definatley leads me to believe it is a bug in the CS6 library.
I certainly wish we could get some attention to this issue. It does not happen every time for me but when it does it means a complete shut down of Dreamweaver. Often I have to shut it down via the Windows task manger since the continous popup windows makes normal shut down impossible.
I did submit the issue to https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
but did not hear back so I imagine it was ignored. It would be good is everyone who is experiencing the issue would report it. perhaps they would pay attention then, I do not think it is asking too much for an included feature to work as expected and no, I do not think it should be expected that users find a work-around.
Well I submitted a bug report, maybe you can do the same and reference this thread? The more reports, the more likely they'll look into it further.
Here is the bug report url:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Hello,
I had this problem even when Dreamweaver was owned by Macromedia. That is like 12 yrs ago. I needed to use Dreamweaver again. Now CS6. Can't believe it is still here.
Today I had this problem and I MAY HAVE SOME HINT why it is like this. I was editing the Lib item, and basically adding and removing HTML , div tags. I think it was caused by UNEVEN tags, which resulted in Dreamweaver engine not able to find the library items on the page. Perhaps it may seem lame, but the ideal option this case, would be for DMX to use string parsing and not any DOM parsing ( making some wild guess) - apologies I am no where close. Cheers
North America
Europe, Middle East and Africa
Asia Pacific