@travise38589766 , FYI this is a reply from AI     I get the frustration when a reply doesn’t feel directly helpful — especially when you’re knee-deep in tabs and debugging. That said, @Nancy OShea was the only one who responded initially, and she’s consistently generous with her time here. Her tip might not have addressed your issue head-on, but it often helps others facing quirks with PHP tabs in Dreamweaver. There’s probably more nuance to this bug than meets the eye, and it might take a few of us pooling notes to trace a pattern. I’m curious — does this only happen after extended sessions? Or after switching between files that share similar filenames or extensions?   I would have worded it differently.   ... View more

Please print the following guide, laminate it and keep it handy for reference.   🧭 Dreamweaver 21.5 Tab Handling Cheat Sheet A survival guide for ex-DW8 users navigating the new terrain :locked: Preventing Accidental New Panels Action Shortcut / Tip Reposition tab without spawning new panel Drag tab horizontally only, keeping cursor aligned with tab row. Release precisely on the tab line. Avoid docking mishaps Hold Ctrl (Windows) or Cmd (Mac) while dragging to prevent auto-docking into new zones. Undo rogue panel creation Drag tab back into main tab row or use Window > Workspace Layout > Reset to restore layout. :rocket: Moving Tabs Across the Tab Bar Goal Shortcut / Tip Jump tab from far right to far left Use the >> dropdown to select the tab, then drag it leftward along the tab line. Close unused tabs quickly Ctrl + W (Windows) or Cmd + W (Mac) to close current tab. Cycle through tabs Ctrl + Tab (Windows) or Cmd + ~ (Mac) to switch between open tabs. 🧰 Workspace Optimization Task Shortcut / Tip Increase tab grab area Go to Edit > Preferences > Fonts and increase UI font size slightly. Save custom layout Window > Workspace Layout > New Workspace to preserve your preferred setup. Reset layout if things go wonky Window > Workspace Layout > Reset <Your Workspace> to restore sanity.   Edit: It looks like this forum does not preserve the emoji's. This is an image of what the Cheat Sheet should look like:     ... View more

Somthing like this?? https://youtu.be/TF2OP509pEI?si=1RBWxIs8JYfEtr6h   ... View more

Ah! Seven years ago, aged 75, I switched from Dreamweaver to Wappler and never looked back. Wappler supports PHP, ASP, and NodeJS and has a slightly different way for the frontend to communicate with the backend. This is done via API's.   This illustrates the function of an API ... View more

There's no sign anyone from Adobe monitors this so I suggest reaching out to their support. You'll see Nancy's replies but she's just a nice person trying to help. She doesn't work for Adobe support. Adobe is done with Dreamweaver so, as painful as it might be, going to back to 21.4 for your users might be the only viable option. I'm building all of my new projects using VS Code now. If you work in code view, it has been a breath of fresh air. By @glenn-p   A very wise decision, one that I have been advocating for the last 10 years. Dreameweaver is dead were it not for the life support machine called Adobe. I do not understand why any serious 'enterprise' would still be using it.   ... View more

I mean buy the entire application code  from Adobe so adobe doesn't own it any longer at all. That way it could be developed again by an interested party. By @haleyt88803336   Dreamweaver began losing its dominance in the web development world during the early to mid-2010s, and its decline became more pronounced by 2020, when Adobe placed it into minimum development status—meaning no new features were planned, only bug fixes and OS compatibility updates. If you're nostalgic for Dreamweaver but want something modern, Wappler is often cited as a spiritual successor—especially for visual development with full-stack capabilities.   ... View more

Chrome DevTools Coverage Tab: Shows unused CSS/JS bytes visually Click on the file name and it will show the unsused parts for the selected page.     ... View more

