Uploaded image for project: 'CMS'
  1. CMS
  2. CMS-631

I18n & skins

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major Major
    • 3.3
    • 2.1.10, 2.2.7, 2.6.6, 2.9.12, 2.9.19, 3.0 M3
    • Skins
    • None

      When adding a new skin its catalogue is unknown (except if we restart)
      For a small cms, it does not matters, except when you have a bug cms where you build many sites with new skins and you does not want to restart
      !

          [CMS-631] I18n & skins

          Raphaël Franchet made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Raphaël Franchet made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Raphaël Franchet added a comment -

          ok for me

          Raphaël Franchet added a comment - ok for me

          Cédric Damioli added a comment -

          I propose to do nothing if the skin is added or modified by hand directly on the server.
          We could scan periodically the skins/ folder for new skins, but we won't be able to detect modified skins et it would certainly be not fast enough for developers.

          There's a method I18nTransformer.needsReload() which may be called from code when modifying skins or i18n catalogues.

          Cédric Damioli added a comment - I propose to do nothing if the skin is added or modified by hand directly on the server. We could scan periodically the skins/ folder for new skins, but we won't be able to detect modified skins et it would certainly be not fast enough for developers. There's a method I18nTransformer.needsReload() which may be called from code when modifying skins or i18n catalogues.
          Cédric Damioli made changes -
          Link New: This issue Est composé de ARTISTEER-2 [ ARTISTEER-2 ]
          Laurence Aumeunier made changes -
          Assignee New: Cédric Damioli [ cedric ]
          Fix Version/s New: 3.3 [ 10470 ]
          Fix Version/s Original: 3.LATER [ 10121 ]
          Raphaël Franchet made changes -
          Description Original: Quand on ajoute une nouvelle skin son catalogue est "inconnu" si on redémarre pas.
          Dans le cas habituel on s'en moque sauf que :

          Cas d'utilisation 1
          * je change de skin coté CMS
          * à la génération elle est copiée sur le SITE et n'est pas "reconnue"

          Cas d'utilisation 2
          * en massivement multisite, les gens créent bcp de skin et veulent pas redémarrer à chaque fois
          		 New: When adding a new skin its catalogue is unknown (except if we restart)
          For a small cms, it does not matters, except when you have a bug cms where you build many sites with new skins and you does not want to restart
           !
          Summary Original: I18n et skins New: I18n & skins
          Cédric Damioli made changes -
          Workflow Original: jira [ 11833 ] New: Ametys [ 13273 ]
          Raphaël Franchet made changes -
          Fix Version/s New: 3.LATER [ 10121 ]
          Affects Version/s New: 3.0 [ 10113 ]
          Affects Version/s New: 2.2.7 [ 10083 ]
          Affects Version/s New: 2.9.19 [ 10111 ]
          Affects Version/s New: 2.6.6 [ 10091 ]
          Affects Version/s New: 2.1.10 [ 10081 ]
          Julien Couret (Inactive) made changes -
          Project Import New: Thu May 28 17:09:53 UTC 2009 [ 1243530593866 ]

            cedric Cédric Damioli
            raphael Raphaël Franchet
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: