The admin page will show all the possible sidebar items (both from feeds and created locally) along with an enable checkbox and weight dropdown menu. The enabled items will be put in a single block and ordered by weight. The block content will look something like this:
<div> <div>item</div> <div>item</div> </div> Where "item" is the contents of the description tag of the enabled sidebar element and the div tags will have class and style attributes. I thought there was no feed.module, isn't there only import.module? This could be done within the confines of import.module, but would that be mixing different functions too much? If I do build into import.module then I need a cvs server to use, preferably SourceForge. -Neil ---- Original message ---- >Date: Tue, 29 Jul 2003 08:09:00 -0400 >From: Moshe Weitzman <[EMAIL PROTECTED]> >Subject: Re: [developers] import.module working for sidebar.module? >To: [EMAIL PROTECTED] > >Neil Drumm wrote: > >> I think these questions are mostly for Moshe >> >> The nodes for feeds and stories used by sidebar.module should not be published >> anywhere except for an admin interface, does the import module have a way to deal >> with this? Where is a current copy of node.module I can use when developing >> sidebar.module? >> >> -Neil >> >> -- >> [EMAIL PROTECTED] >> aim: ndrumm3 >> http://www.ews.uiuc.edu/~ndrumm >> > >What you want is for new items in a given feed to be 'unpublished' by >default. This prevents them from appearing anywhere except Admin. So you >need to enhance feed.module in order that new items get thus unpublish >bit set when they are saved. For UI, you will want to mimic the >'promote' dropdown menu on the feed admin page. For functionality, you >also want to mimic the 'promote' bit. If you search for 'promote' in the >code (warning - I haven't tried this) you should see how it is working >and add your publish/unpublish bit similarly. > >An HTML mockup of how this will look for Admins and for Users would help >me understand if there is a better way to accomplish this within Drupal >as opposed to creating a new module. From what I gather, you want a >feed whose last item? is always the content of a Block. We have >everything alreayd except for the 'whose content is the last item'. The >content of a feed block is usually a list of links to the most recent 5 > items from that feed ... Your goal may be better achieved by enhancing >feed.module as opposed to creating a custom module. Either way is fine I >suppose. > >