This is what Copilot has to say on the subject:   The latest version of Adobe Dreamweaver—May 2025 release (version 21.5)—is mostly a maintenance update focused on security and stability rather than new features. Here's a quick rundown: :wrench: What's New in Version 21.5 Upgraded third-party libraries to patch known security vulnerabilities Bug fixes and performance improvements, especially for legacy issues Continued support for core web technologies like HTML5, CSS3, and JavaScript 🧭 General Direction Adobe has placed Dreamweaver in minimal maintenance mode, meaning no major feature development is planned The tool remains stable for designing and managing dynamic websites, but it's not evolving rapidly 🧩 Alternatives Gaining Traction Given the slow pace of updates, many developers are exploring alternatives: Wappler – a low-code editor with strong visual tools and dynamic capabilities VS Code – lightweight, extensible, and free, with live preview extensions Pinegrow, Webflow, and Squarespace – for more visual or template-driven workflows If you're still using Dreamweaver for HTML/CSS-heavy projects, it’s functional—but if you're looking for innovation or modern frameworks, it might be time to explore other options.   ... View more

There are a few places. 1. The border on line 1795 in the main.css file 2. The border-top on line 1812 in the main.css file 3. The border-bottom on line 1821 in the main.css file Commenting out those three settings out removes the lines from your image, but that may also remove them from places you actually want them. By @Jon Fritz   Better still, don't remove them, make them transparent by changing the opacity to 0% as in border: solid 1px rgba(255, 255, 255, 0); ... View more

Use the developer tools in your browser and all will be revealed as in Or better still, used Wappler so that you can be independent of a browser:     ... View more

Hi Paul, It sounds like those two pages may have lost their connection to the template—especially since everything else is still functioning. You might want to open the non-working pages in Code view and check for the `<!-- InstanceBegin template="..." -->` tag at the top. If it’s missing or malformed, Dreamweaver won’t be able to reapply the template, and the “File Deleted” message makes sense in that context.   Another factor could be Dreamweaver itself. Version 21.5 build 15662 on macOS Sequoia has reportedly been unstable for some users, especially around site definitions and template linkage. If the issue persists, it might be worth testing with an earlier version—just to rule out a bug in the current build.   Hope that helps!     ... View more

Somthing like this? <!doctype html> <html> <head> <base href="/"> <meta charset="UTF-8"> <title>Untitled Document</title> <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> <link rel="stylesheet" href="/bootstrap/5/css/bootstrap.min.css" /> <link rel="stylesheet" href="/css/style.css" /> <script src="/dmxAppConnect/dmxBootstrap5Navigation/dmxBootstrap5Navigation.js" defer></script> </head> <body is="dmx-app" id="junk"> <header> <img src="https://picsum.photos/id/29/2600/500.jpg" class="img-fluid position-relative"> <nav class="navbar navbar-expand"> <div class="container position-absolute bottom-0 start-50 translate-middle"> <div class="navbar-nav w-100 justify-content-center"> <a class="btn btn-secondary me-2" href="#">Link 1</a> <a class="btn btn-secondary me-2" href="#">Link 2</a> <a class="btn btn-secondary me-2" href="#">Link 3</a> <a class="btn btn-secondary me-2" href="#">Link 4</a> <a class="btn btn-secondary me-2" href="#">Link 5</a> <a class="btn btn-secondary me-2" href="#">Link 6</a> <a class="btn btn-secondary" href="#">Link 7</a> </div> </div> </nav> </header> <script src="/bootstrap/5/js/bootstrap.bundle.min.js"></script> </body> </html>   ... View more

