[Pro] Problem moving FWP website?

I just tried moving an updated FWP website from my development server to my client’s live server and everything transferred okay, save the CSS menus, which ended up looking like text listings, except for the Perch enabled pages.

Unfortunately, I had to take the update down because I didn’t want to inconvenience my client. I’ve never had that happen before. What do I need to check?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Okay, I placed the updated website on another domain I own so you can see what’s happening. The Perch database has been disabled for safety’s sake. View any of the pages that are NOT Perch enabled and the CSS menu fails. http://gorcb.com/about.html

But the same code on my development server works fine:
http://wmp.idealynx.com/about.html

Any ideas on why this is happening?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Okay, I think I figured it out. The #fwNav1 code is missing from some of the LIVE pages, but I don’t know why. Simply dragging and dropping files shouldn’t do that. This is very weird.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

The #fwNav1 code was commented out. I just corrected it on one of the LIVE pages, but I’m still perplexed as to why that is happening.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

And why the development server copy is working, when it shouldn’t be.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

You’ve fixed this already, I think. It looks fine here.

Walter

On Mar 23, 2013, at 11:49 AM, RavenManiac wrote:

Okay, I placed the updated website on another domain I own so you can see what’s happening. The Perch database has been disabled for safety’s sake. View any of the pages that are NOT Perch enabled and the CSS menu fails. http://gorcb.com/about.html

But the same code on my development server works fine:
http://wmp.idealynx.com/about.html

Any ideas on why this is happening?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 23 Mar 2013, 4:12 pm, waltd wrote:

You’ve fixed this already, I think. It looks fine here.

Walter

I did, but I had to manually fix the code using TextWrangler. That shouldn’t happen. For some reason, FWP is inserting comment marks around the CSS menu code it’s generating. Check out this other page that I haven’t fixed:
http://gorcb.com/about/map.html

Then, check out the very same page on my development server, where the comment marks exists, but for whatever reason they’re being ignored:
http://wmp.idealynx.com/about/map.html


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Is this the GD server up to its tricks again?

David


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 23 Mar 2013, 4:38 pm, DeltaDave wrote:

Is this the GD server up to its tricks again?

David

Unfortunately, yes. I really wish I wasn’t under contract with them. Upon further review of the code, I noticed this error message:

[an error occurred while processing this directive]

What the heck? I updated the website to HTML 5. I wonder if that’s part of the problem.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It is this that GD server doesn’t like

<!--#fwNav1

The server thinks the code is commented out

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

This is the same problem Justin had: http://www.freewaytalk.net/thread/view/128055

I’m going to try that solution and when my contract with GoDaddy expires they are GONE!


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Try using External Stylesheets - either through an action or in the Doc Setup preferences.

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

when my contract with GoDaddy expires they are GONE!

What sort of Contract did you set up with them?

I do use them for Domain Name Management but wouldn’t touch them for hosting so have never had to consider their “contracts”

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I think it’s like a 2-year hosted domain contract.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Check you haven’t a comment that looks like

<!--# Some Comment-->

before this include, if you have then change it to

<!-- Some Comment -->

See if that fixes the problem.

HTH

On Mar 23, 2013, at 5:42 PM, RavenManiac wrote:

On 23 Mar 2013, 4:38 pm, DeltaDave wrote:

Is this the GD server up to its tricks again?

David

Unfortunately, yes. I really wish I wasn’t under contract with them. Upon further review of the code, I noticed this error message:

[an error occurred while processing this directive]

What the heck? I updated the website to HTML 5. I wonder if that’s part of the problem.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I’m inserting a comment in the HMTL Markup , but nothing with a # symbol. Here’s the only code I’m inserting:


<!-- Begin Menu drop shadow code -->
<style type="text/css">
.sub {
-webkit-box-shadow: #000000 3px 3px 5px;
-moz-box-shadow: #000000 3px 3px 5px;
box-shadow: #000000 3px 3px 5px;
}
ul.sub, ul.sub li.fwLastChild, ul.sub li.fwLastChild a {
-webkit-border-bottom-right-radius: 5px;
-webkit-border-bottom-left-radius: 5px;
-moz-border-radius-bottomright: 5px;
-moz-border-radius-bottomleft: 5px;
border-bottom-right-radius: 5px;
border-bottom-left-radius: 5px;
}
</style>
<!-- End Menu drop shadow code -->

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I think Apache will think it is a SSI tag, if it where

<!-- #fwNav1

and not

<!--#fwNav1

then I guess it should be OK, if there is whitespace it should not be read as an SSI tag by apache.

On Mar 23, 2013, at 5:48 PM, DeltaDave wrote:

It is this that GD server doesn’t like

<!--#fwNav1

The server thinks the code is commented out

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

That doesn’t mean you have to host there. Go ahead and buy/register all the domains you like from them (although I wouldn’t just on general principles) but host anywhere else you like. You only have to bite your tongue and visit their “control” panel once in a great while – to point your domains at your host of choice.

Walter

On Mar 23, 2013, at 1:04 PM, RavenManiac wrote:

I think it’s like a 2-year hosted domain contract.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Yes, but I already spent several hundred dollars so I can hosts multiple client sites off of my domain. I need to wait until that expires to move to another provider.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Maybe I am wrong on the whitespace stopping this <!-- # being picked up as a SSI tag by apache:
Found this from a post on this on the internet back from 2008
http://the-stickman.com/2008/03/

HTH

On Mar 23, 2013, at 6:45 PM, Mike B wrote:

I think Apache will think it is a SSI tag, if it where

<!-- #fwNav1

and not

<!--#fwNav1

then I guess it should be OK, if there is whitespace it should not be read as an SSI tag by apache.

On Mar 23, 2013, at 5:48 PM, DeltaDave wrote:

It is this that GD server doesn’t like

<!--#fwNav1

The server thinks the code is commented out

D


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options