Skip to content
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

Clarify globalize slug documentation further #309

Merged
merged 1 commit into from Jul 4, 2012
Merged

Clarify globalize slug documentation further #309

merged 1 commit into from Jul 4, 2012

Conversation

robyurkowski
Copy link
Contributor

In response to @norman's comment here:

The previous change made in dc78438 lost clarity when it assumed parallelism, when in fact the first object had changed with the same commit. Now it should be clearer that the model must set the slug column translatable, not the translation table.

@norman
Copy link
Owner

norman commented Jul 4, 2012

Sorry, but it's still not clear. I think it should say something like:

In order to use this module, your model's table and translation table must both have a slug
column, and and your model must set the +slug+ field as translatable with Globalize.

@robyurkowski
Copy link
Contributor Author

I was about to ask this, because I'm currently translating a few tables and things are blowing up without that. I was going by what was said in #293, though I think I understand where we misconnected.

Third time's the charm — I'll correct and squash shortly.

It should now be clear that both the model's table and the model's
translation table must have a slug field, and the model must declare the
slug field translatable.
@robyurkowski
Copy link
Contributor Author

There we go.

norman added a commit that referenced this pull request Jul 4, 2012
Clarify globalize slug documentation further
@norman norman merged commit 4052027 into norman:master Jul 4, 2012
@norman
Copy link
Owner

norman commented Jul 4, 2012

Pulled, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants