Jump to content

nico

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

nico's Achievements

Newbie

Newbie (2/6)

1

Reputation

  1. Hi all, I'm trying to access the home/root page's multilanguage title field via API like so: $page->title; this works on all other (sub-) pages, which are using the exact same template as the home page. only on the home page, it is not working to either output or save a different language title than the default one. it always outputs the default language page title – and saving a new page title via api (no matter if default or other languages) is not working at all (while working fine on normal sub pages with the same template). when saving via the admin-interface, it is being saved to the database - but still not output properly when fetched via the api. this is only happening with the required multilanguage title field. all other content fields are working just fine. is there any reason for this, like the root page title being restricted somehow? we tried comparing the different pages and templates and couldn't come up with any difference, except for the home page having the status "systemID" in settings. thanks, N.
  2. Thanks for this @horst ! The workaround looks way cleaner than using additional fields or checkboxes. Additionally, we'll be setting the actual secondary language slug (f.ex. "en") instead of "onlySecondary" as default page title (for pages which only contain secondary language data) in order to pass on the specific language information. Best, -N.
  3. Hi @horst, thanks for your reply! Thanks for clarifying the need of an always active default language as fallback – as for the second part: I have exactly the problem, that the automatically synced multilanguage pages will each only have one language set, and if that language is not the default language that's where it gets messy because the page title cannot be set only for a secondary language. I've looked into a few workarounds (f.ex. additionally setting the language from the json in a checkbox or additional field, but write the actual contents into the default language fields instead.. but this would mean much more code/filtering on the frontend which I'm trying to avoid).
  4. Hi all, We were trying to find a way to set up the following functionality and are not sure if we might have overlooked something, is it possible to: - either create an entry with the title field being set in a secondary language only (keep default language tab for the required title field empty) - or, make it possible to set any language (including the default language) active/inactive by using the checkboxes in the page settings (currently this only works for the secondary languages)? The goal we are trying to achieve is to be able to sync/create new pages via the API from json-data and depending on which language the data origins from, it should only set the according tabs for the multi-language fields (including the required page title). best, Nico
×
×
  • Create New...