GetSimple Support Forum

Full Version: i18n and slug names
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
hmm, so I am using 3.1 with all the i18n goodness.
I am having an issue though.

All pages I have with a name with spaces in it has a slug(auto created) with underscores, naturally.

Now everything is being treated as a language.

so
I make

My Page

slug becomes
my_page

And i have a new language called
"page" all over the place.

How is this supposed to behave ?
Can I never use underscores in slugs now?
I have to avoid spaces in IDs.
And have to manually set titles now.

Just a little confused, any help appreciated.

Can this be fixed so only valid language codes are recognized as _ appends ?
shawn_a Wrote:hmm, so I am using 3.1 with all the i18n goodness.
I am having an issue though.

All pages I have with a name with spaces in it has a slug(auto created) with underscores, naturally.

Now everything is being treated as a language.

so I make

My Page

slug becomes
my_page

And i have a new language called
"page" all over the place.

How is this supposed to behave ?
Can I never use underscores in slugs now?
I have to avoid spaces in IDs.
And have to manually set titles now.

Just a little confused, any help appreciated.

Can this be fixed so only valid language codes are recognized as _ appends ?

The default behavior of GetSimple is to use -, not _.
Thus it should not be a problem normally.
Does your language file contain a TRANSLITERATION array which translates spaces to _?
hmm, this is all on my dev machine, default installs of everything.
3.1
latest of all plugins.

EDIT:
ok now I am twice as confused.
I went back and deleted the test file I just made.
test lang
slug test_lang (auto)

Recreated it and now it has dashes in it.
test lang
test-lang

I am absolutely baffled what is going on.
holy $@%^#&, whew.

Figured it out, what a waste of time.
I hate these kinds of bugs, they just tax you.

lol

Ok so the issue is special pages.

Special pages allowed me to create an reserved name ID field.
which creates the input named
post-id

which conflicts with guess what

page slug
post-id


I would suggest adding a prefix to special pages fields so they don't and cannot ever do this.
or conflict with custom fields from other plugins.

post-sp-fieldname would be awesome.

sigh.

EDIT:
Special pages is amazing btw.
Thanks!
shawn_a Wrote:Special pages allowed me to create an reserved name ID field.
which creates the input named
post-id

which conflicts with guess what

page slug
post-id

Thanks for finding this bug.
I'll fix it.