Doctrine 1

Impossible to create non-unique slugs

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.2.2
  • Fix Version/s: None
  • Component/s: Sluggable
  • Labels:
    None

Description

I want to create a non-unique slug of a title field from my table.

But I've found that when I change unique from 'true' to 'false' the slugs were not created or updated

In lib\Doctrine\Template\Listener\Sluggable.php inside preUpdate() function the first if() statement disables the unique (false) option.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jacob Mather added a comment -

Theoretically this should clear up the issue. Sorry for not having the time for a complete test at the moment,

Show
Jacob Mather added a comment - Theoretically this should clear up the issue. Sorry for not having the time for a complete test at the moment,
Hide
Permalink
webPragmatist added a comment - - edited

The patch by Jacob doesn't work. The reason for the unique check is to bypass appending a numeric value to the end of a slug in the even two exist.

It just needs to somehow be directly sent to the urlize function.

Show
webPragmatist added a comment - - edited The patch by Jacob doesn't work. The reason for the unique check is to bypass appending a numeric value to the end of a slug in the even two exist. It just needs to somehow be directly sent to the urlize function.
Hide
Permalink
Jacob Mather added a comment -

I would just like to post an update after I've been able to test:

The only functionality that i found actually broken was updating a slug with unique set to false.

The reason was the wrapped if.

If you set unique to false, slugs will still fail to update as canUpdate must also be set to true.

The patch, so far as I can determine, does correct the underlying issue if a slug failing to update when unique is false and canUpdate is true.

Show
Jacob Mather added a comment - I would just like to post an update after I've been able to test: The only functionality that i found actually broken was updating a slug with unique set to false. The reason was the wrapped if. If you set unique to false, slugs will still fail to update as canUpdate must also be set to true. The patch, so far as I can determine, does correct the underlying issue if a slug failing to update when unique is false and canUpdate is true.

People

  • Assignee:
    Jonathan H. Wage
    Reporter:
    Adwise Internetmarketing
Vote (2)
Watch (2)

Dates

  • Created:
    Updated: