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?
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
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.
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
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
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.
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.
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.