Extension talk:Presentation

From MediaWiki.org
Jump to navigation Jump to search

thanks guy for all your extensions.


  • Nice!

split() deprecated[edit]

Are you still maintaining this? I get these errors when using this extension:

Deprecated: Function split() is deprecated in /var/lib/mediawiki/extensions/Presentation.php on line 66
Deprecated: Function split() is deprecated in /var/lib/mediawiki/extensions/Presentation.php on line 219

I just replaced split with explode and those errors go away.

Thank you

Next slide doesn't work[edit]

MediaWiki 1.14: selecting a next article (forward button or menu) doesn't has any effect. Cause: article name contains a ' (e.g. thema's)
After changing the name, the extension was working very nice.-Bert

Problem with article title[edit]

Using article title such as "Brilliant Business Connections, Kay F (2005)", the title is been broken into different sections such as "Brilliant Business Connections" and "Kay F (2005)" and therefore does not work for already existing title with that structure.

Further creating a title link with the interlink "[[" will be followed by a fatal crash.

  • added delimiter preference --Kenyu73 16:59, 2 October 2009 (UTC)

Navigation errors[edit]

When using the dropdown menu or the errors to navigate, the extension takes you to a blank page that says Object Moved. This document may be found here. But, once you click the here link you are sucessfully back at the presentation with the correct page displayed. Can this be corrected?

Thank you in advance!

--Dgennaro 16:41, 6 October 2009 (UTC)

Slides could have a prefix[edit]

Without it we cannot have different slides with the same title (eg. Summary). It would be nice if the slides were searched as a subpage of the presentation name, like MyPresentation/Summary, MyPresentatio/Whatever etc

Only works in the Main Namespace[edit]

  1. I tested this out in a subpage of my user page (User:cornetl/testarea/present) and found that only the first slide would show. The pages that were referenced are in the Main Namespace.
  2. I then tested with pages that were in the User Namespace (root page with <presentation> and referenced pages both in the User Namespace). I had to add the 'User:' qualifier to them, but this only brought up the first slide again no matter which slide I picked.
<presentation name='test'>
User:Cornetl/testarea/test1,
User:Cornetl/testarea/test2
</presentation>
  1. Then when I moved the root page into the main Namespace it worked. This included referenceing pages in Main and User.
<presentation name='test'>
User:Cornetl/testarea/test1,
User:Cornetl/testarea/test2,
Loading system,
Differential analysis
</presentation>

I think there is a current limitation that the page with the <presentation> tags must be in the Main Namespace.

Doesn't work with Safari and Apple browser[edit]

I tested this extension in IE and Firefox = OK, wonderfull ! In Safari (Iphone and Macbook) = I can only access to the main view

Add possibility to give a caption in the combo box[edit]

Great & useful extension!

Would be even greater if you add the possibility to add a caption for each page such as

<presentation name="my name" delimiter=",">
 page1 | caption for page 1,
 page2 | caption for page 2,
 page 3 with no caption needed,
 ...
</presentation>

Starting with last slide[edit]

It would have been nice to be able to set the initial slide to the last one. If each slide represents past events, then this is best organised with the most current event at the end.

Parsing inside tag[edit]

This is a great extension. I was wondering what it would take to allow for parsing inside the presentation tag. For instance, to create a presentation with a pre-determined set of pages from a template, so using something like {{List of animals found in Tazmania}} to create a presentation from that. Alternatively, using DPL inside presentation could also plausibly work if it didn't break the presentation parsing, which it does now. For instance, using <presentation...>{{#dpl:category=Animals found in Tazmania}}</presentation>. This could allow for rapid creation of presentations without having to tediously select each page you want for very large or large numbers of presentations.    Thorncrag   21:27, 9 February 2011 (UTC)

I was able to add this functionality to the extension by telling it to parse wiki text. I don't know if this is exactly standard procedure, but it worked for me so here's what I did. In the extension:
@ line 39:
--function launchPresentation( $paramstring, $params = array() ){
++function launchPresentation( $paramstring, $params = array(), $parser, $frame ){

@ line 49:
++$paramstring = $parser->recursiveTagParse( $paramstring, $frame );

This enables me to, inside the presentation tag, reference a page which contains a dynamically-generated list which is precisely what I was looking to do. Hope this helps someone else.    Thorncrag   00:19, 29 March 2011 (UTC)

Can you make it C5?[edit]

http://meyerweb.com/eric/tools/s5/

Cheers, --Dmb 10:40, 11 March 2011 (UTC)

Extension:S5SlideShow. Although this one doesn’t work with MediaWiki 1.24 (current version). ~ Seb35 [^_^] 18:06, 6 April 2015 (UTC)

Call to a member function getText() on a non-object[edit]

Is this extension still being maintained? I'm getting an error

PHP Fatal error: Call to a member function getText() on a non-object in extensions/Presentation/Presentation.php on line 43

This is a nice extension Thank you

XSS vulnerability / major security issue[edit]

This extension has multiple issues with XSS vulnerabilities: most of the variables are not escaped, e.g. the variable $name corresponding to the name of the presentation given in the parameter name could be crafted to display arbitrary HTML on the page. This is a quite serious security issue. ~ Seb35 [^_^] 18:04, 6 April 2015 (UTC)

Google Code Shutting Down[edit]

Hello, As you are likely aware, Google is shutting down their Google Code service in January of 2016. This extension appears to house its code with Google Code and is at risk to creating broken links and confusion of users in the near future.

I’m helping to let folks know about this coming update and provide some helpful links to make this migration easy. I hope you’ll take a moment and migrate your extension to a new hosting solution.

For extensions that have a compatible license, you can request developer access to the MediaWiki source repositories for extensions and get a new repository created for you. Alternatively, you may also export your code to other popular repositories such as Github and Bitbucket. Google has provided tools to help with this migration.

Ckoerner (talk) 17:20, 7 July 2015 (UTC)