surfitin10

Also, for future reference of anyone reading this post, this Codex page tells you how to maintain the WordPress db between development and production servers:

I am also interested in using permalinks for better SEO, but I’m not sure there is a way to do this on my local development environment without using “localhost” explicitly in the permalink URL. Is it possible to use permalinks that can be tested locally and that will still work on a live site? Thanks again!

I understand that using a third party service could solve the newsletter issue; however, what about posts/comments/other data that is developed on the live site? Will this data be preserved if I copy over a new db? If not, I assume it means I will have to install new plugins directly to the live site and test there.

Thank you for that Christine, but if you copy over the database file from the local to the live server, will that not overwrite the data on the live system (i.e. user names / email address from people who have signed up for a newsletter)?

See resolution here: https://www.ads-software.com/support/topic/426706?replies=2

See resolution here: https://www.ads-software.com/support/topic/426706?replies=2

See resolution here: https://www.ads-software.com/support/topic/426706?replies=2

So none of the plugins I tried actually worked in both firefox and safari (shocker!). But here is the code I used to get it to work in both:

<div class="flashmovie">
<object height="500" width="900">
<param name="movie" value="https://www.trendefemme.com/wp-content/themes/dev/intro.swf"></param>
<param name="allowscriptaccess" value="always"></param>
<embed allowscriptaccess="always" height="500" src="https://www.trendefemme.com/wp-content/themes/dev/intro.swf" type="application/x-shockwave-flash" width="900"></embed>
</object>
</div>

Now, define CSS class flashmovie with the same height as the object (in my case, 500px). This will ensure that the video size renders properly in both browsers. It is unfortunate that firefox did not render the video height based on the embed tag alone. Anyway, I finally figured it out and I hope it helps you too if you are reading this, thanks!

Thanks. I had to add CSS for the object class that is added by the plugin when the flash is loaded. Apparently the default values were causing the extra whitespace (i.e. height had to be specified). It is now working well in Safari.

Regarding the Firefox embed parameters, I didn’t see anything directly relative in the plugin options. Did you mean to add a custom tag (fvars in the plugin)? Or is there a way to make the plugin use certain embed tags for Firefox only?

Hello, thank you for your assistance. I install the Kimili flash plugin as directed. I also created a homepage template so that I could use Kimili with the homepage. The flash now appears the same as before in Safari. In Firefox, it doesn’t appear at all. However, there are not any validation issues with the flash portion of the homepage now. Do you know why the flash isn’t displaying in Firefox at all? Is there any way to reduce the whitespace added on the top and bottom of the flash? Here’s the site. Thanks again!

Here is the site where you can see the flash and source:

My Site

Thank you for your help with the flash code! My video is now loading and playing, but it displays with extra white space on the top and bottom of the video in Safari and the video size is much smaller in Firefox. I’m not sure if I need additional parameters in the flash code itself to account for these display issues. I have worked with the CSS for the past hour and have not found a way to fix these issues. Do you have any idea what might be wrong?

Thanks again!

Thanks to both of you!

So I can probably use the postID, but I need to clean up the db first as it has a ton of sample posts/comments that I want to remove and not take to the live site. This data was added simply for development testing. Are you aware of a fast way to remove data like comments/posts without removing theme/wp settings from the db?

Otherwise, the body_class function might work. So basically, I would call this php in my custom contact page for example:

<?php body_class( $custom_contact ); ?>

Then that updates the body tag to:

<body class="custom_content">

From there, I can create additional CSS for the custom_content class that will only be applied to that page. Essentially, this would allow me to create any number of custom classes for each page dynamically. Please correct me if I misunderstood.

Yes that’s true; however, the body tag is included in my header. I could create 2 headers and put the body tag into page.php perhaps.

I’m not sure about how the post ID to title mapping works on the backend. When I move wordpress to a new server (i.e. load my dev work to a production web host), will all of the post IDs be exactly the same in the new installation? I intended this question to be more of a general ‘how would you do this’ inquiry as I am really unfamiliar with what to expect when I move my dev work to a live server.