5

You can not use Template Routes to remove index.php from your URLs. To remove index.php from you URLs you need to set up a redirect in an htaccess file, there are instructions here. Getting rid of the group name is where Template Routes comes in. Navigate to the Template Route Manager under Design ‣ Templates ‣ Template Route Manager. Locate the Route field ...


3

There's a similar post here But you could just look in the template debugging info. Another option would be to add something to each template that shows its name (either output to screen or as an HTML comment). Of course, you would then need to traverse the whole site and note which templates were used, and which ones weren't. Which would possibly be ...


3

I'm really confused by your question, but I'm going to make an attempt at clarifying some base concepts that I think you are wrongly assuming about a commercial grade CMS (content management system) like ExpressionEngine, and CMS's in general (possibly, not trying to say you don't know what you are doing). First of all, this is a content management system. ...


3

Now I can help you. The exp:channel:entries module just looks dynamically for an entry if its title appears on segment_2 or segment_3. For your template, it appears on segment_4. Buuuuuuuuuuut template routes overrides this behavior. From the docs: Template Routes overrides the default behavior of URLs, if you wish to use a Channel Entries Tag in your ...


2

The variables need to have a name and that url_title is a reserved word. To avoid conflicts, if you need to keep the Segments required set to no, keep a static part on the first segment: /{coaching_type:regex[(workplace|personal)]}-coaching/{coaching_title:alpha_dash} By this way, you can't grab the first segment by {segment:coaching_type}, but {segment_1}...


2

If you have an SQL editor, like Sequel Pro, that allows you to quickly edit data in SQL tables, the group_order column in the exp_template_groups table is where the order is stored. You can see the data with: select * from exp_template_groups Fancy SQL to renumber the groups to match the ID order, or alphabetical order, also might be doable.


2

Add dynamic="no" to your parameters like this {exp:channel:entries channel="gallery_slider" category="6" limit="1" dynamic="no"} test output {/exp:channel:entries} ExpressionEngine tries to determine the entry_id or url_title by itself, and if that id isn't part of that channel it won't show anything. Here's a link to the docs.


2

AFIAK there is no quick/easy/simple way. You're on the hook for trying to generate every page within the site and reverse-engineering it to see what templates were involved. With Templates Routes now possible this chore will get even harder. I have lobbied in the past for an addon that would not only do this, but find all the cruft in a legacy install - ...


1

I was having the same issue. I copied a new version of the "themes" folder from a fresh 2.9.2 install into my webroot. Then I put my third-party themes back in and all works great now. I think it's a set of styles or JS in the themes folder that you're missing. Good luck! Greg


1

I don't think you can. You also don't need to do that. The template file you are wanting to be your homepage is already called index. http://www.ee2docs.com/cp/design/templates/new_template_group.html#default-home-page Set your site template group as your default template group via this setting, and it automatically will make site/index your root.


1

1) Verify the template files system path is correct: Design > Templates > Global Preferences 2) Generally speaking, you can clear the current cache by navigating to "Tools > Data > Clear Caching". You can also try deleting all of the cache files in the /system/expressionengine/cache/ folder but I haven't tried that for this type of scenario.


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