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


11

url_title_path requires a template_group/tempate to be passed to it, so it can return a complete URL. It should be used when creating links. (It seems to be the same as title_permalink, which is what I always use myself.) e.g., {url_title_path="news/entry"} returns http://mysite.com/news/entry/hello-world url_title is simply a variable which returns an ...


8

EE has always maintained a unique entry id, but only unique url titles within a given channel. There is no way that I know of to force unique url titles across all channels. This usually isn't an issue so long as you are specifying channels in your template code. Incidentally this is why EE uses a /category/ segment when using category url titles - that's ...


7

This is a feature of ExpressionEngine. You won't be able to use numbers alone as URL Titles. If you managed it in the past, it was probably a bug/fluke that it was allowed, or the entry was created in a non-standard way. In the content_edit.php file there's a check for is_numeric() that triggers an error. // Is the url_title a pure number? If so we show ...


6

You can do a bulk update of URL Titles with SQL like: UPDATE exp_channel_titles SET url_title=REPLACE( LOWER(title) , ' ', '-') WHERE channel_id=1 You can see URL Title is being derived from Title replacing space with dash and changing in lower case. You can have channel_id and any other condition in WHERE according to your preference. You can have second ...


6

There's plenty of addons already out there: http://devot-ee.com/add-ons/title-master http://devot-ee.com/add-ons/mx-title-control


6

You can use any ee add-ons which can create url_titles from another field (for example - MX *Title Control) + somethink like low_replace to remove dot's. You can replace it on JS level, you can use Foreign Character Extension You can make your own ext. using entry_submission_start hook. If you decide to hack core: \expressionengine\helpers\EE_url_helper....


5

I would do this using a 'featured quote' relationship field (either native or Playa depending on whether you want the client to be able to select more than one quote per entry).


5

Using a specific entry_id begs for a problem later - I wouldn't. What you can do is create a custom status for that channel and then let the entries tag target that status specifically. Limiting the results to 1 also will help focus on the individual entry; if you add a new entry with the same status, it will take only that last, most-recent version, no ...


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


4

You can most definitely do this. Just use the channel entries API hooks. You can use a conditional to test to make sure your logic performs only for new records vs. edit. It would actually be relatively easy to do. The most time consuming part would be adding a settings pane so you could use a UI to building the URL titles on a per channel basis (for example)...


4

That's odd, you've always had to use an alpha character - not numbers only. EE would interpret those as IDs rather than URL titles and become very confused. I'm not sure how you'd have number-only URL titles if submitting directly through EE's forms.


4

Entry ID's are not re-used, so you are right - if someone deletes that entry and publishes another the code will fail. URL_titles are re-created, so if the original entry is deleted and a new one is published with exactly the same title (and hence, url_title), the code will still work. So url_title is safer, but still not awesome. A custom status would ...


4

Like, multiple different ways, depending on what you want to do. One way: {!-- template: teamplate.group/index.html (default template group) --} {exp:channel:entries {if segment_1} url_title="{segment_1}" {if:else} url_title="home-page-entry-url-title" {/if}} ... maybe use a homepage partial here if no segment 1, otherwise use a ...


3

I always tend to identify the product details page as simply /details/ to avoid this problem, but to achieve what you're after, the following should work (in theory). Note that your example doesn't take into consideration pagination which would change the last segment. Maybe the client doesn't want it, but may once they get bulk products in there. The ...


3

You are using {permalink=enewsletter/article} in your code. http://ellislab.com/expressionengine/user-guide/modules/channel/channel_entries.html#permalink That will return an id What you want is {title_permalink="enewsletter/article"}


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

You can do this with last version (2.8.8) of MX Title Control. You can add {random_string} tag into URL Title Pattern and get 10 characters random string. Hidden Configuration Variables $config['mx_random_string_length'] = "20"; $config['mx_random_string_pattern'] = "0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ";


3

Have a look at the Magic Fields add-on - it can do this.


3

As variant you can just use MX Title Control and regenerate you url_ titles by any pattern; by default this ext is repeated default EE logic and convert url_title into a low case. if you want to change this logic, /mx_title_control/ext.mx_title_control.php, line 125: replace $url_title_name_out = $this->convert_accented_characters(strtolower($...


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


2

It's odd that you are getting p tags with formatting set to none. Was this a different field type at one point? Try deleting out any data, saving the entry, then editing it again, add the url once more and finally saving of course. Just some thoughts that might help you (or others) though, might be slightly to one side of your current situation; if that ...


2

You may also consider using Switchee


2

If you search for SurgerEE on devotee - you'll be able to use that to query based on regular expression. https://github.com/dsurgeons/SurgerEE/wiki/String is the function. I've used it lots of times and to really useful. Sorry for the brevity - on the iPad and mobile at the mo.


2

If you're looking to have a URL structure of domain.com/about-us/where-and-when your sidebar would then need to have "about-content" removed as a segment. That should be all you need to change to have the links establish the URL structure you're looking for.


2

You could build a custom extension that queries the database (I think exp_channel_titles) for the url_title supplied, then return an error to the user if it already exists. You would probably want to look into the safecracker_submit_entry_start hook. Alternatively, you could use JavaScript and perform some validation on the front end that passes the ...


2

The Detour Pro addon should do what you need. Detour Pro handles simple redirects like this/old/page to this/new/page The PathFinder addon seems like it will add redirects automatically. Configure ExpressionEngine to automatically perform an HTTP 301 redirect when the URL slug (url_title) for an entry is changed. Want to allow content editors to change ...


2

The no_results conditional should work, something like: {exp:channel:entries channel="speed_sales" dynamic="no" url_title="{embed:url_title}"} {if no_results} <!-- Content for no results --> {if:else} <!-- Otherwise ... --> <h2>{title}</h2> {if lead_copy}<p class="lead">{...


2

As far as I'm aware no. Because EE will strip out the non-alpha numeric characters, not replace them with their similar counterparts. It's not relevant to the Database. So either you have to manually edit the url_title field each time or look at other options. But in looking elsewhere for solutions may give you an even better end result - of being able to ...


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