18

There are several strategies for best utilizing 404s on a Structure site: Hide Structure Templates to Prevent Duplicate URLs First, make sure that any Structure-assigned templates are either hidden, or inside a hidden template group (prepend the group or template name with "_" or "." - so "_blog" or ".blog"). This ensures that there is no duplicate EE URL ...


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


11

I've had the need to do this a number of times, particularly on sites that have press releases. For some reason, press release titles can be insanely long. This is all we ever have to do: In system/expressionengine/controllers/cp/content_publish.php, appx line 2279, change this to what you desire: 'title' => array( ... 'field_maxl' => 255 ), If ...


6

We also provide this script in the docs: http://buildwithstructure.com/documentation/how_can_i_batch_update_templates_for_existing_entries/


5

I'm not certain why Title Master would be insufficient for your needs. It handles increasing title length, url_title length, and works with Structure. Maybe if you state what it doesn't do that you need, that could help in identifying an alternative. Otherwise, if you're going to hack, I think you've hit all the main spots, obviously making sure the ...


5

You should be able to just do: {exp:structure:nav include_ul="no" start_from="forside" max_depth="1"} You can pick what page you want to start from, which in this case looks like "forside".


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

<input type="hidden" name="structure_parent_id" value="{structure:parent:entry_id}" /> Yup, this will definitely be required for this to work with Structure ... but is {structure:parent:entry_id} outputting something usable inside your Safecracker form? Check in your rendered page's source, looking at that hidden field. Otherwise, Structure won't know ...


4

You can share content, but all navigation and page data is site-specific, so you can't call from one into another unfortunately. It's just an EE/MSM limitation.


4

I think, you are using ExpressionEngine 2.5.3. You should see here https://support.ellislab.com/bugs/detail/18234 for the solution.


4

Could you use Matrix & Playa to solve this? Your Matrix field would let you add any number of sidebar widgets to the page as rows in Matrix. You can configure the Maximum Allowed Rows if you want to limit the number of sidebar widgets you associate. Within each Matrix row, your Playa field can be used to relate widget entries from their own Sidebar ...


4

Try doing this in your .htaccess file. This StackOverflow answer shows how. Something like this: RewriteEngine on RewriteBase / RewriteRule ^/(students|parents|faculty|alumni|galleries)/(.+)$ /$1 [L,QSA] The Router addon may also work for you. Router is a regular expression based routing system for ExpressionEngine requests. It allows you to define any ...


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

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

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

I suggest copy/pasting the serialized array from the site_pages column and using an online generator to unserialize it. Then copy the unserialized array over to a text editor to find/replace the old template_id with the new the template_id. The array contains a URI array & Template array. The template array is the last array. So look for [1] => 4 ...


3

If you're using Structure 3.3.8, it already includes the Structure Entries functionality (Official Documentation). Maybe give the native version a try and see if that parses the Assets tag correctly? {exp:structure:entries parent_id="{embed:my_parent_id}"} ... {/exp:structure:entries}


3

I also just just noticed that you are using {page_image}...{/page_image} as a variable pair, and also using a single variable {page_image} inside that loop (that you are passing into the CE Image src= parameter). I think that's probably a typo, right? Shouldn't the single variable be {url}?


3

As far as I know, the Structure nav tag does not output any title attribute for links. There is a free third party add-on Structure Entries http://devot-ee.com/add-ons/structure-entries which you could try using to generate your navigation links instead. You specify your own markup for each link, so you could specify the title attribute etc. Alternatively, ...


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

@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

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="...


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