-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slugs not generated when using with DoctrineFixturesBundle #254
Comments
well my blog has a cron to generate demo data and it works fine. it does not use data fixtures, but it should be pretty much the same. maybe you can test if it works for you? if it does not, it might be the issue with mac os unicode as far as I remember there was something like that. in that case you would need different transliterator for sluggable |
Ok, after another check it doesn't work in my browser either on this machine (works on my notebook though). How could I change my transliterator? I seems that there is an issue in OSX 10.6 which is fixed in 10.7 (given the transliterator works on my notebook). |
you can do |
Just tried it on OSX 10.7 and it worked as expected. So it seems there is an issue when using OSX 10.6 - maybe someone can confirm this? |
I remember someone had this issue some time ago. maybe you can search through the issues, but anyway, I cannot help you much here |
I found one issue where this problem was discussed but the solution didn't worked for me though. I might try this again or wait for PHP 5.4 to use the shipped Transliterator from the intl-extension. ;) |
Add COLLATE for MySQL
Hi there,
when I load fixtures using the DoctrineFixturesBundle, the slugs for those entities are not generated. It works in the browser. One interesting thing is, that some slugs get an -1 as value and some are simply empty.
I found this issue with StofDoctrineExtensionsBundle stof/StofDoctrineExtensionsBundle#2 which has been fixed then, so I'm not sure what the problem might be because the listeners get triggered.
The text was updated successfully, but these errors were encountered: