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

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

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

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

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.


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

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

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


2

Structure is the only self-contained solution to have a completely automated, whole-site navigation for every Pages URI that is automatically kept up to date as the end user adds new pages or changes the overall Pages URI hierarchy. But Structure is more of a whole-hog commitment to how you set up and build your site (some like this, others do not). In other ...


2

Ben Croker of PutsYourLightON has been working on an API specifically designed for CRUD functionality. You should take a look at it here... http://www.putyourlightson.net/open-api And here is the repo for it... https://github.com/putyourlightson/open-api I have messed with this some and it has some great potential.


2

Pop the following in your header: {exp:seo_lite entry_id="{structure:page:entry_id}"} If you do not add a title into the SEO Lite title field, the entry title will be used for the title meta tag. If you do add a title into the SEO Lite title field, that will be used.


2

If the native Entries method doesn't suit your need, Structure Entries will solve your problem.


2

Make sure you also remove any rows referencing Structure references in the modules, extensions, and accessories tables.


2

You need to write custom script for this. You can find script example on Structure support forum. My small modification of this script (you need to create template with rights to run php code) !make DB backup before run the script! <?php /** * Batch reset template_id for Structure entries */ $site_pages = ee()->db->query( "SELECT site_pages ...


2

I've actually run into this issue on a couple of MSM sites in the last couple of weeks. From what I can gather, at some point the root URL is stored in the 'site_pages' column in the 'exp_sites' table, for each site. I have a PHP script that decodes/encodes and unserialzies/serializes the data, and tells you what to change. Ping me at @degerstrom or pal@...


2

I would suggest you use EE categories for your product categories rather than channels. Each product tile is an entry in the products channel, and each tile is assigned to one or more categories which determines which product grid it shows up on. The index/category page is then just a list of the categories in your product categories group, and the product ...


2

Each entry is attached to a single URL, but with something like Freebie you possibly could. You could have an initial channel tag on the main page wrapped in conditionals. This channel tag would have the certain fields you want to show. Then if you appended a random segment on the end that Freebie is ignoring, you could have another channel tag showing the ...


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