• So everything has been running smooth. I have my local host setup with Xamp on the Apache server through MYSQL database on port 80. My wordpress was connected to my Dreamweaver and it was receiving the updates I made on there with no problems before.

    Now all of a sudden I am getting the old “Dynamically related files could not be resolved because the site definition is not correct for this server” message again.

    Everything is correct and has not changed. Local site folder is still C:\xamp\htdocs\, webserver still C:\xamp\htdocs\, and web url still http://localhost/, all connected on local/ network, and in advanced its on php mysql, testing is checked, not remote.

    Nothing has changed but it will not open up my index file now, just gives me the dynamically related files message.

    I have not used Dreamweaver in a couple of days and have done the bulk of my editing in the WordPress admin. The theme I use doesn’t allow for change in the style.php and makes me use the override under within the theme admin for changes to take effect is the main reason.

    When this problem first ocurred I went and replaced all of the WP and theme pages with their original untouched pages with no success. I’m wondering, could the override css/ html code I’ve implemented in the admin area be a reason? I also read somewhere else on the internet that changing the permalinks, which I have done on my static/ post pages, can render this error message as Dreamweaver cannot figure out how to reroute.

    My index page is a static page with new permalinks as are my other pages. I read this on a thread that was a year old, is this still a problem Adobe has not figured a patch too, or is my problem somewhere else? Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Yes, changing permalinks is like moving to a new house without leaving a forwarding address. Just as mail sent to your old address will never get to you at your new home – Dreamweaver will never find any of your pages. This also kills your SEO ranking as Google, et. al. will not know these new permalink pages are really the old pages, renamed.

    If you can’t or don’t want to change the permalinks back, the simple solution is to put redirection statements in your .htaccess file.

    If you’re not a coder or don’t want to edit .htaccess directly, there are many plug-ins that will help you do that safely. Just search for ‘Redirection’ or ‘Redirector’ in the plugins section. One that works well for us is simply named ‘redirection’.

    Thread Starter brainfreeze0

    (@brainfreeze0)

    The sites not even live, its on my remote server. Also, the permalinks were changed in accordance with seo to put my keywords into the extension. At the moment I’ve just been designing my website. When it goes up all of the pages will be correct on permalinks and structure to ensure not to make the mistakes Ive made in the past in doing what you described after it was already live.

    OTT, in a situation like this the redirect would be the appropriate form of action, but it would also be wise to list the old permalinks in your robot.txt and simply delete the pages a few months down the road after Google has stopped crawling and indexing those url’s onto the web.

    Thanks for the help

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Dreamweaver CS5 and WordPress Dynamic Files issue?’ is closed to new replies.