Copy link to clipboard
Copied
I have a php/mysql website running on Win11 xampp localhost server and it displays fine in browsers using http://localhost/sitename
And it loads dynamic content in live mode but still gives the site definition error.
But in design mode dynamic content is not displayed due to "site definition not correct".
If the site definition is incorrect why does it work in everything except design mode?
Does anyone know how to fix this?
Copy link to clipboard
Copied
Is your local site folder pointing to your testing server?
C:\xampp\htdocs\YourSiteName\
Copy link to clipboard
Copied
Yes. C:\VMShared\xampp\htdocs\sitename\
Copy link to clipboard
Copied
What's VMShared? Is that your computer's primary hard drive or a network/cloud drive?
Copy link to clipboard
Copied
VMShared is just a sub-directory that acts as a bridge between C: and a virtual win 7 machine. I had considered that may be an issue at first but the site renders fine in browers using the same server path. Do you think that could be causing the problem with Dreamweaver?
Copy link to clipboard
Copied
Yes. Design view is a hold over from the old Macromedia days. There's a lot it can't do, including cope with exotic set-ups.
You can ignore the warning. Or you can move your local site to the primary drive and see if that cures the issue in Design view. Your choice.
Copy link to clipboard
Copied
Yes. Design view is a hold over from the old Macromedia days. There's a lot it can't do, including cope with exotic set-ups.
By @Nancy OShea
@joe_8368 , I think you are much better off having a second (or third) IDE next to Dreamweaver, to get better solution to your problem.
My advice, try:
Copy link to clipboard
Copied
I moved xampp directly under C: and it's still saying no site defintions. It's also somehow deleting my settings now so I go back and enter everythign again and then says no site definitions and when I go to edit them the server settings are back to default. So somehow it's not retaining the server settings after I click done.
Forutnatly I'm on the 7 day trial so no loss if I can't get it sorted out.
Copy link to clipboard
Copied
If DW's not holding onto your site definition settings, that implies there's a read/write permissions problem.
Try Restoring Preferences.
https://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver.html
Copy link to clipboard
Copied
The reset worked so it's retaining the server settings again, but still giving the same error.
Here's the screenshots:
Copy link to clipboard
Copied
Is Xampp running?
Copy link to clipboard
Copied
Yes, and the site runs correctly via localhost in a browser (or DW live mode).
Copy link to clipboard
Copied
@joe_8368 , I have three questions,
Copy link to clipboard
Copied
1. Apache ver. 2.4.58
2. I moved xampp directly to c:/xampp and that did not change anything
3. No but if it's Windows that's not understanding the path then why does the site run perfectly in browers on localhost?
Copy link to clipboard
Copied
Windows, servers, and browsers handle file paths differently, which can lead to some confusion. Here’s how we’ve addressed these challenges here at our studio, especially when working with local servers on XAMPP and different virtual machines or disks.
We don’t store at all our development files on C:\ . This drive is strictly for Windows and the system. All projects and files are located on virtual disks or machines, resulting in paths like \\SRV-124\folders rather than usually X:\folders.
To make Windows understand correctly these paths, we map our network drives. It's easy and fast. For that, just open a terminal (CMD, PowerShell, or the terminal in VSC) and type:
net use X: "\\SRV-124\folders"
Now, Windows will recognize X:\ as the location for the files located on \\SRV-124\folders. Once you’re done with your work, when ever you need, you can unmap the drive, using :
net use X: /d
C:\ Edit the httpd.conf file of XAMPP located at:
C:\xampp\apache\conf\httpd.conf
You can also edit this file directly by clicking the Edit button next to Apache in the XAMPP Control Panel dashboard.
Add this line at the end of the file:
Include "C:/xampp/alias/*"
This allows you to include custom alias files for each project, making it easier to manage multiple setups without constantly editing httpd.conf.
The term alias is arbitrary, but it is descriptive and meaningful. At our studio, we chose to place this folder at the root of XAMPP, which allows us to maintain multiple separate XAMPP instances, each with its own set of projects.
Create a folder named alias at the root of your XAMPP directory. Inside this folder, you can now add individual .conf files for each project.
Before configuring the alias, ensure you have the project folder ready. For example, for a project named foo:
X:\foo\
\\SRV-124\foo\
The configuration for your alias depends on the version of Apache you’re using. This step is critical because the syntax differs slightly between Apache 2.2 and Apache 2.4+.
You first need to create a file with the same name as your project folder (e.g., foo.conf) and place it inside the alias folder. Depending on your Apache version, this file will need to be filled out differently:
Alias /foo/ "X:/foo/"
<Directory "X:/foo">
Options Indexes FollowSymLinks MultiViews ExecCGI
AllowOverride All
Order allow,deny
Allow from all
</Directory>
Alias /foo/ "X:/foo/"
<Directory "X:/foo">
Options Indexes FollowSymLinks MultiViews ExecCGI
AllowOverride All
Require all granted
</Directory>
Note that <Directory "\\SRV-124\folders"> can also be used, but then it's up to your prefs and habits.
Once the alias is created and the configuration file is in place, restart XAMPP. This allows Apache to recognize the alias.
You can now access your project by visiting the following URL in your browser:
http://localhost/foo/
This setup ensures that your project files are accessible in Dreamweaver, VSC, and any browser. At our studio, this method has worked flawlessly, with all related files, resources, and previews functioning as expected in within DW.
Could you please test it and let us know, thanks.
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more