Child pages
  • [in-bulletin] Poll bugs [5.0.2]
Skip to end of metadata
Go to start of metadata

Imported From: http://groups.google.com/group/in-portal-bugs/browse_thread/thread/c443f360ab73e83d#

Bug #1

  • create a new poll
  • create 2 or 3 answers
  • save your poll
  • open it again
  • go to answers tab and edit an answer
  • whether you save or cancel your answer editing, you've lost all other answers !

Bug #2

All fields are non-multilingual, and they don't interpret lang labels, thus all website can be multilingual but polls cannot.

Note #1

Missing labels in original english pack:

> on front-end
LU_TITLE_ADDCOMMENT
LU_TITLE_VIEWCOMMENTS
LU_TITLE_TOPICS
LU_NOTOPICS
LU_NEWTOPIC
LU_TITLE_NEWTOPIC
LU_TEXT_NONEWTOPICPERMISSION
LU_FLD_MESSAGEBODY
LU_FLD_DISABLEBBCODES
LU_FLD_DISABLESMILEYS
LU_FLD_SHOWSIGNATURES
LU_FLD_NOTIFYOWNERONCHANGES
LU_TITLE_ADDTOPICPENDINGCONFIRM
LU_NEWTOPIC_CONFIRM_PENDING_TEXT
LU_TEXT_MYTOPICS
LU_POSTS
LU_TOPICS
LU_COL_TOPICS
LU_COL_POSTER
LU_COL_REPLIES
LU_BTN_NEWTOPIC


> in admin
LU_PERMNAME_TOPIC.VIEW_DESC
LU_PERMNAME_TOPIC.ADD_DESC
LU_PERMNAME_TOPIC.ADD.PENDING_DESC
LU_PERMNAME_TOPIC.DELETE_DESC
LU_PERMNAME_TOPIC.MODIFY_DESC
LU_PERMNAME_TOPIC.REPLY.DELETE_DESC
LU_PERMNAME_TOPIC.REPLY.VIEW_DESC
LU_PERMNAME_TOPIC.REPLY.ADD_DESC
LU_PERMNAME_TOPIC.REPLY.MODIFY_DESC
LU_PERMNAME_TOPIC.RATE_DESC

Note #2

When adding the module after having installed In-Portal, root directory for In-Bulletin isn't configured properly: Section Properties template is set to "Inherit" and thus module cannot display any page by default, we need to change for "Topics :: /in-bulletin/design/section" (the same "inherit" problem occurs when adding all kind of module after installing in-portal).

Note #3

Poll is a nice function and should be part of CMS and not In-Bulletin, avoiding to install In-Bulletin just for this option.

Related Tasks

INP-490 - Getting issue details... STATUS

11 Comments

  1. About Note #3: I'm more to mediawiki approach, when we have minimal
    functionality in core and all is divided by modules. There are a lot of
    stuff to move to core, but is that a really good idea especially if only 5%
    of that stuff will be used by every user.

  2. allright, I didn't guessed this could be a lot of work, and it's not a
    lot of work to install a new module, it works not so bad actually.

    2010/3/16 Alexander Obuhovich <aik.b...@gmail.com>:

  3. About "Note #1". Yes, when you install module later, then it's front-end
    phrases are not inserted, since we only store language-pack wide mark, that
    theme's phrases were imported. While moving front-end phrases to theme
    folder we were considering that mark to be module based, but I don't really
    remember why we haven't implemented it that way.

    On Tue, Mar 16, 2010 at 1:15 PM, Phil ..:: domicilis.biz ::.. <

  4. Hi Phil,

    No, it's not a lot of work, but it's going to add more stuff to CORE CMS
    while we are trying to unload extra things so it's not so heavy.

    In the future we might consider smaller modules (projects) so we have more
    things available on demand and not need to install 1 big module to get most
    of the functionality, but again we should think this through.

    PS. We'll look into bugs while will be testing 5.0.3

    DA.

    On Tue, Mar 16, 2010 at 6:15 AM, Phil ..:: domicilis.biz ::.. <

  5. ok, then we have to import lang pack corresponding to added module, I
    didn't thought about that, I as thinking the first install includes
    all labels.

    2010/3/16 Phil ..:: domicilis.biz ::.. <p...@domicilis.biz>:

  6. Hi Dmitry,

    ok, thanks for detailed info, this small modules approach can be good
    for core, but also for commercial purpose, the more modules in-portal
    offers, the better will be the users feeling about in-portal.

    P.

    2010/3/16 Dmitry Andrejev <dandre...@gmail.com>:

  7. All front-end labels were separated to to proper modules inside the theme.
    Maybe as a fix we must install proper module language pack at all cases,
    when module is installed separately. What you think Dmitry.

    On Tue, Mar 16, 2010 at 1:31 PM, Phil ..:: domicilis.biz ::.. <

  8. Yes, I think it's the case.

    We should be able to install new Language pack (Phrases) from the Primary
    Theme is it's found.

    I don't think it's really hard to do, is it?

    DA.
    On Tue, Mar 16, 2010 at 6:38 AM, Alexander Obuhovich <aik.b...@gmail.com>wrote:

  9. No problem, we need to file a task for this, maybe even as bug in 5.0.3-B1
    version.

  10. Sure, that's our task:

    624: Install Front-end Language pack from Primary Theme when Module is
    installed afterward

    INP-490 - Getting issue details... STATUS


    PS. will adjust product version once 5.0.3-B1 is out.

     <

    INP-490 - Getting issue details... STATUS

    >DA.
  11. Just to summarize:

     Bug #1

    This no longer happens in 5.2.2-B1 version. Probably was fixed in some task.

    Bug #2

    Considered as an improvement, but no time for making whole Admin Console more multi-lingual now. Sorry.

    Note #1

    Task created.

    Note #2

    This no longer happens in 5.2.2-B1 version. Probably was fixed in some task.

    Note #3

    See other comments.