Structure 2.0

What’s the goal for releasing an EE 2.0 version of Structure?

I’m sure that Travis wants to get an EE 2.0 version out the door as soon as possible. It’s rather unfortunate that EllisLab has kept 2.0 under such tight Cone of Silence restrictions for so long, as that looks to have kept the add-on developers in the dark. Can’t develop for a product you know nothing about.

Of course, if the rumors are true, it’s easier to develop for 2.0 than for 1.x – which means the cautious estimates of our add-on vendors may be too conservative.

Developers have had the ExpressionEngine 2.0 beta for the longest, starting clear back in the dev preview. The developers are anything but in the dark, Brendon.

@Travis,

How should one go about integrating user comments on structure pages? Is this possible?

Hello Travis,

I purchased Structure 2 for a client. I’m actually using 2.0.2.

I have one template for all my Structure pages. All my pages work with the template except for my index page.

I’ve used Structure 1 on a few sites before that and never had a problem with the home page (using “/” as the URL).

It seems like the home page wont accept my fields. Other pages do but not the home page.

Here is my Template code:

{exp:weblog:entries  disable="categories|member_data|trackbacks|comments"}
{embed="embeds/head" title="{title}" alt-title="{alt-title}" meta-description="{alt-description}" meta-keywords="{alt-keywords}"}
{/exp:weblog:entries}
<body{exp:classee_body}>
{embed="embeds/header"}
<div id="content">
{exp:weblog:entries disable="categories|member_data|trackbacks|comments"}
{exp:allow_eecode}
<div class="center clearfix">
<div id="primarycontent" class="clearfix">
{if member_group == "1"}<a href="/system/index.php?C=edit&M=edit_entry&weblog_id={weblog_id}&entry_id={entry_id}" title="Edit {title}" class="edit" target="_blank" rel="noopener"> /images/edit.png</a>{/if}
{content}
</div><!-- PRIMARYCONTENT -->
{embed="embeds/secondarycontent"}
</div>
{/exp:allow_eecode}
{/exp:weblog:entries}
</div><!-- CONTENT -->
{embed="embeds/footer"}
{embed="embeds/scripts"}
</body>
</html>

The home page I have here should be showing the content I have in my field “content”… but instead it only shows the tag… http://www.vegasluxurysalesandrentals.com/

All other pages work fine and even call their respective entries… http://www.vegasluxurysalesandrentals.com/about/ http://www.vegasluxurysalesandrentals.com/news/

Is it something I’m doing wrong? Or it’s a bug with the new version? My other sites using Structure 1 work fine with that type of template…

thanks for your help!

Hey Travis,

Great add-on, version 2 is my first time using Structure and I’m very impressed.

One minor suggestion on the navigation tag - it makes more sense to wrap the span within the anchor tag, instead of around it. More browsers support the :hover pseudo class for anchors, and you would need to change both background images on a hover if you are using the sliding doors technique. I changed it within the module manually, but I figured I’d make the recommendation. Or maybe make it an additional parameter?

I’ll also second the request for a tree navigation option, for dropdown menu support.

Thanks for the great work!

I have a question about template caching and Structure. Do they both play well together?

I am just wondering, because I am basically reusing the same template for different entries. Will it cache by page_url?

Any more background info on that?

Thanks!

Greg

Licenses are $65 per site

Travis, any way to make a one time ‘Multi-license’ fee for developers? Maybe 65 for one site, 200 for unlimmited. Since most of your support goes to individuals who will use structure in similar ways on multiple sites, it doesn’t seem to me that you’ll be giving equal support in portportion to developers sites. I’ve just used structure in the last 4 websites this month, and only needed support/forums for 1 of them - the first one. After that I understood it much better. And I imagine its the same for most other developers.

Also, you might find more people willing to use structure (with multi site license) just because they know they don’t have to keep paying for each additional site.

Thoughts?

Maybe 65 for one site, 200 for unlimmited

I’ve just used structure in the last 4 websites this month

So you would have covered your costs in less than a month and have a free license for any future website…!

Based on other costing models (e.g. themeforest $10 per site $300 unlimited), $65 per site and $1,950 for unlimited would be more realistic and fair to both parties.

It’s not just about support, but the hard work that went into development, getting the website and documentation in place, all the v1.x efforts, etc.

I would suggest a model that EE uses, where there’s a discount each time, but the management of that is even more effort and work.

Peter.

I’ve recently stumbled on Structure and have spent this afternoon getting to grips with it for a new project. So far, it seems like it could make a huge different to the way I handle tiers of content and I just wish I’d found it sooner.

The only query I have so far is one that seems like it should be pretty straightforward. My guess is it’s just a lack of familiarity with the module. Anyway, I want to display a list of siblings for an entry (i.e. pages on the same level). If it has none, I don’t want anything to be returned. I don’t want links to parents or to children. I’ve spent a while playing around with {exp:structure:nav_sub} and its various parameters but despite my best efforts it seems to be trying to be too clever.

Can anyone point me in the right direction? Thanks.

Edit: Sod’s law - figured it out as soon as I posted. Phew. 😊

Sorry for the delay, I wasn’t getting forum updates

Support for purchased licenses is provided through support [at] buildwithstructure [dot com]

Sometimes forum updates are not sent and you will get quicker replies through the email above. Thanks!

@pushloop Sorry, I’ll add better requirements to the site

@Joe Sending you a PM

@Batdelfuego I don’t see the issue, sending you a PM

@Steve A nav_full tag for dropdowns has been added as of 2.0.3 and the span will be fixed in 2.0.4 (I agree with that markup).

@gstewart You should be fine - I’ve never had issues. When in doubt try it out!

@Chuck Our fee per license is pretty low and it takes a lot of time to develop and support this. This is generally a cost that should be passed onto the client, just like an EE license. We all have to eat and pay bills!

RE: Release date & Upgrades We’ll have Structure EE2 ready by March 1st. I realize this may be longer than some would like, but it’s a large complex module and will take time to properly convert. That said, we’re adding several new features and planning on making navigation tags much more flexible. This will mean deprecating some old tags and support will be provided for those upgrading that want help to convert a site to using the new tags. This will allow for a more robust and powerful Structure. Those who purchase a 1.6.8 license will be eligible for a free upgrade to the EE2 version. Any concerns or questions can be sent to the email address above.

Navigation Feedback In planning the new tags we’re interested to hear how you use the tags and how they could help you more. Behavior, code, ideas, anything - email your ideas to contact [at] buildwithstructure [dot com]

I just upgraded to structure 2.0 and I can’t find where to change a child-pages weblog. I’m also getting an error message when I try to reorder pages. I’m using ee version: 1.6.8 Build: 20090723.

@rlargett You can post a child page to a new weblog through the publish menu or by clicking the “add page” link next to a parent title. If you have more than one weblog available and managed by Structure it will let you choose which one to post to. Once a page is created, you can’t change the weblog it’s in, you’ll need to delete and re-add through a method above. As far as reordering: are the module and extension files set to permission 755? Do you have at least PHP 5? Do you have the jQuery extension activated?

Once again, Support for purchased licenses is provided through support [at] buildwithstructure [dot com] Sometimes forum updates are not sent and you will get quicker replies through the email above. Thanks!

We’re going to leave this thread open and support is still provided through support [at] buildwithstructure [dot com] and articles for salmon issues will be posted here: http://buildwithstructure.com/knowledge

Thanks everyone!