11
chapi
Re: Xoops 2.1 Module development Roadmap
  • 2003/11/7 9:53

  • chapi

  • Theme Designer

  • Posts: 611

  • Since: 2002/1/22


Members
- ability to choose whether the search form should be displayed or not, if _not_ is selected display the userlist directly
- ability to search the users by groups

News
- group permissions on categories in the administration
- enhanced dhtml editor (marking a text and selecting bold will make it bold)
- integrate wysiwyg editor (eventully this should be moved to the core, so all modules can make use of it)
- add the news posts to the members post count

Newbb
- subcategories
- possibility to delete single posts

Downloads
- ability to upload files when submitting a download

Weblinks
- ability to upload screenshots when submitting a link
- ability to automatically resize these screenshots

Contact
- ability to configure the input fields
- ability to set fields as recommended
- emailadress from sender into the head (currently when I reply to an email it is sent to me )
- ability to use a different email address than the admin one, possibility to send this data to more than one email-address, maybe to a whole usergroup

12
Catzwolf
Re: Xoops 2.1 Module development Roadmap
  • 2003/11/9 7:10

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


Thanks Chapi for the ideas Some good ones too

13
Catzwolf
Re: Xoops 2.1 Module development Roadmap
  • 2003/11/9 7:12

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


All these should be implemented in a future version without the need of hacks

14
Catzwolf
Re: Xoops 2.1 Module development Roadmap
  • 2003/11/9 7:14

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


Many thanks to eveyone who has put forward their 'wants', please do not stop there. Use your chance now to get what you want into your modules or don't moan about it later

Come on, I thought you lot where going to give us a headache with so much to choose from lol!

15
Olorin
Re: Xoops 2.1 Module development Roadmap
  • 2003/11/9 11:30

  • Olorin

  • Just popping in

  • Posts: 50

  • Since: 2003/7/5 1


Well, when it comes to the requests against newbb, Xoopsers have requested everything I want on the newbb thread.(maybe started by Catzwolf?)

-About Contact Module-
I have a suggestion about a contact module for Xoops2.1.
Why don't you take into consideration to replace the current contact module with liaise(@BradyCoke) as Wf-section replaced section module as an official one. Liaise definitely has enough flexibility for a contact module. (Plus you can enjoy default nonsense questions.lol)

Links
- Ability to have multiple category per link.
- Ability to control the max & min number of categories per link(Admin)
- *More flexible navigation control

I need to explaion what I mean with the last request.

----Category Structure----
Softwares(Parent Category A)
-Linux (Child A1)
-Windows (Child A2)

Harwares(Parent Category B)
-Linux (Child B1)
-Windows (Child B2)
--------------------------

In this case, If you click "Softwares", the 2 links: "Linux" and "Windows" show up at the top since they are its Children. But if you can refer to not only its Child-Categories, but also arbitary Parent and Child Categories, it would be much functionable Link Module, woudn't it? As you can imagine, it would be friendly to visitors if they are also able to move to Hardwares-Windows with ease when they are checking Softwares-Windows.

(You might say "Why don't you make Windows Parent and make soft & hard its Children?" Yes, that really makes sense. But it is just an example... )

16
gruessle
Re: Xoops 2.1 Module development Roadmap
  • 2003/11/9 11:41

  • gruessle

  • Friend of XOOPS

  • Posts: 348

  • Since: 2003/9/20


I think Olorin has a good point I would like to extend on that:

--------- CatA -------------- CatB
----- CatA1 - CatA2 ----- CatB1 - CatB2
------------------- CatAB1

CatAB1 as Sub Category in both CatA2 & CatB1

----------------

Besides I think Links should be replaced with the Addresses module

------------------

webmaster registration @ xoops.org
How about if XOOPS webmasters could register with xoops.org and xoops.org would check their website once a month or so and list the most used or most users XOOPS site in a block at xoops.org.

The list could included
How many users
Language
Title & Slogan of site

17
ronhab
Re: Xoops 2.1 Module development Roadmap
  • 2003/11/9 12:52

  • ronhab

  • Friend of XOOPS

  • Posts: 160

  • Since: 2003/4/27


News
- Has a bug where when a person submits news, the Time of Expiration is set to 12/31/1969 instead of the current date.
- Ability to vote on stories as well as comments (moderation)
- The drop down boxes for both Time of Publication and Time of Expiration only go up until 2004. 2005 will be here sooner than we think!
- If you add multiple subtopics to a main topic, the subtopics are not alpha sorted and thus get out of order rather easily
- Ability to have expired articles pruned from the database or stored in a second database or some other way that can help limit growth of the primary database.
- Add a poll to a story
- A what's related block

NewBB
- Mark all read button
- Moderation/voting as above
- Mark all read button
- Subcategories for forums
- Mark all read button
- Friends/foes system or, what may be simpler - an "ignore this user" button/function
- Mark all read button
- Delete a post without losing all the sub posts
- Mark all read button
- Hide private forums except for those users that have access to it
- Mark all read button

Contact Us
- Ability to customize the form
- Check box for "I wish to be contacted on this issue"
- Checkboxes/drop down list for the topic of the message (general, site feedback, bug report, problem logging in, suggestion, etc.)

Oh, one more thing: Is it possible to get a mark all read function for the forums?

18
GIJOE
Use name() instead of uname()
  • 2003/11/9 12:53

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


Users have two type of name in most systems.
I think that the two names have the following characters each other.

1) Login name
It is used at login.
Therefore, it is necessary to limit the character which can be used.
(Especially with mutlibyte languages)
This information should not be opened to the public too much.
There are some systems which conceals Login name.

2) Nickname ("Real name" in some systems).
It is used for the display.
Because more various expressions are permitted,
the character which can be used should be abundant.

In XOOPS, I believe that uname should be "Login name" and name should be "Nickname".

But almost modules use $xoopsUser->uname() instead of name() for displaying.

"All modules should display Nickname instead of Login name."

If 'name' field isn't suitable for Nickname, 'nickname' field should be added into the user's table by Core Development Team.

19
dlh
Re: Use name() instead of uname()
  • 2003/11/9 20:12

  • dlh

  • Posts: 182

  • Since: 2002/2/20


Great suggestions already from everybody!

I would like to add a suggestion for a new core module. I believe that a newsletter module should be added as a core content related module. There should be content hooks for the core modules: news, links, newbb, faq, members, etc. These hooks should tell XOOPS to "place this content, in this location, representing this timeframe".

Thus once you set you your newsletter template, it can be automagically generated by the system and sent out to members who have elected to receive the newsletter.

Also, people should be able to sign up for the newsletter but not membership.

Thanks for listening!

Later,

Dan

20
Catzwolf
Re: Use name() instead of uname()
  • 2003/11/10 2:07

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


Quote:

dlh wrote:
Great suggestions already from everybody!

I would like to add a suggestion for a new core module. I believe that a newsletter module should be added as a core content related module. There should be content hooks for the core modules: news, links, newbb, faq, members, etc. These hooks should tell XOOPS to "place this content, in this location, representing this timeframe".

Thus once you set you your newsletter template, it can be automagically generated by the system and sent out to members who have elected to receive the newsletter.

Also, people should be able to sign up for the newsletter but not membership.

Thanks for listening!

Later,

Dan


First, There will be no more core modules as from 2.1.0, these will be replaced by certified XOOPS Modules.

Next, The newsletter module will be updated with many new features.

:)


Login

Username:
Password:

Lost Password? Register now!

Who's Online

53 user(s) are online (22 user(s) are browsing Support Forums)


Members: 0


Guests: 53


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits