11

Note: The Title Master add-on should take care of all of this, but if you can't use that for whatever reason, here is the procedure for the hack: Update 10/10/14: Title Master appears to be abandonware at this point. This works as of EE 2.9 Always back up your files and database before hacking the core! Native EE Titles & URL Titles /system/...


5

Your question is not very specific, so we can't give you specific answers... however EE can handle all of this stuff, but it does take some planning. Here are a few comments in no particular order that may help... Firstly I'd recommend ditching Structure, as you'll be fighting it at every step for control of your URLs and you could also find that it hinders ...


5

To make this work, in the entry for Home under the structure tab, set the Structure Page URL to "/"


4

I found that the new Parser logic doesn't account for page_url in their $this->_urls block. Adding the following after line 423 of Simple_variable.php is the fix: elseif ($key == "page_url") { $tagdata = str_replace(LD.$key.RD, $data['page_url'], $tagdata); }


4

Your channels should not match your nav, they should match your page types. So you really only need, in what you've laid out: Channel: Pages Channel: Products Pages has the fields that comprise a Page. Products has the fields that comprise a Product. Go to Channel Settings on your Structure screen. You'll see those two channels. Set each as Type: Page. ...


4

Use the Structure global variable {structure:page:uri} which is the same as EE's native "page_url" variable.


4

As Josh suggests in the comments, give this a whirl: {exp:channel:entries channel="statics" dynamic="no"}


4

The {structure:child_ids_for:XX} tag is parsed very late, after plugin tags have parsed. In other words, too late to be used as a tag parameter. The channel:entries tag will receive the unparsed structure tag. You will have to use an embed to get around this: {embed="your/embed" entry_ids="{exp:structure:child_ids entry_id='43'}"} And your/embed template: ...


4

You need to create a channel field into that channel and in channel entry, you need to assign that user group type who can access the page. for eg: Suppose you have a channel (named as "XYZ") and add a new channel field (as 'group_permission'). This channel field can be drop down and you can add group listing in drop down (as group A, group B) Now Go ...


4

Check out TJ Draper's Construct.


3

@James Right, I really do understand that argument, but at the same time the "streams of content" philosophy requires knowing quite a lot about content before it is ever created. Yep, you're absolutely right there. Most EE sites I've made usually end up with a generic 'Pages' channel, but I always try to drill home that it needs to be for exceptional ...


3

You'll need to use the Structure Entries add-on for this. Here's the basic idea (full docs can be found at the devot-ee page): <select id="Menu" name="menu"> {exp:structure_entries depth="1"} <option value="{page_uri}" {if {current_page}}selected{/if}>{title}</option> {/exp:structure_entries} </select>


3

I’m using 2.5.5 and 1.09 and I’m also experiencing this problem with the return parameter. When I check the rendered form markup I can see this in the HiddenFields div: <input type="hidden" name="RET" value="http://domain.com/templategroup/template"> Whereas that value is just the path to the template where I’m using the profile:edit:login tag. and ...


3

No, even though we use the same hooks as the Pages module EE has no parameter for that. Here are all of the available parameters for the channel tag: http://ellislab.com/expressionengine/user-guide/modules/channel/channel_entries.html#parameters


3

I did this exact same thing all natively with the exception of structure a few months ago. The challenge was to provide member groups access to different information on the same template with the added challenge of each member group having a state affiliation and union affiliation that they belonged to. The most difficult part was a file system (think ...


3

it should work according to the docs. have a look here: http://eeharbor.com/transcribe/faq Does Transcribe work with the next_prev tag? Yes, Transcribe does work with the next_entry and prev_entry tags in ExpressionEngine, please note, it requires you to use the parse="inward" parameter, Here is an example of how it works - {exp:channel:entries channel="...


3

This is an older question, but...for folks interested in this exact plugin for EE3, Structure has now been ported over. https://eeharbor.com/structure


3

Finally resolved this. On a whim I decided to try the URL /en and that had the same effect too so that meant it had to be language related, with the original problem being with 'de'. In my htaccess, which is where I started in the first place, I found a reference to a multi-lingual snippet, which included en|fr|es and wouldn't you know it....de. Removing ...


3

You can add this script to your blog page then /blog url redirect to first child page. {exp:structure:first_child_redirect}


2

Is this a typo whilst copy/pasting or are discipline02 children meant to cross-link to discipline01 children? discipline02 --Child01 URL://discipline01/Child01 --Child03 URL://discipline01/Child03 If I understand correcly I'm not sure Structure is the best fit in this situation. Structure largely exists to provide that familiar page-based CMS system ...


2

I recently had this same issue, when I learned that you need to set paginate_base="template/page" So lets say you have a news group and inside of that you have a index page it would be "news/index" for me that worked. With dynamic and cache set to "no"


2

indeed the parts can be related with playa, the main edition could be fetched with year="" month="" and day="". you'ld need some logic with segment_n conditionals and preload_replace or switchee to check if the segments where filled in. Edit: examples added Preload_replace You can use {preload_replace:varname="value"} to set a variable that is instantly ...


2

I haven't used that new feature, but it would be the same as the Pages module since we store our data in the same place.


2

I literally just saw this plugin on twitter this morning: Template Info, which was originally developed by Leevi Graham for EE1, and then Sean ported to EE2. Just add one or all of the following tags to your template: {exp:template_info attribute="template_id"} {exp:template_info attribute="template_name"} {exp:template_info attribute="template_group_id"} {...


2

You'll have to use another hook, template_fetch_template, and cache the template_id there: public function template_fetch_template($row) { if ( ! ee()->session->cache('your_extension', 'template_id')) { ee()->session->set_cache('your_extension', 'template_id', $row['template_id']); } } public function some_other_hook() { $...


2

Unfortunately there wont really be an easier way than with Freebie. It's designed for this very purpose when you need EE to ignore certain URL segments and comes in very handy when dealing with Structure because of the way it deviates from EE's native URL handling. In the case of both strict URL handling and Structure you definitely need to break those URL ...


2

I looks like your missing the / in the start_from parameter, this could be causing the issue. Also, add the max_depth parameter like Mark suggested if you want to cap the depth {exp:structure:nav add_level_classes='yes' show_depth='2' start_from="/shareholders"}


2

I solved the issue by adding max_depth="2". It appears that structure dynamically ignores the show_depth parameter when inside that section.


2

Right now, you would need to use the Structure Entries plugin for custom nav markup: http://devot-ee.com/add-ons/structure-entries


2

If you remove this parameter - error_handling="inline" you should see what default errors are causing the login to fail in the default EE error page - should help you fix the error.


Only top voted, non community-wiki answers of a minimum length are eligible