Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      story #7883 pluginify and upgrade PHPWiki to 1.5.2
    Actions
    Summary
    Empty
    pluginify and upgrade PHPWiki to 1.5.2
    PHPWiki is not vulnerable to publicly disclosed vulnerabilities.
    PHPWiki is outside the Tuleap core so he can be managed like any other plugin.
    • The current PHPWiki version in the Tuleap core is conserved without changes for stability reasons
    • When a project with a PHPWiki instance choose to activate the plugin:
      • The old version is no more accessible
      • All the pages and parameters must be imported in the new version
      • The project can not fall back to the old version
    • Fresh Tuleap instance can only use PHPWiki via the plugin
    Empty
    Empty
    Status
    Empty
    Canceled
    Development
    • [ ] Does it involves User Interface? 
    • [ ] Are there any mockups?
    • [ ] Are permissions checked?
    • [ ] Does it need Javascript development?
    • [x] Does it need a forge upgrade bucket?
    • [ ] Does it need to execute things in system events?
    • [ ] Does it impact project creation (templates)?
    • [ ] Is it exploratory?
    Empty
    Details
    #7883
    Thomas Gerbet (tgerbet)
    2017-02-16 15:28
    2015-02-24 15:57
    7891

    References
    Artifact links
    Empty
    Referencing story #7883

    Artifact Tracker v5

    rel #8323 8.6
    rel #8547 8.9

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/59/3859/13' of ssh://gerrit.tuleap.net:29418/tuleap into tuleap-stable-master 40528c7b32
    User avatar Manuel Vacelet (vaceletm) , 2015-08-07 15:52
    story #7883: Creation of the PHPWiki plugin 77aca930d8
    User avatar Thomas Gerbet (tgerbet) , 2015-07-30 16:52
    Merge commit 'refs/changes/66/3666/7' of ssh://gerrit.tuleap.net:29418/tuleap into stable 5b1c0dc335
    User avatar Nicolas Terray (nterray) , 2015-08-10 15:56
    story #7883: Disable register_globals for PHPWiki b874ff8d6b
    User avatar Thomas Gerbet (tgerbet) , 2015-08-10 08:58
    Merge commit 'refs/changes/72/3872/9' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 449f4ee86d
    User avatar dylan bowden (dylan) , 2015-08-21 12:13
    story #7883: site admin can choose the project to migrate to PHPWiki plugin ac625a8ef1
    User avatar Thomas Gerbet (tgerbet) , 2015-08-20 12:25
    Merge commit 'refs/changes/55/4355/2' of ssh://gerrit.tuleap.net:29418/tuleap into tuleap-stable-master 548064559e
    User avatar Manuel Vacelet (vaceletm) , 2015-08-21 14:57
    story #7883: PHPWiki plugin is visible in the widget Project Public Area 7ea0b59e28
    User avatar Thomas Gerbet (tgerbet) , 2015-08-21 12:22
    Merge commit 'refs/changes/65/3865/7' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD f9a2a16c12
    User avatar Yannis ROSSETTO (rossettoy) , 2015-08-25 12:16
    story #7883: Redirect from PHPWiki core to the plugin when a project use the plugin 897ae9e60a
    User avatar Thomas Gerbet (tgerbet) , 2015-08-24 14:35
    Merge commit 'refs/changes/19/4419/5' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD d7f78fd5ee
    User avatar Yannis ROSSETTO (rossettoy) , 2015-08-31 14:43
    story #7883: PHPWiki plugin works with Docman 2d14af34b7
    User avatar Thomas Gerbet (tgerbet) , 2015-08-31 12:25
    Merge commit 'refs/changes/51/4451/10' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 22165a963a
    User avatar Yannis ROSSETTO (rossettoy) , 2015-12-01 13:13
    story #7883: PHPWiki plugin can be accessed via the REST API 529c2a1662
    User avatar Thomas Gerbet (tgerbet) , 2015-12-01 12:07
    Abandon the unfinished PHPWiki plugin ed0b50ea35
    User avatar Thomas Gerbet (tgerbet) , 2017-02-16 15:04
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2015-07-27 15:21
    Ok for new sites.

    For existing ones we should check whether phpwiki was activated or not (service check is not enough). Until we have a clear migration path we should:
    - Use plugin for all new activations
    - Allow progressive migration (like mediawiki)
    User avatar
    Thomas Gerbet (tgerbet)2015-07-27 14:58
    On new forge: the legacy PHPWiki is not accessible.
    On existing forge:
    * the project was not using PHPWiki yet: only PHPWiki plugin is available to be enabled in the project admin.
    * the project was using PHPWiki: the project can be migrated to the plugin in the site admin. Once the plugin is activated, the legacy PHPWiki is inaccessible and redirect to the plugin. It must not be possible to enable both the plugin and the legacy PHPWiki in the same project.
    User avatar
    Manuel Vacelet (vaceletm)2015-07-23 13:31
    I mean, what is the expected workflow:
    - For new forge ?
    - For existing forge with phpwiki deployed ?

    In the first case, I expect that legacy phpwiki is not deployed, for the later what will happen in the various cases:
    - Project was not using phpwiki yet ?
    - Project was already using phpwiki ?
    User avatar
    Thomas Gerbet (tgerbet)2015-07-23 13:23
    The PHPWiki plugin is deployed like any other plugin.
    For the migration from the PHPWiki in the Tuleap core to PHPWiki plugin, we use the same method as for Mediawiki upgrade. An interface is available in the site admin to migrate a project to the plugin.
    User avatar
    Thomas Gerbet (tgerbet)2015-04-07 11:47
    • I want to
      -upgrade PHPWiki to the last version 
      +pluginify and upgrade PHPWiki to 1.5.2 
    • So that
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • Acceptance criteria
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes