Extension talk:NewsBulletins

Issues
''Hello Ruggerit, two more suggestions:

1) Is it correct that I have to edit the mainpage (and just save it without any changes) to see a new news on it? I tried F5, Strg+F5 but id didn't work.

2) I think it would be useful when URLs would been parsed automatically.

''Hello Ruggerit, thank you so much for this Extension! Easy, small, sexy >> perfect :) Just one little bug is annoying me. I use the SelectCategoryTagCloud (version 1.3) extension and it seems that your NewsBulletins has some parsing Problems with it. ''On my "Bulletin Page" I see the Category-Token at the end of every news.

''Your extension appears to do exactly what I've been looking for and I'm very excited about it. However, I can't get it working. After adding the php file to my extensions folder and adding the necessary line to my LocalSettings.php my entire wiki is rendered with the NewsBulletins.php text in the background. An error message is also printed out repeatedly underneath the code that says:''

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wiki/extensions/NewsBulletins/NewsBulletins.php:8) in /var/www/wiki/includes/WebResponse.php on line 10

Any ideas?

The problem is perhaps the following : when you have copied/pasted the code, you have copied a blank line. So, you have to delete the last line.

''I appreciate the quick response. However, I doubled checked the code and there are no blank lines. Any other ideas?' Is the Calendar extensions required for your extension to work?

The calendar extension is not required for this extension, I was just trying to give credit for coding ideas and help.

The php error of trying to output headers comes from an error somewhere in the php code itself. The best way to troubleshoot this is to start from the top:
 * Be sure to copy the php code exactly from the source (I will try to provide another source that is an exact file, rather than copying out of the wiki). Also, add "" to the end of the file.
 * This file should be in the extensions directory
 * The include_once php command should point to the extension file location (ex: extensions/yourdirectoryname/file.php)
 * Note that the css file will not cause this problem.

Now assuming that all these steps are followed exactly, any more information would help me in finding the problem. You say that this error message comes up on every page? What happens on pages with the  tags

I will preform some more tests and get back with any findings.

--Ruggerit 20:35, 5 August 2008 (UTC)

After a little bit of testing, I believe I found the issue. When adding the code to the wiki page, I forgot to add the  tags in the NewsBulletins.php file. These indicate the start and end of php code and are very important to the extension (and all php code). Add "" to the last line and the extension should start working. Sorry for the mistake.

--Ruggerit 00:20, 6 August 2008 (UTC)

Patch to allow wikilinks to be rendered properly in news items
The following simple change enables the extension to handle wikilinks in news items properly: 177a178 >      global $wgOut, $wgTitle, $wgParser; 213c214,217 <      return $newsBulletins->showBulletins; --- >      $popts = $wgOut->parserOptions; >      $popts->enableLimitReport( false ); >      $parserOutput = $wgParser->parse( $newsBulletins->showBulletins, $wgTitle, $popts, true, false ); >      return $parserOutput->getText; 366c370 <                              $output .= " &raquo; ". $sk->makeKnownLinkObj($title, $title_text). " "; --- >                              $output .= " &raquo; ". "$title_text". " "; -Jlerner 04:45, 3 March 2009 (UTC)

Time zone patch
This may be helpful if the correct time is not being displayed in your news bulletins.

370c370,371 <                              $output .= " ". date("M j, Y g:i a",strtotime($row->cl_timestamp)). " "; --- >                              //Patched to display correct time in current time zone >                              $output .= " ". date("M j, Y g:i a",strtotime($row->cl_timestamp) + ($wgLocalTZoffset * 60)). " ";