Hot answers tagged

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


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


3

Because your freebie conditional uses an {if:else} statement, it is considered an advanced conditional. Advanced conditionals are rendered after module/plugin tags are rendered (see: Rendering Stages). The safecracker tag in the else condition is getting parsed and executed before the condition is evaluated. The solution is to split it into two simple ...


3

ExpressionEngine 2.8's introduced Template Routes so you now have more control over how your templates are processed. It allows you to override the default template route, which is /template_group/template. For example instead of going /blog/read/url_title you can now add a template route for read.html in the blog template group to load like /blog/url_title ...


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

As long as you don't have a template or template group named that url title, you can code your index template to take in {segment_1} as a url_title. {exp:channel:entries channel="foo" {if segment_1}url_title="{segment_1}" dynamic="no"{/if}} edit: This only works if you set strict url's to no


2

So the grand and magnificent Mark Croxton let me know that the problem in this example is my use of line breaks, which are being passed into the parameter values and choking EE. I removed them from the template, but he also said that either {exp:stash:set} or {exp:stash:get} could have the paramater trim="yes" added to it to clear out the extra whitespace. ...


2

You can simply make entries for the return pages, and have transcribe handle it for you. What i do is to embed the form: {embed="_inc/.contact_form" thepath="{exp:transcribe:uri path='/contact/thank-you/'}"} {exp:forms_js_validation:init lang="{transcribe:language_abbreviation}"} {exp:forms_js_validation:add selector="form" require_class="...


1

Late to the party here but my guess is because you have dynamic="no" so it will always return a result.


1

An {if:else} conditional won't work here (or with any other tag to try to change a parameter) because it's parsed after {exp:...} tags. This is often called an advanced conditional. You can see this by turning on Template Debugging: the parameters should look unparsed or partially parsed for the tag. I don't have experience with Transcribe, Structure and ...


1

With wgcode_categories, you can add an orderby="cat_name" parameter.


1

Here's a different page/embed approach to ponder, it may make maintenace much easier. Think inside out and consider using partials. about partials Heres our layout. Template = layout/.default <!DOCTYPE html> <html lang="en"> <head> <title>{exp:stash:head_title} - LocalYak</title> {sn_head} {...


1

Basically I was using freebie segments to dynamically add sorting and ordering parameters. Low took a look at the site and recommended that the better (and correct!) way of dynamically adding the sorting and ordering parameters in Low Search is to build the URL and include them in the query. This can be done numerous ways, but the end result looks something ...


1

I've seen multi-language site implementations that deal with similar issues since you essentially want something like this: http://mysite.com/en/ http://mysite.com/fr/ And depending on the URL, you want {site_url} to return the language code segment as well as the domain (http://mysite.com/en/). Here's a pretty good write-up of how to accomplish this: ...


1

To make "{cf_news_title_{freebie_1}}" to work, freebie has to be parsed early. So, let's create an alternative to this. If all of the first segments of URLs is code of languages, on your config. php, add this: global $assign_to_config; if(!isset($assign_to_config['global_vars']))$assign_to_config['global_vars'] = array(); $lang_code = substr($_SERVER['...


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