Sign in Register
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Feeleen 1 post 71 karma points
    Aug 30, 2016 @ 11:35
    Feeleen
    0

    Is it a good idea to store site settings in a special content node?

    I want to create a node "Settings" with a document type containing all the props and settings for my site and then look for these prop settings in my view's code where needed

    Are there any underwater rocks on this way?

    PS. Backoffice ui is too complicated to develop..

    Copy Link
  • Ian 178 posts 752 karma points
    Aug 30, 2016 @ 14:32
    Ian
    2

    I would say the only issues are:

    Ensuring the node is always created (more of an issue with a multiligual site where the tree structure might be being duplicated when adding new languages)

    Maintaining global access to the node without hard coding anything.

    This is why in a lot of cases the sites extend from a single root node (or root not per language) and settings are put on a tab in that document. This way you know you have easy access to settings wherever you are in the site.

    The plus sides of having a separate document type however are that you can limit admin access to it. I don't think there would be any big issues.

    Copy Link
  • Alex Skrypnyk 6182 posts 24283 karma points MVP 8x admin c-trib
    Aug 30, 2016 @ 14:50
    Alex Skrypnyk
    0

    Hi Feeleen and Ian,

    Can you provide screen of your backoffice?

    Do you have one root node? One language?

    Let us to look at your structure and we will decide is it make sense to use Settings node.

    Sometimes it's better to store data in the root node.

    Thanks,

    Alex

    Copy Link

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies