 |
|
Item13452: Extensions web enhancements for compatibility, encoding, etc.
Priority: Enhancement
Current State: Confirmed
Released In: n/a
Target Release:
Current State: Confirmed
Released In: n/a
Target Release:
Applies To: Web Site
Component:
Branches:
Component:
Branches:
- Re-encoding of Topic text and text attachments during copy in Foswiki::Configure::Package
- Extensions release process, and dealing with encoding during upload
- Config.spec issues with encoding.
- Default encoding of extensions should be iso-8859-1. unless they cannot be used on Foswiki 1.1
- This keeps good compatibility with Foswiki 1.0 / 1.1
- New non-backwards-compatible extensions should default to utf-8
- Package form and installer should flag the character set used in the distribution.
- 1.2 Package installer needs to detect / default the distribution encoding, and re-encode into the {Store}{Encoding} during installation
- pseudo_install is another can of worms. Can't symlink incompatible encodings.
- pseudo-install should be a feature of Foswiki::Configure::Package. Linking when requested, and only for compatible encoding.
- This would solve other issues related to incomplete installation of config.spec, Plugin module name, etc.
It is hard to believe what has evolved from simple questions on IRC about the DateTimePlugin. I tried somewhat classify what plugins should be tested for the "1.2 compatibily", but this is really an mess.
For example: - In the github we have 570 repositories (Extension, Plugins, Addons, Contribs - etc..), plus 45 Contribs/Addons from the "distro".
- when the wizard consults the foswiki's web with the query:
http://foswiki.org/Extensions/JsonReport?contenttype=application/json;skin=text;release=Foswiki-1.2.0_Beta_1;version=v1.1.999_002;pluginsapi=2.3
it gets returned (thanks God) only 310, so the list is somewhat filtered on the server side. - However, the filtering works strangely, because it sure isn't based on the received (release,version,plugins) parameters, because for example it still offers to install the ZonePlugin what is ages in the core and sure not needed for the 1.2.
- classify, what plugins are in the real use
- I asked gac410 about some usage stats, be noting such exists.
- Maybe something could be extracted from the log-files - e.g. what plugins are downloaded in the last 7 years and how many times...
- also, i could extract from the
git logwhat plugins are got updates from 2008, (not counting the global updates, as replacing TWIKIWEB to SYSTEMWEB and like) - but this is simply doesn't helps at all.
- update for the each actively used plugin the required informations about its compatibility. Doing this for each plugin, is an terrible and hard work and TBH, many plugins are useless.
- offer for download really only highly polished extensions - as our marketing texts states
- Extensions what doesn't installs cleanly and without any errors from the configure's Extension installer (or its command-line equivalent e.g.
tools/extension_installer) should not be offered. - Foswiki shouldn't be as the "goods" from chineese e-shops, where the quantity replaces the quality.
- offering for download problematic extensions hurts Foswiki reputation (Repeat this with myself several times.)
- experienced users, who are able manage to work some rarely used and problematic extensions, they sure will be able to manage manually download them from the github or FO.
- We really badly needs classify what extensions are in the active and common use. (e.g. it is used not only by the extension author).
- unmaintained extensions should be not offered for download, or only after checking some checkbox, in the Wizzard interface - "only at your own risk".
- also, the IRC-guest shown another problem: he states: the DateTimePlugin didn't works, because it didn't works nor in the foswiki.org. We need:
- install to foswiki.org all our flagship and really highly polished extensions,
- and clearly mark in the FO's Extension web - the list of installed plugins. Maybe, enough add to the top of the Extensions an TWISTY section what ajax-includes the InstalledPlugins topic. The user should know the extension's installed-status.
- in the 1.2 - the bootstrap process should generate one unique UUID for each Foswiki installation (e.g. the bootstrap should hardcode this UUID into some source code, or at least as an variable in the LocalSite.cfg).
- and this UUID should be sent with the extensions wizard with each "study" and/or "download" request. It is completely anonymous but allows to us gather some more-real plugin usage/install stats.
- the above probably isn't too hard to implement - for CDot probably 20 minute
- A bit more hard is implementing an new section to the configure what asks the users to allow SHARE with the FO
- the list of all currently installed extensions
- and some other (but fully anonymous) usage info
- and sent this info as an JSON string to FO - for example once a month when if and when the user runs the configure.
Uff...
-- JozefMojzis - 07 Jun 2015
George, I somewhat disagree with the Default encoding of extensions should be iso-8859-1. It is a step backward and in the future we will cope with the non-uniformity charset-problem again. We need (IMHO) convert all current (non-ascii) extensions to utf8. Now and forever, and offer to download only good extensions.
-- JozefMojzis - 07 Jun 2015
I think MultiLingualPlugin is better suited for translations than DateTimePlugin as it lets you add translations as part of the wikiapp.
-- MichaelDaum - 07 Jun 2015
There are 363 extensions using PackageForm, which has a Compatibility field. Unfortunately this field is used very badly. Ultimately we depend on extension authors to test compatibility, but there's no reason to make it hard to record!
I propose the following:
- We change the Extensions.Compatibility field to a radio group, similar to that in Tasks web where we select compatibility options.
- We work through the known extensions and fix the compatibility field. I think it's reasonable to assume 1.1.x compatibility for any extension not explicitly labelled otherwise.
- Which Foswiki version you are running n the server,
- Which OS you are running on server and client,
- Which other extensions you have installed,
- Which versions of CPAN modules you have installed,
- Which browsers are going to be used, and how they are configured,
Searched: form.name='PackageForm'
WARNING: this plugin is not maintained by the original author anymore. Number of topics: 422
-- CrawfordCurrie - 09 Jun 2015
ItemTemplate edit
| Summary | Extensions web enhancements for compatibility, encoding, etc. |
| ReportedBy | GeorgeClark |
| Codebase | trunk |
| SVN Range | |
| AppliesTo | Web Site |
| Component | |
| Priority | Enhancement |
| CurrentState | Confirmed |
| WaitingFor | |
| Checkins | |
| ReleasedIn | n/a |
| CheckinsOnBranches | |
| trunkCheckins | |
| masterCheckins | |
| ItemBranchCheckins | |
| Release02x01Checkins | |
| Release02x00Checkins | |
| Release01x01Checkins |
Edit | Attach | Print version | History: r2 < r1 | Backlinks | View wiki text | Edit wiki text | More topic actions
Topic revision: r2 - 26 Sep 2016, GeorgeClark
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. 
Legal Imprint Privacy Policy
Legal Imprint Privacy Policy