erp5_officejs: fix jio_configurator

bt5/erp5_officejs/PathTemplateItem/web_page_module/gadget_officejs_page_jio_configurator_js.js

@@ -15,10 +15,10 @@
           type: "replicate",
           // XXX This drop the signature lists...
           query: {
-            query: 'portal_type:"' + portal_type
+            query: 'portal_type: ("Presentation", "Web Page", "Spreadsheet", "Text", "Web Illustration")'
             // XX Synchonizing the whole module is too much, here is a way to start quietly
             // Supsended until modification_date is handled for synchronization
-              + '" AND modification_date:>="'
+              + ' AND modification_date:>="'
               + old_date.toISOString() + '" ',
             limit: [0, 1234567890]
           },
@@ -42,9 +42,7 @@
           },
           remote_sub_storage: {
             type: "erp5",
-            url: (new URI("hateoas"))
-              .absoluteTo(location.href)
-              .toString(),
+            url: "./hateoas",
             default_view_reference: "jio_view"
           }
         };

bt5/erp5_officejs/PathTemplateItem/web_page_module/gadget_officejs_page_jio_configurator_js.xml

@@ -230,7 +230,7 @@
             </item>
             <item>
                 <key> <string>serial</string> </key>
-                <value> <string>947.30152.42918.48418</string> </value>
+                <value> <string>953.32209.35088.11844</string> </value>
             </item>
             <item>
                 <key> <string>state</string> </key>
@@ -248,7 +248,7 @@
                     </tuple>
                     <state>
                       <tuple>
-                        <float>1450730073.08</float>
+                        <float>1472233610.35</float>
                         <string>UTC</string>
                       </tuple>
                     </state>

[Cédric Le Ninivin]

This way of solving the problem seems too heavy in term of bandwidth consumption for users. I'd rather fix the way the portal_type setting is store and accessed.

[Boris Kocherov]

@cedric.leninivin, i understand why you wrote this line of code. But if the storage description is saved in persistent storage and this storage is the same for all gadgets, then it doesn't work.

I agree i did it the simliest way. Of course you can change it as you think, for me it's just should work.

[Cédric Le Ninivin]

I agree, it was done fast and the problem appear when using the same domain but doesn't in production. I'll fix the way the stting is accessed so that it depends on the application.

[Cédric Le Ninivin]

But this current change is harmful for the production case were each application has its domain.

[Boris Kocherov]

I've deleted this commit. i made it as i thought the global setting gadget had been not working, but i just hadn't understood correctly how it had to work. For my testing purposes i have made subdomains for each application, so now i have the similar environment as Nexedi's production, and as a result i don't need this patch too.