Editing a Concrete5 website inside of Dreamweaver
Permalink
Hi all, I don't know if anyone will be able to help me or point me in the right direction. I want to work on a Concrete5 website but do so inside of Dreamweaver. I've gotten to the point where I can see the website inside of Dreamweaver, but can't edit any of the content inside.
I'm on a Mac using Mamp, but can be on the Windows portion of my Mac and use Xampp or Wamp if that's where someone's area of experience is in. Please let me know if you need any other information to make things clearer. Any help and time of your's would be appreciated!
I'm on a Mac using Mamp, but can be on the Windows portion of my Mac and use Xampp or Wamp if that's where someone's area of experience is in. Please let me know if you need any other information to make things clearer. Any help and time of your's would be appreciated!
The main problem I see is:
Where I should instead be seeing the actual code for the page instead. I've tried looking into how to respond to that, but results on Google have come up pretty dry. I'm seeing the same message on Coda (I know I'm probably missing something very critical, so I apologize in advance for that!)
<?php require('concrete/dispatcher.php');
Where I should instead be seeing the actual code for the page instead. I've tried looking into how to respond to that, but results on Google have come up pretty dry. I'm seeing the same message on Coda (I know I'm probably missing something very critical, so I apologize in advance for that!)
I'm sort of getting the impression from your post that you're not quite understanding what kind of website system concrete5 is.
Concrete5, being a content management, is dynamic - meaning that it generates the output of your website on the fly, fetching content from the database, working out the blocks, content. The pages themselves are also represented in the database.
This is in contrast to a static website, where you've just got a bunch of html files sitting there, a file per page of your site. There's no processing or database. With these kinds of sites you can just open up the html files (i.e. with Dreamweaver), save them and your change is made.
So if you open up a concrete5 site in Dreamweaver, all you are really going to to see is all the files that _run_ the concrete5 system. You aren't going to find an about.html file for your About page for example.
To make content changes to a concrete5 site, you need to log into it. Generally you can get to the login via http://yoursite.com/index.php/login.... Then you use the using controls to make changes, create new pages, etc.
The main reason you might open your site's files in an editor is when you are making a theme. This is where you'd creating the templates and css for a theme, which describes how your site will look and be structured. Again though, the pages and content aren't going to be placed this way, that's done via concrete5's editing interface.
Concrete5, being a content management, is dynamic - meaning that it generates the output of your website on the fly, fetching content from the database, working out the blocks, content. The pages themselves are also represented in the database.
This is in contrast to a static website, where you've just got a bunch of html files sitting there, a file per page of your site. There's no processing or database. With these kinds of sites you can just open up the html files (i.e. with Dreamweaver), save them and your change is made.
So if you open up a concrete5 site in Dreamweaver, all you are really going to to see is all the files that _run_ the concrete5 system. You aren't going to find an about.html file for your About page for example.
To make content changes to a concrete5 site, you need to log into it. Generally you can get to the login via http://yoursite.com/index.php/login.... Then you use the using controls to make changes, create new pages, etc.
The main reason you might open your site's files in an editor is when you are making a theme. This is where you'd creating the templates and css for a theme, which describes how your site will look and be structured. Again though, the pages and content aren't going to be placed this way, that's done via concrete5's editing interface.
Okay, that's what I was started to expect, because a similar thing ended up happening with a Joomla template. That makes sense, so thank you for clarifying and going so into the specifics. I really appreciate it.
Or, you could try using Coda2 seeing as you're running a Mac.http://panic.com/coda/