OK< so i didnt want to start with a full blown post hoping that the issue would be a common issue, so here goes:
EE is running on an IIS server :( and has issues when adding weblogs, specifically hit “save/update” and it generates the infamous error
CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers.
Hit “Quick save” and the error posted previous shows.
Before you ask, I have tried all 3 “fixes” except the disable FASTCGI to no effect.
This is a fresh install, a couple of empty template groups but nothing meaningful aka no code.
All I can think of is that prior to installing this extension, whilst it would error on submitting an article EE recorded everything EE orientated before psoting the error, so once adding this extension, EE still records everything but stumbles when recording the extension specific data.
Looks like for this particular install your extension just cant handle the hostile IIS environment (who can blame it).
Hit me up for logins if you want but my limited knowledge says that this install on this server just dont like the code :(
Just an update: Chief has bailed using Structure for this install because of the IIS issues, although we have many sites using Structure on IIS no problem. We weren’t able to get more info and move forward to find a fix. Anyone that has the same, be sure to get in touch if you can recreate the problem. Thanks!
@Cheif No need for sarcasm and ill feelings, Chief, I just try to note what’s going on here for people that follow issues in the forums this wasn’t a jab. We got back to you yesterday and are going as fast as we can not to mention I’m traveling abroad at the moment. I didn’t even get the first forum notification until after it was posted and the official means for support is via email as well. You seem to be having larger EE-related IIS issues anyway if you’re getting errors when adding weblogs and I know you’ve said you’re under a large time crunch, so we understand. Hopefully we can help you in the future. Good luck.
@PhilBrienesse Generally no, as only listing content should expire, which doesn’t use nav_sub. Pages are usually not time sensitive content. Can you give me an example of when this would be useful? If I’m convinced I’ll add it to our (very long) list of future updates. Thanks for your feedback!
Site I am working on currently goes down 1 level from /projects Which would have been fine for a listing. But part of the reason i upgraded them to structure as well as 1.6.8 (at same time) was that they now need projects to go to 2 levels below projects ie /projects/theproject/sub-page For some reason they would like to post some short term projects to auto expire rather than moving them to the category past (projects are categorized past/present/pending). So a very specific example and personally i don’t normally see a reason or much use for it on a regular basis. In this case the client is ok with marking it on their calendar and then switching the entry to closed. So no big deal and I understand if it doesn’t make the long list of future upgrades.
Just want to say what a great extension this is by the way. One of the best things is the documentation. Many EE extensions seem sorely lacking in documentation (even paid ones). I appreciate the great support, once again enjoy your travels.
Is there any way I can set up Structure so that I can have a submenu under a main menu section which has items that link to ahref targets on the main menu section page? For example:
Coaching - Swim - Bike - Run
…and each of those children links to a # on the Coaching page.
Any help on this would be greatly appreciated!
Creating my first EE site and it’s turning out to be a more complex site than I thought it would be. I think Structure will save my sanity, but I have some questions about setting up template groups.
The site I’m setting up will have 3 main sections with a lot of pages and subpages of different types in each section. I’m thinking a logical organization might be to have 3 template groups, with each group having templates for each page type it contains - static, forms, different repeating info pages. The static template would probably be the same in each section, but that doesn’t seem like a big deal to me.
Does that make sense? and more importantly will it work? Would there be a better way to set it up?
Flo
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.