In-Bulletin Poll bugs - v502

1 view
Skip to first unread message

Phil

unread,
Mar 15, 2010, 7:26:01 PM3/15/10
to In-Portal Bugs Team
Hello,

test on v502 english-only lamp platform.

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
- wether 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.

Phil.

Alexander Obuhovich

unread,
Mar 16, 2010, 4:57:36 AM3/16/10
to in-port...@googlegroups.com
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.


--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.




--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

Phil ..:: domicilis.biz ::..

unread,
Mar 16, 2010, 7:15:54 AM3/16/10
to in-port...@googlegroups.com
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....@gmail.com>:

Alexander Obuhovich

unread,
Mar 16, 2010, 7:20:02 AM3/16/10
to in-port...@googlegroups.com
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.

Dmitry Andrejev

unread,
Mar 16, 2010, 7:27:13 AM3/16/10
to in-port...@googlegroups.com
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.

Phil ..:: domicilis.biz ::..

unread,
Mar 16, 2010, 7:31:58 AM3/16/10
to in-port...@googlegroups.com
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 ::.. <ph...@domicilis.biz>:

Phil ..:: domicilis.biz ::..

unread,
Mar 16, 2010, 7:35:11 AM3/16/10
to in-port...@googlegroups.com
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 <dand...@gmail.com>:

Alexander Obuhovich

unread,
Mar 16, 2010, 7:38:08 AM3/16/10
to in-port...@googlegroups.com
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.

Dmitry Andrejev

unread,
Mar 16, 2010, 8:14:29 AM3/16/10
to in-port...@googlegroups.com
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.

Alexander Obuhovich

unread,
Mar 16, 2010, 8:15:50 AM3/16/10
to in-port...@googlegroups.com
No problem, we need to file a task for this, maybe even as bug in 5.0.3-B1 version.

Dmitry Andrejev

unread,
Mar 16, 2010, 8:23:04 AM3/16/10
to in-port...@googlegroups.com
Sure, that's our task:

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


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

DA.
Reply all
Reply to author
Forward
0 new messages