I created the following without touching a single line of code: <!doctype html> <html> <head> <base href="/"> <meta charset="UTF-8"> <title>Untitled Document</title> <link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.15.4/css/all.css" integrity="sha384-DyZ88mC6Up2uqS4h/KRgHuoeGwBcD4Ng9SiP4dIRy0EXTlnuz47vAwmeGwVChigm" crossorigin="anonymous" /> <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> <link rel="stylesheet" href="/bootstrap/5/css/bootstrap.min.css" /> <link rel="stylesheet" href="/css/style.css" /> </head> <body is="dmx-app" id="junk"> <section> <div class="container"> <div class="row row-cols-2 gy-3 gx-3 row-cols-sm-3 row-cols-lg-5 justify-content-around"> <div class="col"> <a href="international_distributor2.htm#helenadistributor1" class="nav-link">Distributors (A-E)</a> </div> <div class="col"> <a href="international_distributor2.htm#helenadistributor2" class="nav-link">Distributors (F-J)</a> </div> <div class="col"> <a href="international_distributor2.htm#helenadistributor3" class="nav-link">Distributors (K-P)</a> </div> <div class="col"> <a href="international_distributor2.htm#helenadistributor4" class="nav-link">Distributors (Q-S)</a> </div> <div class="col"> <a href="international_distributor2.htm#helenadistributor5" class="nav-link">Distributors (T-Z)</a> </div> </div> </div> </section> <script src="/bootstrap/5/js/bootstrap.bundle.min.js"></script> </body> </html>   ... View more

Why is the update using outdated PHP and Bootstrap versions.   There should be a security warning attached to Dreamweaver.   Using PHP 7 today—especially in a production environment—is not recommended due to serious security concerns. All versions of PHP 7, including 7.4 (the last in the series), reached end of life (EOL) as of November 28, 2022. That means they no longer receive official security updates or bug fixes from the PHP development team. Here are the key risks of continuing with PHP 7: Unpatched vulnerabilities: Any new security flaws discovered in PHP 7 will remain unaddressed, leaving your application exposed to exploits like remote code execution, SQL injection, and cross-site scripting (XSS). Compliance issues: Running unsupported software can violate security standards like PCI-DSS or ISO 27001, which may be critical depending on your industry. Dependency conflicts: Many modern libraries and frameworks are dropping support for PHP 7, which can lead to compatibility issues and stalled development. Increased attack surface: Legacy PHP code often lacks modern safeguards like strict typing, improved error handling, and safer default configurations. If you're stuck with PHP 7 due to legacy systems, some vendors like Zend and TuxCare offer extended support with backported security patches. But ideally, upgrading to PHP 8.2 or later is the safest and most future-proof move.   You can still use Bootstrap 4, but it’s no longer the safest or most future-proof choice. As of January 1, 2023, Bootstrap 4 reached end of life, meaning it no longer receives official updates or security patches from the core team. Here’s what that means for you: Security vulnerabilities: Recently disclosed issues like CVE-2024-6531, a cross-site scripting (XSS) flaw in the carousel component, highlight the risks of using unsupported versions. No official fixes: Any new bugs or vulnerabilities won’t be patched unless you’re using a third-party long-term support provider like HeroDevs. Compliance concerns: If your project needs to meet certain security or privacy standards, using EOL software could raise red flags. Dependency drag: Bootstrap 4 still relies on jQuery, which many modern stacks are moving away from for performance and security reasons. If you’re maintaining a legacy app, Bootstrap 4 might still be fine with proper sanitization and security hardening. But for new projects—or if you’re planning a refresh—Bootstrap 5 or 5.3.6 is the way to go. It drops jQuery, improves accessibility, and has a more modern utility API.   ... View more

It appears that you encounter various challenges when using Dreamweaver.   As of now, Adobe Dreamweaver is not officially end-of-life (EOL). Adobe still lists it as an active product, and there’s no formal announcement about discontinuation. That said, development has slowed significantly, and many in the web dev community consider it outdated—especially with modern alternatives like VS Code, Sublime Text, and WebStorm dominating the scene.   Wappler is arguably the closest contemporary alternative to Dreamweaver, offering significantly more robust and future-oriented framework. It provides a visual interface alongside code control, supports templating, and enables dynamic data binding.   Here are the reasons why Wappler could be a suitable option for your 2,000-page legacy project: Visual and Code Hybrid: Similar to Dreamweaver but updated, allowing visual layout management while providing access to code when needed Templating and Components: Enables the recreation of .dwt-style templates through Wappler’s layout and partial system, which is more adaptable and scalable. Database and API Integration: Offers backend tools that facilitate the modernization the site into a dynamic or CMS-driven application if desired.   Disclosure: I am a Wappler user with a paid subscription. I have no affiliation with the Wappler product beyond my personal use and do not receive any benefits if you choose to subscribe.   ... View more

