Not necessarily. As soon as I upload a fresh copy I’ll test your theory.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 23 Mar 2013, 6:08 pm, Mike B wrote:
Maybe I am wrong on the whitespace stopping this
Nope, you were right. I just added your modification to this page and now it works fine: http://gorcb.com/about/crane.html
But, I still can’t understand why the CSS menu works on the following Perch enabled pages, but none of the standard pages:
http://gorcb.com/about/news.php
http://gorcb.com/photo-gallery.php
http://gorcb.com/contact/location.php
http://gorcb.com/extras/floral-regulations.php
There is something more to this mystery. What’s different about the Perch pages? And even with the CMS turned off the CSS menu still works.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
.php pages!
if the page was .shtml it would probably work also… at a guess.
HTH
On Mar 23, 2013, at 7:18 PM, RavenManiac wrote:
On 23 Mar 2013, 6:08 pm, Mike B wrote:
Maybe I am wrong on the whitespace stopping this
Nope, you were right. I just added your modification to this page and now it works fine: http://gorcb.com/about/crane.html
But, I still can’t understand why the CSS menu works on the following Perch enabled pages, but none of the standard pages:
Custom Home Builder Richmond VA | River City Builders
http://gorcb.com/about/news.php
http://gorcb.com/photo-gallery.php
http://gorcb.com/contact/location.php
http://gorcb.com/extras/floral-regulations.php
There is something more to this mystery. What’s different about the Perch pages? And even with the CMS turned off the CSS menu still works.
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, 6:27 pm, Mike B wrote:
.php pages!
if the page was .shtml it would probably work also… at a guess.
HTH
Wow! You’re good Mike. I just changed this page from html to shtml: http://gorcb.com/about/crane.shtml and your theory works!
So what happens if I change all of my FWP pages to shtml?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
They end in a .php file extension, so Apache isn’t scanning them at all, let alone scanning them for SSI includes.
Walter
On Mar 23, 2013, at 2:18 PM, RavenManiac wrote:
On 23 Mar 2013, 6:08 pm, Mike B wrote:
Maybe I am wrong on the whitespace stopping this
Nope, you were right. I just added your modification to this page and now it works fine: http://gorcb.com/about/crane.html
There is something more to this mystery. What’s different about the Perch pages? And even with the CMS turned off the CSS menu still works.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Well not really, Apache servers are normally set up to allow .shtml page to parse SSI includes.
If you change all your pages to .shtml, basically apache will look through those pages for SSI tags, but why do that if they don’t are not using SSI tags? If you don’t need a page with a .shtml extension then don’t use it, the server will just use up energy parsing files that it doesn’t need to.
It seems the reason the error was shown was because Apache picked up on what it thought was an SSI tag and then seen it was not correct, so it put out an error: [an error occurred while processing this directive]
The whitespace was obviously enough to break the ‘assumed SSI’ tag out of SSI format and so stop that from happening on the page with the change you made, although it might be best for these to be on two seperate lines… just to be safe.
<!--
#fwMenu1 {...............}
~~~~'
On Mar 23, 2013, at 7:36 PM, RavenManiac wrote:
>> On 23 Mar 2013, 6:27 pm, Mike B wrote:
>>
>> .php pages!
>>
>> if the page was .shtml it would probably work also... at a guess.
>>
>> HTH
>
> Wow! You're good Mike. I just changed this page from html to shtml: http://gorcb.com/about/crane.shtml and your theory works!
>
> So what happens if I change all of my FWP pages to shtml?
>
>
>
> _______________________________________________
> 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/optionsRats. I jumped too soon and changed all of my pages to shtml. I’ll change them back to html. It really sucks that I have to go in and manually add a space to every html page. I hope Softpress fixes this issue.
IS there anything I can add to the HMTL Markup that would also break the assumed SSI tag?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The error here is in GoDaddy’s Apache configuration, which is set to search ALL pages for SSI directives, not just those with an .shtml extension, as the default Apache configuration would have it. This is yet another example of their weirdness. It still doesn’t excuse the CSS Menus Action from writing more correct code, but it does explain why the site works correctly on a normally (correctly) configured server, and fails on GoDaddy.
Walter
On Mar 23, 2013, at 3:13 PM, Mike B wrote:
Well not really, Apache servers are normally set up to allow .shtml page to parse SSI includes.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Sorry, ‘not correct’ meaning it was an .html page which was using what Apache thought to be an SSI tag when .html extensions where not set up on the server to use SSI inlcudes, which they generally wouldn’t be.
On Mar 23, 2013, at 8:13 PM, Mike B wrote:
It seems the reason the error was shown was because Apache picked up on what it thought was an SSI tag and then seen it was not correct, so it put out an error: [an error occurred while processing this directive]
On Mar 23, 2013, at 7:36 PM, RavenManiac wrote:
On 23 Mar 2013, 6:27 pm, Mike B wrote:
.php pages!
if the page was .shtml it would probably work also… at a guess.
HTH
Wow! You’re good Mike. I just changed this page from html to shtml: http://gorcb.com/about/crane.shtml and your theory works!
So what happens if I change all of my FWP pages to shtml?
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
So, what’s the easiest way to fix this issue until Softpress can address the problem, if they are willing to do so?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Apply the Action I just wrote to each .html page that you also use the CSS Menus Action on, and you’re done.
Walter
On Mar 23, 2013, at 3:24 PM, RavenManiac wrote:
So, what’s the easiest way to fix this issue until Softpress can address the problem, if they are willing to do so?
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
From what I understand this is a setting users control from their GoDaddy account:
WARNING: Changing the default behavior of file extensions in your hosting account can have unexpected results, possibly disabling installed software on your hosting account. This is an advanced feature and should be used by experienced users only.
Modify File Extension Behavior Using the File Extension Manager
• Log in to your Account Manager.
• Click Web Hosting.
• Next to the hosting account you want to use, click Launch.
• In the Settings section of the Control Panel in your hosting account, click the File Extension Manager icon.
• Select the extension you want to modify and click the Edit (Pencil) icon.
• Choose what application you want this extension to run under. When you're finished, click OK.
Calls to that extension will now be rendered in the application you selected.
The above is taken from GoDaddy.
HTH
On Mar 23, 2013, at 8:24 PM, Walter Lee Davis wrote:
The error here is in GoDaddy’s Apache configuration, which is set to search ALL pages for SSI directives, not just those with an .shtml extension, as the default Apache configuration would have it. This is yet another example of their weirdness. It still doesn’t excuse the CSS Menus Action from writing more correct code, but it does explain why the site works correctly on a normally (correctly) configured server, and fails on GoDaddy.
Walter
On Mar 23, 2013, at 3:13 PM, Mike B wrote:
Well not really, Apache servers are normally set up to allow .shtml page to parse SSI includes.
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, 7:40 pm, Mike B wrote:
From what I understand this is a setting users control from their GoDaddy account:
I just checked and there is nothing in that control panel to enable of disable SSI checking.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
It seems GoDaddy have SSI set up to parse .html files by default, but I think looking at this the problem is that ‘fwMenu’ is not a SSI directive and that is why the error was returned, whereas if the following was used on a GoDaddy .html page:
the date would be returned because it is correctly formatted for SSI and a proper SSI directive.
But if the user does not want .html pages to be parsed on their GoDaddy account then using their account manager to set 'html page not to be parsed as SSI would be an option.
I don’t have a GoDaddy account so I am just picking the GoDaddy account mangager stuff from serches, someone with an account would need to check this.
On Mar 23, 2013, at 8:24 PM, Mike B wrote:
Sorry, ‘not correct’ meaning it was an .html page which was using what Apache thought to be an SSI tag when .html extensions where not set up on the server to use SSI inlcudes, which they generally wouldn’t be.
On Mar 23, 2013, at 8:13 PM, Mike B wrote:
It seems the reason the error was shown was because Apache picked up on what it thought was an SSI tag and then seen it was not correct, so it put out an error: [an error occurred while processing this directive]
On Mar 23, 2013, at 7:36 PM, RavenManiac wrote:
On 23 Mar 2013, 6:27 pm, Mike B wrote:
.php pages!
if the page was .shtml it would probably work also… at a guess.
HTH
Wow! You’re good Mike. I just changed this page from html to shtml: http://gorcb.com/about/crane.shtml and your theory works!
So what happens if I change all of my FWP pages to shtml?
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
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
http://support.godaddy.com/godaddy/issues-with-server-side-includes-and-htaccess-file/
On Mar 23, 2013, at 8:49 PM, RavenManiac wrote:
On 23 Mar 2013, 7:40 pm, Mike B wrote:
From what I understand this is a setting users control from their GoDaddy account:
I just checked and there is nothing in that control panel to enable of disable SSI checking.
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
Yep, I posted in the GD forum and they sent me that link as well.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
BTW, I checked my GoDaddy root folder and I don’t have an .htaccess file. 
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
You will need to have your ftp client to show files starting with a . to see those files.
HTH
On Mar 23, 2013, at 9:11 PM, RavenManiac wrote:
BTW, I checked my GoDaddy root folder and I don’t have an .htaccess file.
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
From what I have found on GD search you probably need to add this yourself, I would make sure your ftp client is set to make .files visible before you try creating one so you do not overwrite anything that might otherwise be there.
On Mar 23, 2013, at 9:22 PM, Mike B wrote:
You will need to have your ftp client to show files starting with a . to see those files.
HTH
On Mar 23, 2013, at 9:11 PM, RavenManiac wrote:
BTW, I checked my GoDaddy root folder and I don’t have an .htaccess file.
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
On 23 Mar 2013, 8:28 pm, Mike B wrote:
From what I have found on GD search you probably need to add this yourself, I would make sure your ftp client is set to make .files visible before you try creating one so you do not overwrite anything that might otherwise be there.
Can I use an app like Funter to show the hidden files you’re referring to? Funter - Show Hidden Files on Mac | Free Download
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options