1 The folder contains extensions which need to be updated through a web site.
2 The "Updates dialog" of the Extension Manager will mark the updates for these
3 extensions as "browser based update". The Extension Manager will open a browser
4 for each of the extensions and navigate to the respective website.
6 ================================================================================
8 ================================================================================
9 They contain <update-information>. That is they reference directly the respective
10 webX.update.xml (for example, web1.update.xml) files which are available at
11 http://extensions.openoffice.org/testarea/desktop/website_update/update/...
13 http://extensions.openoffice.org/testarea/desktop/website_update/update/web2.update.xml
15 The update information contain multiple URLs to "localized" web sites. Each URL is
16 assigned to a particular local. For example:
18 <src xlink:href="http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_de.html" lang="de"/>
20 The Extension Manager will choose the URLs where the lang attribute matches most
21 closely the locale of the office.
23 The following table shows what localized web site is used, when the office uses the locale
24 en-US. The web page will display the locale used. See update/web1_de.html, etc.
29 Installed office en-US
30 | publisher | release notes
31 =============================================
32 web1.oxt | en-US | en-US
33 ---------------------------------------------
34 web2.oxt | en-US-region1 | en-US-region1
35 ---------------------------------------------
37 ---------------------------------------------
38 web4.oxt | en-GB | en-GB
39 ---------------------------------------------
43 ================================================================================
45 ================================================================================
46 Need not be committed in extensions/www/testarea/desktop.
48 web6.oxt is intended for tests with extensions.services.openoffice.org.
49 It does not contain <update-information>. That is, the Extension Manager will obtain
50 the update information from the repository as feed:
52 http://updateext.services.openoffice.org/ProductUpdateService/check.Update
58 -Create the new extension in the repository.
59 -Provide a company name and a URL to the company website. In our case this should be
60 http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
62 -Create a new release for the extension. Upload the description.xml of version 2.0
63 (update/web6/description.xml). Provide a download URL for the web site (field
64 "Download from page / Open follow up page URL", which should be
65 http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
66 Provide release notes.
70 -Install version 1.0 of the extension:
71 desktop/test/deployment/update/website_update/web6.oxt
73 -Run the update in the Extension Manager
77 The Update Dialog should show the publisher name as provided in "Provider URL" field
78 of the extension edit page (not release).
80 A release notes link is displayed with a URL to the release notes as provided in
81 the "Provider Title" field of the extension release edit page.
83 When running the update then the web browser should navigate to
84 http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
87 ================================================================================
89 ================================================================================
90 Need not be committed in extensions/www/testarea/desktop
92 web7.oxt is intended for tests with extensions.services.openoffice.org.
93 It does not contain <update-information>. That is, the Extension Manager will obtain
94 the update information from the repository as feed:
96 http://updateext.services.openoffice.org/ProductUpdateService/check.Update
98 The description.xml which will be uploaded contains URLs for release notes and publisher
99 names/ URLs. That is, this information is not generated from the information of the
106 -Create the new extension in the repository.
107 -Provide a company name and a URL to the company website. In our case these should be different
108 to those provided in the description.xml. These should NOT go into the update feed.
109 Choose for example as "Provider Title": FOO and as "Provider URL" some valid URL but NOT
110 http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
112 -Create a new release for the extension. Upload the description.xml of version 2.0
113 (update/web7/description.xml). Provide a download URL for the web site (field
114 "Download from page / Open follow up page URL", which should be
115 http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
116 Provide release notes.
119 -Install version 1.0 of the extension:
120 desktop/test/deployment/update/website_update/web7.oxt
122 -Run the update in the Extension Manager
125 The Update Dialog should show the publisher name as provided in the description.xml.
126 That is: My OpenOffice en-US and NOT "FOO".
128 A release notes link is displayed with a URL to the release notes as provided in
129 the description.xml. That is:
130 http://extensions.openoffice.org/testarea/desktop/publisher/release-notes_xxx.html
132 When running the update then the web browser should navigate to
133 http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html