You are running out of real estate, partly due to the logo:       ... View more

Consistency in development choices isn’t about adhering to popularity alone—it’s about selecting tools that best serve the project’s needs while ensuring maintainability and efficiency. Bootstrap is widely adopted, making it a practical choice for standardized styling and layout. Wappler, on the other hand, provides a structured workflow that aligns with my development approach, particularly in cases where flexibility and efficiency are prioritized.   Vue and Wappler share several similarities, particularly in their component-based approach and reactive data binding. Wappler’s App Connect framework offers a structured workflow that aligns with modern development practices, much like Vue. The key difference is that Wappler provides a visual development environment while still allowing custom coding, making it a practical choice for certain workflows.   The decision to use Wappler was based on workflow efficiency and maintainability, not just familiarity. Every framework has its strengths, and the choice depends on the specific needs of the project. Standardization and ease of collaboration remain key considerations, regardless of the tool used. Every framework has its strengths, and the choice depends on the specific needs of the project. Standardization and ease of collaboration remain key considerations, regardless of the tool used.   The key is making informed decisions based on project requirements rather than rigid absolutes. Professionalism in development is about understanding trade-offs and making educated choices—not dismissing methodologies outright simply because they differ from conventional workflows.     ... View more

Http/2/3 etc wasn't deployed so that developers could include redundant code bloat it was deployed because websites and apps became more complex requiring  more complex code which was integral and used by the website/app. You and many other developers are  abusing a solution which was never intended to be used to mitigate code bloat. By @osgood_   The purpose of HTTP/2 and HTTP/3 is to optimize resource loading and improve web performance, which naturally includes handling larger codebases more efficiently. While they weren’t designed specifically to 'justify' unnecessary code, they do mitigate performance concerns that were more pressing in earlier web development eras.   Regarding the off-topic remark, Vue vs. Wappler, the decision to transition was based on workflow efficiency and maintainability, not just familiarity. Every framework has its strengths, and the choice depends on the specific needs of the project. Standardization and ease of collaboration are key considerations, especially when working on projects that may be maintained by multiple developers over time.   Ultimately, professionalism in development is about making informed choices that balance efficiency, scalability, and maintainability—not adhering to rigid absolutes."*   ... View more

Professionalism in web development isn't just about minimizing code—it’s about making informed decisions that balance efficiency, maintainability, and scalability. Bootstrap, like any tool, has its place when used appropriately. In modern development, concerns about 'bloat' are largely mitigated by optimized delivery methods such as HTTP/2 and caching strategies.   Rather than focusing on rigid absolutes, the goal should be to choose solutions that best serve the project’s needs while ensuring long-term maintainability. If a standardized framework improves collaboration and future-proofing, that’s a valid consideration—just as bespoke solutions have their own merits in specific cases.   Regarding the off-topic remarks, yes, I have recently had to redo a Vue framework-based website. I managed to make significant improvements by translating it into the Wappler front-end framework called App Connect.   ... View more

I've a hundred sandbags loaded in the boot of my car I dont need, the car is very slow, so instead of removing the sand bags I had a more powerful engine fitted By @osgood_   I have a spare wheel in the boot of my car, that has never been used. It does not affect performance because it's relatively small in weight.   Getting back on topic, modern web development negates the effect of so-called bloat, as this example shows:   Furthermore, because my sites deploy NodeJS/Express, the file gets loaded once for the whole website. A small price to pay for a standardised stylesheet that is understood by millions of developers around the globe, making site maintenance a cinch for anyone. This is in stark contrast to your bespoke stylesheets.   And because I am using an HTTP/2 server, the files are simultaneously loaded, thus time is not a factor.   ... View more

There is a Cold Fusion Builder extension for VS Code, but not for DW.  Go figure!     By @Nancy OShea   A telltale sign of things to come? ... View more

