Zikula Community

• autoresponse
  
  

  • Rank: Freshman
  • Registered: Apr 06, 2005
  • Last visit: Feb 27, 2010
  • Posts: 59

  Posted: Jan 14, 2008 - 05:39 PM

  I'm doing a trail upgrade of a site from 764 to .8 and need to fix a few things.
  
  Now that the submit_news module has gone, what is the correct link to use for ordinary users to submit news. Also what permissions do I need to give it so that users can make a submission but it still needs to be approved.
  
  It seems the submitted articles list has gone from news and we need to use pending content instead but I've got no idea what to use in the create element page of pending content.
  
  Does the pending content module work for new registrations. what would I use in the create element page for that.
  
  Thanks

  • 
  •  
• AmmoDump
  
  

  • Rank: Team Member
  • Registered: Dec 07, 2003
  • Last visit: May 09, 2010
  • Posts: 2703

  Posted: Jan 16, 2008 - 04:56 AM

  The news has been streamed lined...
  
  You can use module News with function new to submit News. User permission needs to be comment.
  
  The submitted news items go into pending in the News admin.
  
  --
  David Pahl
  Zikula Support Team

  • 
  •  
• ToonDawg
  
  

  • Rank: Softmore
  • Registered: Apr 27, 2006
  • Last visit: Nov 07, 2009
  • Posts: 111

  Posted: Aug 31, 2008 - 09:23 AM

  When a user submits a news article, the status is going straight to "rejected" instead of pending.
  
  My permission level is set as such: Users .* .* Comment
  
  Also, I noticed it looks like the start date and end date aren't being filled in, so it's set to the standard UNIX 1969 time. Should I fill out a bug report, or is something set up wrong in my install?
  
  
  
  edited by: ToonDawg, Sep 01, 2008 - 02:29 AM

  • 
  •  
• espaan
  
  

  • Rank: Developer
  • Registered: Aug 23, 2003
  • Last visit: May 31, 2010
  • Posts: 1428

  Posted: Sep 01, 2008 - 06:07 PM

  I get this error too, there is some inconsistency in the code.
  pnuserapi.php sets published_status to 0 for approved when admin or 1 for others in the create function
  

  Code

  } else if ( SecurityUtil::checkPermission( 'Stories::Story', '::', ACCESS_ADD)) {
          $args['published_status'] = 0;
      } else {
          $args['published_status'] = 1;
      }

  
  This should be if not access_add published_status = 2. Then it is pending.
  
  
  whereas pnadmin.php lists the following in the view function:
  

  Code

  switch ($item['published_status']) {
              case 0:
                  $item['status'] = _NEWS_PUBLISHED;
                  break;
              case 1:
                  $item['status'] = _NEWS_REJECTED;
                  break;
              case 2:
                  $item['status'] = _NEWS_PENDING;
                  break;
              case 3:
                  $item['status'] = _NEWS_ARCHIVED;
                  break;
              default:
                  $item['status'] = _NEWS_UNKNOWN;
                  break;
          }

  
  
  mmhh they are not consistent with each other. I don't know if something changed from 1.0.0 to 1.0.2 in this area. Otherwise it should be fixed asap
  ToonDawg, could you file a ticket with the Core project about this?
  
  Also the news_admin_modify.htm template lists the numbers as in pnadmin
  

  Code

  <div class="pn-formrow">
              <label for="news_published_status"><!--[pnml name="_NEWS_PUBLISHEDSTATUS"]--></label>
              <select id="news_published_status" name="story[published_status]">
                  <option value="0"<!--[if $published_status eq 0]--> selected="selected"<!--[/if]-->><!--[pnml name="_NEWS_PUBLISHED"]--></option>
                  <option value="1"<!--[if $published_status eq 1]--> selected="selected"<!--[/if]-->><!--[pnml name="_NEWS_REJECTED"]--></option>
                  <option value="2"<!--[if $published_status eq 2]--> selected="selected"<!--[/if]-->><!--[pnml name="_NEWS_PENDING"]--></option>
                  <option value="3"<!--[if $published_status eq 3]--> selected="selected"<!--[/if]-->><!--[pnml name="_NEWS_ARCHIVED"]--></option>
              </select>
          </div>

  
  so you can set the status from 0 published to the other values
  
  And the stories and storiesext block can use the status value for displaying a selected set of articles, like normally published. But you might want to list the archived articles instead. This is not possible at hte moment.
  
  --
  campertoday.nl, Module development, Dutch Zikula Community

  • 
  •  
• espaan
  
  

  • Rank: Developer
  • Registered: Aug 23, 2003
  • Last visit: May 31, 2010
  • Posts: 1428

  Posted: Sep 02, 2008 - 02:32 AM

  The bug has been submitted to the Core project and solved already by Mateo
  So wait for 1.0.3 for the fix
  
  --
  campertoday.nl, Module development, Dutch Zikula Community

  • 
  •  
• ToonDawg
  
  

  • Rank: Softmore
  • Registered: Apr 27, 2006
  • Last visit: Nov 07, 2009
  • Posts: 111

  Posted: Sep 03, 2008 - 05:56 AM

  Thanks for testing and submitting that bug! :)

  • 
  •  
•  
•  

Users on-line

• michiel

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