Download
(2013-06-23, 16:48:07)Carlos Wrote: As a workaround, you could just create the default page (no suffix) with the same content as your preferred language page (with suffix). Only snag is if you have to update it (them).
I suppose this solution is not very good for you, it's not easy for users, requires extra work...
Would be troublesome to explain to users and make things needlessly complex, whereas for the end user it should be as simple as possible. Imagine having to explain that to have a page just for the 2nd language they would need to create it on the default language too, even though they don't need it there.
At the same time it wouldn't realistically work if you ask me. As it would mean that the pages are basically included on the default website too. Maybe not in the menu (if you don't select that option) but they are still there.
Setting them to private in the default language would at the same time mean they are set to private in the non-default language(s).
At the same time, as opposed to an extensive rewrite of the plugin, it could perhaps also be possible to follow this route somewhat.
Create a new page, select a box stating for which language it is and then, in the case of the default language not being selected, have a sort of empty placeholder be used in the admin for the default language. So that it would work as per the functionality of the plugin but at the same time doesn't result in an actual page on the website of the default language.
Something to that extent.
Mind you, I am not a programmer so I am just throwing some things in the air which might not at all be feasible but who knows maybe a 'simpler' option like this would in fact be possible.