I would not advise using a Bootstrap accordion in a predominately non-bootstrap website if that is the idea as you'll only be leveraging about 3% of the javascript, leaving 97% bloat...........gulp!!!!......not to mention the 1000's of lines of redundant css!!!! By @osgood_   There may be bloat in the website, but certainly not caused by the Bootstrap framework:     It is great to see that HTTP/2 is being delpoyed for the site; even better that HTTP/3 is deployed for the Bootstrap framework.   Talking Bootstrap bloat is so much of a previous (read: jQuery) era.   ... View more

The problem lies with the ID of each of the accordion panels. Each of the conecutive ID are #highSchool   Each panel should have a unique ID. You will find highSchool in several places for each panel   ... View more

<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>David Bassett Memorial</title> <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/css/bootstrap.min.css" rel="stylesheet"> </head> <body> <!-- Navigation Bar --> <nav class="navbar navbar-expand-lg navbar-dark bg-dark"> <div class="container"> <a class="navbar-brand" href="https://www.bassett.net">Bassett.net Home</a> </div> </nav> <!-- Main Container --> <div class="container mt-4"> <h1 class="text-center">David Bassett Memorial</h1> <!-- Accordion Section --> <div class="accordion" id="memorialAccordion"> <div class="accordion-item"> <h2 class="accordion-header"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#birthYears"> Birth and Early Years </button> </h2> <div id="birthYears" class="accordion-collapse collapse" data-bs-parent="#memorialAccordion"> <div class="accordion-body"> <p>Born to Charles Harold Bassett and Sarah Gertrude Jones.</p> </div> </div> </div> <div class="accordion-item"> <h2 class="accordion-header"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#highSchool"> High School and Military Years </button> </h2> <div id="highSchool" class="accordion-collapse collapse" data-bs-parent="#memorialAccordion"> <div class="accordion-body"> <p>Stories from his service in Vietnam, including Bob Hope’s visit.</p> </div> </div> </div> <div class="accordion-item"> <h2 class="accordion-header"> <button class="accordion-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#career"> Career and Contributions </button> </h2> <div id="career" class="accordion-collapse collapse" data-bs-parent="#memorialAccordion"> <div class="accordion-body"> <p>His years as a teacher, locksmith, and construction worker.</p> </div> </div> </div> </div> </div> <!-- Bootstrap JS --> <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js"></script> </body> </html> ... View more

