Edit View - Allow People To Set The Slug

[geoffd]

Right now the slug for a blog post defaults to the ID.

We should have it default to the title of the post.

We should then show the slug beneath the title and allow people to edit it. Probably show it as text with a little edit button. (John should suggest something for how that should work.)

[johnnyoffline]

Slug Sample

[boutell]

We need a single slugifier that is also invoked for editing and changing page slugs... some refactoring wanted here. It should be pluggable by setting a callable in app.yml so folks can come up with alternate ones that work for their funky character sets if they want.

[johnnyoffline]

The slug field is empty until you type a post title. Any changes to the post title should update the slug UNTIL you publish the post. After the post is published, the slug is stable. The slug must be manually edited after the post is published.

The slug should be displayed as a live text field. We will style it to look editable onfocus. It should save onblur.

[johnnyoffline]

Dan, I am going to mock this up with javascript / css so that it "looks" right.

When I get it there, I will assign this back to you for making it actually submit and store to the database.

[johnnyoffline]

Permalink URL

[johnnyoffline]

Dan:

I need help assembling the "real" path to the post so it can be displayed as the permalink.

in editSuccess.php

Error: Macro Image(permalink-url.png) failed

Attachment 'ticket:206: permalink-url.png' does not exist.

<?php // Dan, Can you echo the REAL URL prefix here -- I don't know how to build a URL based on the complex blog route business we are doing  ?>

<div id="a_blog_post_permalink_interface">Permalink: http://site/blog/url/<?php echo $a_blog_post->slug ?></div>

[johnnyoffline]

Error: Macro Image(permalink-url.png) failed

Attachment 'ticket:206: permalink-url.png' does not exist.

[johnnyoffline]

There's a space in the filename. Dolt!

[johnnyoffline]

Dan, this is roughed in now.

There's notes in the file for you editSuccess.

Also, I am using a jquery.slugify.js to clean up the slug before it submits.

This is most likely temporary. I liked your idea for submitting one ajax call instead of two.

We can knock this out tomorrow.

[johnnyoffline]

The slug is going to work like worpdress.

Upon first save it is set to the title of the post and will remain that way unless the blogger explicitly changes the slug.

From that point on the slug will reflect the original title even if the title is updated / changed after that point.

[johnnyoffline]

This works from a frontend perspective.

All of the markup and JS lives in editSuccess or aBlog.js

Please confirm that the slug works how we want it to (I think it does).

Then assign to Rick for review.

Thanks.

[johnnyoffline]

Dan:

The slug saves but nothing comes back from the server. I need a slugified slug to get returned from the server and passed back into my input field.

ALSO:

I need the URL leading up to the slug to be representative of something relating to where the post could be found in the site. Let's make this simpler rather than more difficult. Maybe something like this:

First Step: check if there is only 1 blog engine, if so, great use it to build the url preceding the slug.

I don't know, this feels like a design problem to me. Rick / Tom should weigh in on this part.

[boutell]

There's a weighty ticket on solving the second half of this problem already in which we worked through the design issues of how to pick the best engine page to use.

See #145

[dordille]

This has all been wrapped up. [1095]