Fork me on GitHub

Admin Messages dead?  Bottom

  • I just downloaded the 1.3 test copy. Did some basic setup and went to edit the default admin message.... and it's not that anymore, but an HTML block. Admin messages not to be found in Modules. Not to be found in Cozi. Not to be found in Github (maybe not looking in the right place?).

    Is it dead?
  • It's removed. There's little need for it when there's stuff like an HTML block, PageMaster, Pages, and other modules that can accomplish the same task.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • Admin_Messages basically is a "PostNuke concept", but I imagine that a copy of it can be available to work as another third party module.

    --
    - Mateo T. -
    Mis principios... son mis fines
  • When you upgrade from 1.2.x your Admin_Messages will be migrated to HTML blocks and the Admin_Messages module entry and table will be deleted. The module was removed because basically, it's a duplication of the HTML block and therefor pointless for us to maintain.

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • No, no, no :) Admin messages is a nice simple database and has options to set publication and expiration dates as well as simple permissions that "mere mortals" (as my clients say) can use. I have low priority requests from these users to add sorting capabilities to the module, so maybe I'll adopt this one.
  • icon_smile
    You are most welcome. Please head over the github.com and setup an account. We can create a Cozi account for you to track your tickets.

    Drak

    --
    Zikula Lead Developer
    Board Member of the Zikula Foundation
    Follow me on twitter.com/zikuladrak
  • I find it a shame also that the admin messages module will not be kept as a core module. It allows users with very little knowledge instant use and is quite a no-brainer to run. As far as usability, if too many useful modules are stripped off the core package, you will end up with a dev-concentric CMS that will have very little popular appeal and may run the risk of being marginalized as a useful product.

    Fewer users -> less interest -> fewer devs -> more work for core devs -> more removal of core modules -> fewer users again and round it goes again. You may find yourselves constantly looking for people to pick up the development of modules for sheer lack of manpower. There is, after-all, a point where if the critical mass of users is so low that it then becomes a constant drain on dev resources time to maintain useful modules. Time becomes a premium commodity.

    If the philosophy behind Zikula is to appeal to people who are interested in raising CMS sites, then you have to be careful in pruning too much off the usability of the product.

    It makes me wonder what are the modules that you (Zikula core devs) consider the core modules necessary to make Zikula a good CMS solution? Will it have enough modules as a package to satisfy a ready-made download, easy-to-install and quick to configure as a minimal CMS site?

    As a user here is what I would consider a good baisc CMS solution:

    - admin tools (updates/language/settings/ header & footer mod. capable/admin message module/)
    - blogging or page or news module (incorporates photos/videos/sound) -- after all that is what the CMS is for
    - photo album module
    - calendar module
    - user module
    - stats module
    - weblinks module

    Not sure if I missed any that you may find necessary, but these, I would say are the basic necessities of a CMS. If a new user has to work too hard to get these to work, then the appeal, for lack of user time, is quite negative. Ease-of-use should be the over-riding tenant of the package.

    Just my thoughts on not including the admin message module. It will be sorely missed by users like myself. Worse yet, by people who will write in the forums, requesting information on how to leave admin message on their Zikula installation when you really never field such questions now. I just think it's a hurdle for both user-dev that could just simply be easily solved by keeping it in. I hope you reconsider this move.

    You do have a great package, but I find that it is taking more and more time/effort/ to keep the sites going when there is an update. Not to mention, less and less traffic on the forums.

    Marc
  • The solution of using HTML block instead of admin_message is good idea, but as marc and bronto said, it was a useful module for end-users adding information for a group or for a duration.
    If I add a block HTML for my client they'll have to manage group permission and manually close the visibility of the block.
  • Marc - IMHO, you are confusing "the Core" with a "distribution". The "core" is simply the main "Application Framework" which allows a CMS to function. It provides APIs and technologies to enable what is seen. The "core" has been pared back since Zikula v1.0 and is further refined in the current version and again in 1.3.

    A distribution is what you want - and what you WILL get. Following the completion of v1.3.0, the "core" will not typically be distributed as a standalone download. A Zikula-Foundation-supported 'official distribution' will become the main download. This will include various important modules (including third party) and will be fully functional "out of the box".

    So, in a nutshell, you are right - more things should be included in a standard download. It will be - it will just be called a 'distribution', not the 'core'.

    and Admin messages is still available and being developed. see above.
  • Yes, sorry about that.

    I am just concerned that the view from developers is that its usefulness is negligible, whereas, I find that it is one of the more important module of the distribution from users' perspective. It is normally the first message I use on my Zikula sites for site information to users and the one that I use to communicate with the users.

    Marc

This list is based on users active over the last 60 minutes.