May I suggest an alternative approach?   Copy and paste the following code into a new document and view it in your favourite browser: <!DOCTYPE html> <html lang="en"> <head> <base href="/"> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>David Bassett 1945-2025</title> <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-QWTKZyjpPEjISv5WaRU9OFeRpok6YctnYmDr5pNlyT2bRjXh0JMhjY6hW+ALEwIH" crossorigin="anonymous"> </head> <body> <!-- Navbar --> <nav class="navbar navbar-expand-lg navbar-dark bg-dark"> <div class="container"> <a class="navbar-brand" href="http://bassett.net">Home - Bassett.net</a> <button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbarNav"> <span class="navbar-toggler-icon"></span> </button> </div> </nav> <!-- Main Container --> <div class="container mt-4"> <div class="row"> <!-- Sidebar --> <div class="col-md-3"> <div class="card"> <img src="/photos/family/2025-05-02-justDave.jpg" class="card-img-top img-fluid" alt="David Bassett"> <div class="card-body text-center"> <h5 class="card-title">Kathryn & Dave</h5> <p>2008 Trip to Alaska</p> </div> </div> </div> <!-- Content Section --> <div class="col-md-9"> <h1>David Bassett 2 May 1945 - 16 May 2025</h1> <!-- Accordion Section --> <div class="accordion" id="biographyAccordion"> <div class="accordion-item"> <h2 class="accordion-header"> <button class="accordion-button" type="button" data-bs-toggle="collapse" data-bs-target="#birthYears"> Birth and Elementary Years </button> </h2> <div id="birthYears" class="accordion-collapse collapse" data-bs-parent="#biographyAccordion"> <div class="accordion-body"> <p>Born to Charles Harold Bassett and Sarah Gertrude Jones.</p> <p>Coming soon: Various pictures including the Model T he learned to drive on.</p> </div> </div> </div> <div class="accordion-item"> <h2 class="accordion-header"> <button class="accordion-button" type="button" data-bs-toggle="collapse" data-bs-target="#highSchool"> High School and Vietnam </button> </h2> <div id="highSchool" class="accordion-collapse collapse" data-bs-parent="#biographyAccordion"> <div class="accordion-body"> <p>Stories from his time in the service, including Vietnam, Bob Hope’s visit, and more.</p> </div> </div> </div> <div class="accordion-item"> <h2 class="accordion-header"> <button class="accordion-button" type="button" data-bs-toggle="collapse" data-bs-target="#workingYears"> Working Years </button> </h2> <div id="workingYears" class="accordion-collapse collapse" data-bs-parent="#biographyAccordion"> <div class="accordion-body"> <p>Details about his teaching career, construction experience, and locksmith work.</p> </div> </div> </div> </div> </div> </div> </div> <!-- Bootstrap JS --> <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js" integrity="sha384-YvpcrYf0tY3lHB60NNkmXc5s9fDVZLESaAA55NDzOxhy9GkcIdslK1eN7N6jIeHz" crossorigin="anonymous"></script> </body> </html>   How did I get this code? I opened your current page in my Edge browser. Then I opened Copilot (top right corner of the browser) and asked to "give me the HTML code for the whole document using Bootstrap 5.3"   This was the reply: Here's a modernized version of your document using Bootstrap 5.3 for improved responsiveness, accessibility, and styling. It replaces custom JavaScript accordions, outdated inline styles, and manual layout structures with Bootstrap components.   Key Improvements: - Bootstrap grid system (`container`, `row`, `col-*`) for proper responsiveness. - ccordion component for collapsible sections. - Navbar for intuitive site navigation. - Bootstrap card components for structured content. - Image responsiveness (`img-fluid`) for better display on all devices. --- Updated HTML Code Using Bootstrap 5.3 (as shown above)   Additional Enhancements Fully responsive layout using Bootstrap grid. Improved readability with better font sizing and spacing. Bootstrap components replace custom styles and scripts. Accordion system for structured content browsing.   Would you like additional features, such as a footer or contact form? 😊   The result:   Try it for yourself, you'll be surprised!   ... View more

What about updating to VSCode?     ... View more

New features built-in server side type WAMP and XAMP, AI controlled Validators for code and links and scripts. Support for both independent and team development. Automated maintenance of finished web product with the help of validators on both the development side and client side. Also good support for third-party development of plugins and addons desirable. By @Kajrov   Wappler has all of the above plus a proper AI integration that will write all of the tedious coding automatically. Have a look at the following video as an example: https://youtu.be/TF2OP509pEI?si=cVr-RI8KUKmPyZxE     ... View more

I decided to ask Copilot for a comparison. This is the answer: Which One Should You Choose? VSCode: Best for developers who prefer full control over coding. Dreamweaver: Good for designers who want visual editing but need manual Bootstrap 5 integration. Wappler: Ideal for low-code development with modern frameworks.   If you're working with Bootstrap 5 and PHP 8, Wappler might be the easiest choice. But if you prefer coding flexibility, VSCode is a strong contender.   ... View more

There are no real alternatives to DW that does everything DW does, in one place. By @Martini Celltrot     ... View more

You bring a smile to my face. In just few days, I will turn 82 and I can’t help but wish to be 40 years younger. 😉    Spry! How I missed the framework when Adobe discontinued it a decade ago. It gave me a deeper appreciation for JavaScript. Nowadays, I develop my applications using NodeJS, a server-side JavaScript model.    PS. A couple of weeks ago, I created a website for my son using AI. What would have taken me a few months during my Dreamweaver days, took less than a week. This includes a secure admin panel so that he can maintain the properties list himself.   ... View more