Can't change page titles from admin

[Roope]

I have very strange problem on one little multilingual site that has only default language set at the moment. I can only edit Title field of Home page but all others are uneditable. The text that was used on creation rolls back after page save. Title is editable via API though.

Site is build on dev branch. Just pulled latest updates but no change. There is only admin hotkeys and emo modules installed (except language support). Default language changed to finnish and here is only error that system throws on page save: Session: Missing required value (_pw_page_name)

Could this be some bug on PageTitleLanguage module or is there something obvious I'm just missing again? I have no problems on any other projects developed from same branch.

[Roope]

OK, so I was able to reproduce this scenario: when you use PageTitleLanguage fieldtype with only default language installed, content of the Title field is not editable. Content does not change after page save. Problem is solved when you install more languages to PW.

Maybe this thread should be moved to Multi-Language Support forum instead where we can discuss is this even bug since why would you need PageTitleLanguage field with only default language installed. Well, I did so because we will have different languages for the site in the future but first release will be only in finnish.

[ryan]

I'd consider that a bug. There are reasons to install language support even with only 1 language, like if you want to take advantage of static translation capability in template files. I've added this as an issue on GitHub, and I'm hoping to get through the current queue of issues here over the next few days. 

[Roope]

Thanks for the fix!

[adrian]

I just came across this in PW 3.0.105

Has anyone else also seen this recently?

@ryan - any chance there has been a regression regarding this?

As soon as I add a second language to the system it works again.

[adrian]

Turns out it's only an issue when I have this module installed: http://modules.processwire.com/modules/restrict-multi-language-branch/

Although that module works by setting the template noLang flag so I expect the same issue could also be replicated by setting that for a template, so I do think this needs some attention still.

[adrian]

Bit me once again today :)

In this case I did have that module installed, but even after disabling it, I still had issues with a particular template where I had specifically set noLang in the advanced template settings, so watch out for that.