Testing and fine-tuning
Video: Testing and fine-tuningOnce you're live site is up and running, there is still a little bit to go. It's pretty much critical that you do your own testing and especially with the WordPress based site engage your client in the testing process as well. So I like to think of it as divided into two main areas, your own testing and then client-based testing. Your own testing should initially address the public-facing site. You want to make sure that all of your output is cross-browser, cross-platform, and especially today, cross-device.
- Working with web fonts
- Styling a header
- Adding header functions
- Setting up content columns
- Changing the main content
- Managing the content code
- Customizing the sidebar
- Styling search
- Working with search text
- Integrating the footer
- Next steps
Viewers: in countries Watching now:
In this course, author Joseph Lowery shows how to combine the utility of WordPress and the power of Adobe Dreamweaver to transition existing websites to the WordPress platform. The course demonstrates how to create new blog posts and pages, customize WordPress themes, and extend WordPress editable pages from within Dreamweaver. It also covers how to add Spry elements, add and customize plugins, and enhance WordPress-stored content with Dreamweaver's dynamic pages. Plus, a chapter on responsive design shows how you can adapt your layouts for tablets and mobile devices.
- Using the Dynamically-Related Files feature in Dreamweaver to design WordPress pages
- Applying WordPress themes
- Customizing themes
- Adding Spry widgets
- Adding WordPress dynamic data
- Populating the WordPress database
- Publishing a WordPress site
Testing and fine-tuning
Once you're live site is up and running, there is still a little bit to go. It's pretty much critical that you do your own testing and especially with the WordPress based site engage your client in the testing process as well. So I like to think of it as divided into two main areas, your own testing and then client-based testing. Your own testing should initially address the public-facing site. You want to make sure that all of your output is cross-browser, cross-platform, and especially today, cross-device.
One key tool that you can use to help ensure that your site is both cross-browser and cross-platform is Adobe BrowserLab, and it's something that you can access right from within Dreamweaver. Now you also want to be sure to test your administrative site, and by that I mean the WordPress Dashboard. For the most part there is been a lot of testing that is already gone into making sure its cross-browser and cross-platform tested well, so you really only need to do a little bit of that.
However, I do recommend that you look at your WordPress site on a variety of platforms and browsers just to ensure that there are no surprises. When it comes to different devices like tablets and phones, that area is under development as they say, and I would especially test hard on any enhancements that you bring to your site as we did earlier in the course, especially in the cross-device category. You want to make sure that any menus that you've added to the Dashboard are easily accessible on both phone, tablet, and desktop.
Another aspect to testing and fine tuning your administrative site is making sure that the client assistance and support is in place. It's one thing if your client is well versed with WordPress blogs and has worked with them for years and all of their company have used them for years, but that's not always the situation. I typically encounter clients who are new to using WordPress and need a lot of support initially. What I do is I create some basic targeted documentation that includes their log-in details meaning the URL that they go to in order to log in, what their usernames and passwords are, and how to find them if they don't have them available to them, and then just the basics of entering posts and editing posts.
I try to set up my WordPress site so most of the hard work--meaning setting up different pages with different themes--is already done. And the client only needs to do a bare minimum, such as enter a post and assign a category. On the client side of things, you want them to also be concerned with testing the public-facing site, as well as the Dashboard administrative site. With the public-facing site, you're going to be dealing with real-world browser, platform, and device testing.
And by that I mean they're going to be using exactly what it is that they work with in their everyday lives. I always try to find out ahead of time what browsers and systems people are used to working with so that I can be sure to pretest those a little more heavily than I would other devices. I want to make sure that when the client sees the work for the first time, that it looks exactly as they're expecting it to. That being said, you never know when they will get word from a trusted advisor who's on an Internet Explorer 6 platform that the site doesn't look quite right.
So you have to be prepared for situations like that, whether you build in the expectation of what browsers, the sites we'll work on in the contract or less formally. One thing that I found very helpful when working with clients and WordPress sites is to initiate a soft launch so that the site is launched but only the client's personnel have access to it. So that they can see not only what it looks like under real-world circumstances as they add more content and expand certain areas of the site, but also so that they can get their content onto the site before it officially launches.
One of the most frustrating things from a web designer's perspective is often getting the content that a client intends to put on the site ahead of time so that you can incorporate that correctly and see what it is they're really working with. Having a soft launch allows them both the experience of getting used to working with the site so you can answer any questions in an upfront manner as well as populating the site. Typically during this process, you'll encounter some minor bug fixes and some adjustments where one feature may not work out exactly as they had thought and so they want something slightly different.
Now that's all fine. But one thing I want to caution you about, this is also an area where feature creep can come in. You want to be aware of the possibility of that but also alert for ways to take that desire to enhance the site into an opportunity for future work. Now there is a tremendous amount of gratification in seeing a client make the site their own by adding content and bringing your site design to life. Enjoy your work as it takes off and becomes an important destination on the web. [00:05:15ll.91]
Find answers to the most frequently asked questions about Dreamweaver and WordPress: Core Concepts .
Here are the FAQs that matched your search "" :
- Q: While trying to set up a Dreamweaver site, an error occurs that says Dreamweaver cannot resolve the dynamic files because the site definition is incorrect. What is causing this? This is using WAMP on a Windows 7 computer.
- A: When setting up the site in Dreamweaver and creating a local testing server, make sure to point it to the folder in c:/wamp/www/ that is being used for the site. If using the same naming convention as shown in the videos, the server folder should be pointing to C:\wamp\www\explore_ca\ and the Web URL field should read http://localhost/explore_ca/, like the picture here:
- Q: How do I set the password for WAMP Server 2?
- A: The WAMP server does not include a password for MySQL when first installed. You’ll need to add a password by modifying a configuration text file and set up a password in the MySQL server.
Setting a password on the MySQL server:
- From the Start menu, enter CMD to open the command line interface.
- Switch to the bin directory of your MySQL folder, installed by WAMP. For version 5.1.36 of MySQL, for example, enter cd c:\wamp\bin\mysql\mysql5.1.36\bin
Navigate within the WAMP folder installed on your system to find the proper path.
- Enter the following: mysql -u root
- The command line for MySQL will open with a mysql prompt like this: mysql>
- Enter the following:
SET PASSWORD for 'root'@'localhost' = PASSWORD('yourPassword');
- replace 'yourPassword' with the password you want to use.
- Close the CMD window.
After you change the MySQL password you will have to edit the config.inc.php file. Here's how:
- In Windows Explorer, navigate to C:\wamp\apps\phpmyadmin220.127.116.11 (version number may vary).
- Open the file config.inc.php in Dreamweaver or another text editor.
- Locate the following line:
$cfg['Servers'][$i]['password'] = '';
- Enter your password between the quotes; make sure the password is the same as the one you set in the MySQL server.
- Save the file.
- From the system tray icon for WAMP, choose Restart All Services.
- To test, choose phpMyAdmin from the WAMP system tray icon.
- Q: After creating a template following the instructions in the Chapter 5 video “Creating a page template in Dreamweaver,” I am unable to select the template. In the video, the instructor’s page shows a heading of Template, with a dropdown menu, but my version shows only a dropdown labeled “Attributes,” and the newly created template does not appear. What is causing this issue?
- A: This seems to be a bug in WordPress that occurs occasionally. Although a cause has yet to be determined, a possible workaround to get the Template option to appear is switch themes. Switching to the default theme and then back again to Explore_California should reveal the Template option.
- Q: While following along with the instructions in the "Setting up a MySQL password for Windows," I encountered this error: MySQL said: "#1045 – Access denied for user ‘root’@’localhost’ (using password: NO)" What is causing this error?
- A: This error occurs when trying to enter the MySQL monitor with a password for a user who has not set a password yet. In that case, removing the “-u root” part should resolve the problem.
- Q: While following along to the chapter 2 movie "Using dynamically related files," I get an error message that reads: "Dynamically-related files could not be resolved because the site definition is not correct for this server." What is causing this error?
- A: This is a known issue with Dreamweaver, and relates to the permalink settings in the WordPress installation. If the permalink setting is set to something other than the default, like “Month & Name,” for example, Dreamweaver is unable to resolve the dynamic files, and the described error will occur. Changing the permalink setting back to Default will clear the error.
- Q: I am bit confused as to my need to use MAMP with a WordPress site in Dreamweaver. If I am going to use a separate commercial hosting site as my server, do I still need to use MAMP in my WordPress site?
- A: MAMP is installed to provide an easy-to-use development server capable of handling MySQL and PHP on your local computer. It's also possible to set up MySQL and PHP servers separately, but it requires many more steps and is not as "user-friendly" as the described process. Your hosting server will have MySQL/PHP enabled on their servers for the remote live setup, but that doesn't have anything to do with developing and testing pages on your own computer.
- Q: I can't find the file named commevents.php in the exercise files. I need it to set up an online database in the last chapter.
- A: This is a file you create yourself when you first connect to a database. Refer to the "Adding WordPress dynamic data to pages" video in Chapter 7. commevents.php should appear in the Connections folder once you establish a connection.
- Q: In "Setting up a MySQL password for Windows", I'm getting the error "#1045 - Access denied for user 'root'@'localhost'" when testing the phpMyAdmin.
If I try and re-do the steps, I get the following error "ERROR 1044 (42000): Access denied for user ''@'localhost' to database mysql'" when I try to change the password.
- A: This seems to be happening because of the combination of Windows 7 and a
new version of WampServer 2.1. Here's another approach that should work
for the new combination.
Follow these steps instead of the ones using the CMD prompt. (As a bonus, they're much easier!)
- Left-click on the WampServer icon tray.
- Choose phpMyAdmin.
- When the phpMyAdmin page opens in your browser, click the Privileges tab found after the Engines tab.
- Locate the line in the User table with "root - localhost - No..." (probably the last one).
- Click the Edit icon (the final item in the row).
- Scroll down to the Change Password section.
- Select Password and enter your password twice. (If you're following the exercises, enter root).
- Click Go in the lower-right corner.
- Q: I want to setup the practice files and site on my localhost, as described; however, I already have my current WordPress site (under development) running on my localhost. How do I run two WordPress sites on my localhost?
- A: You can easily do it by setting up another site in Dreamweaver. Just copy the WordPress files to that folder as described and establish a new database via phpMyAdmin. You can set up as many WordPress sites as you need to. The author has upwards of 80 on his system, all for different clients.
- Q: This course was updated on 10/23/2012. What changed?
- A: The course was thoroughly revised and uses the most current versions of both programs. We added chapters on responsive design and creating a custom administration panel in WordPress, new movies about concepts and taxonomies, and extended the Spry chapter to include jQuery, among other changes. New movies are indicated by the NEW tag next to the movie name.
Sorry, there are no matches for your search "" —to search again, type in another word or phrase and click search.